echnologies and should be expressed in terms of the user experience rather than any particular solution or technical attribute. For example, in relation to battery life for mobile devices, power consumption is a technical attribute, whereas the length of time between battery recharging is what the user is really concerned about. For a PAN implementation project targeting a large user group it will be important to gather a wide range of views on user requirements - for Chapter Eleven example using a questionnaire or by interview. As a first step it may be necessary to raise awareness by demonstrating the technology to the prospective user group, SO that they are better able to give an informed view on requirements. Common types of user requirement are listed and discussed in Table 11-1. Table 11-1: PAN User Requirement Types Requirement type Considerations Usage model It is important to be clear what types of use the PAN will be put to; portable device synchronisation with a desktop or laptop computer, data exchange between portable devices, etc. Is the usage model likely to change in future or are requirements well defined and static? Device types What type of devices will be used in the PAN? Examples include laptop computer, PDA, mobile phone, hands free headset, personal video player. There may also be a requirement to connect to non-mobile devices - a desktop computer or LAN and related resources. Performance What are the user's performance expectations? This will be expectations particularly important if the usage model includes the transfer of large data files or media streaming. Device weight Particularly for PAN devices that are worn, such as a and size hands-free headset, minimising device size and weight is likely to be a requirement. Ease of connection How important is ease of connection and reconnection. If a device will be used often but intermittently, then the user may not want to perform port activation and authorisation each time a connection is made, such as is required for an IrDA link. Bluetoot