user interface design chapter 4 user requirements: elicitation and analysis
TRANSCRIPT
![Page 1: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/1.jpg)
User Interface DesignUser Interface Design
Chapter 4 Chapter 4
User requirements:elicitation and analysis
![Page 2: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/2.jpg)
Learning outcomesLearning 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.
![Page 3: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/3.jpg)
Learning outcomesLearning outcomes
Outcome 3 : Be ware of the different techniques
used for data collection and understand how to
apply some of more common ones.
![Page 4: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/4.jpg)
Section 1 Section 1
Where do we start?
models
Waterfall model of systems lifecycle
Figure 4.1
![Page 5: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/5.jpg)
Section 1 Section 1
Where do we start?
Star model of systems development
Figure 4.2
![Page 6: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/6.jpg)
Section 1 Section 1
Where do we start?
iterative
evaluation
human centred and iterative development
model
![Page 7: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/7.jpg)
Section 1 Section 1
Where do we start?
Framework of ISO 13470:Human-centred
design processes for interactive systems
Figure 4.3
![Page 8: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/8.jpg)
Section 1 Section 1
Where do we start?
stakeholder
![Page 9: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/9.jpg)
Section 2 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 users Main task goals
Other stakeholders Main task goals
![Page 10: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/10.jpg)
Section 2 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
![Page 11: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/11.jpg)
Section 2 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 attributesAge range
Physical abilities, limitations/ disabilities
Mental attributesIntellectual abilities(a)Differing information search / browsing preferences(b)Specific mental impairments
![Page 12: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/12.jpg)
Section 2 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
![Page 13: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/13.jpg)
Section 2 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
![Page 14: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/14.jpg)
Section 2 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
![Page 15: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/15.jpg)
Section 2 Section 2
The problem definition
Other user interface requirements
◦specific
◦measurable
◦evaluated
![Page 16: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/16.jpg)
Section 3 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
![Page 17: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/17.jpg)
Section 3 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
![Page 18: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/18.jpg)
Section 3 Section 3
Techniques for requirements elicitation
Survey
◦Quantitative
◦Open
◦Categorical
◦Rank order
◦Scalar
![Page 19: User Interface Design Chapter 4 User requirements: elicitation and analysis](https://reader035.vdocuments.us/reader035/viewer/2022062422/56649e7f5503460f94b83809/html5/thumbnails/19.jpg)
Section 3 Section 3
Techniques for requirements elicitation
Focus groups
Interviews
Observation
a final note
◦Data collection
◦Analysis and interpretation