e prospective user group, SO that they are better able to give an informed view on requirements. Implementing Wireless LANs User requirements should be expressed in terms of the user experience rather than any particular solution or technical attribute, as they are independent of specific technologies. For example, in relation to performance expectations, a PHY layer data rate is a technical attribute, whereas the transfer time for a specified large file size is what the user is really concerned about. Common categories of user requirement are listed and discussed in Table 7-1. In virtually all aspects of user requirements the question of future proofing also arises; are future developments expected in the users' work processes, the type of technologies deployed in the users' business, growth in the business, etc., that will change the overall demands placed on the WLAN? Table 7-1: WLAN User Requirement Types Requirement type Considerations Usage model What user activities does the WLAN have to support? Are users routinely transferring large files over the network, such as Internet downloads or video editing? Is the WLAN required to support applications such as voice or video streaming, either now or in the future? Performance What are the user's performance expectations? If large data expectations files are commonly used, what are the required transfer times? Areal coverage What is the operating area in which users will need wireless network coverage? Do usage requirements vary at different locations within this area? Is future growth of the required coverage area expected? Mobility If users will move within the operating area while working, will they need to access the WLAN from several fixed locations (roaming) or will they need continuous service while in motion (mobility) - for example to support voice services? Device What types of user devices will need to connect to the interoperability network? User population What is the total number of users and user devices that are required to be supported? How many 