User Interface Design Chapter 4 User requirements: elicitation and analysis

Learning outcomes Outcome 1 : Understand the advantages and limitations that different systems development models bring to the requirements elicitation process. Outcome 2 :Understand a general model of the requirements elicitation process and how this leads to the production of a problem definition.

Learning outcomes Outcome 3 : Be ware of the different techniques used for data collection and understand how to apply some of more common ones.

Section 1 Where do we start? models Waterfall model of systems lifecycle Figure 4.1

Section 1 Where do we start? Star model of systems development Figure 4.2

Section 1 Where do we start? iterative evaluation human centred and iterative development model

Section 1 Where do we start? Framework of ISO 13470:Human-centred design processes for interactive systems Figure 4.3

Section 1 Where do we start? stakeholder

Section 2 The problem definition What you are aiming to achieve and the next section as how you could achieve this aim Summary of main stakeholders Primary usersMain task goals Other stakeholdersMain task goals

Section 2 The problem definition User group characteristics (1/4) System: Local Office intranet User group: Staff of Local Office Characteristics Skills and knowledge Experience in: (a)Using the current system (b)Using other systems with similar main functions (c)Using systems with the same interface style Potential system requirements Education / qualifications

Section 2 The problem definition User group characteristics (2/4) System: Local Office intranet User group: Staff of Local Office Linguistic ability Background knowledge/ IT knowledge Physical attributes Age range Physical abilities, limitations/ disabilities Mental attributes Intellectual abilities (a)Differing information search / browsing preferences (b)Specific mental impairments

Section 2 The problem definition User group characteristics (3/4) System: Local Office intranet User group: Staff of Local Office Motivations (a)Attitude to job and task (b)Interactions with others (c)Attitude to the system (d)Attitude to information technology (e)Employees attitude to the employing organization

Section 2 The problem definition User group characteristics (4/4) System: Local Office intranet User group: Staff of Local Office Job characteristics Job function Hours of work / operation (a)Hours of work (b)Hours using system (c)Discretion to use Other relevant features

Section 2 The problem definition Other user interface requirements ◦Overall concept of the system ◦Usability features 1.Relevance 2.Content 3.Subjective appeal 4.navigation 5.Accessibility 6.Consistency 7.Transparency

Section 2 The problem definition Other user interface requirements ◦specific ◦measurable ◦evaluated

Section 3 Techniques for requirements elicitation Requirements elicitation techniques Focus on identifying the stakeholders’ needs Involve all the stakeholder groups Involve more than one person from each stakeholder group

Section 3 Techniques for requirements elicitation Use a variety of data gathering techniques Support the data gathering sessions with suitable props Run pilot sessions Data recording is important Be realistic about what can be achieved with the resources available

Section 3 Techniques for requirements elicitation Survey ◦Quantitative ◦Open ◦Categorical ◦Rank order ◦Scalar

Section 3 Techniques for requirements elicitation Focus groups Interviews Observation a final note ◦Data collection ◦Analysis and interpretation