1. Interaction Design
Lifecycle Models, Needs and Requirements,and Prototyping
2. 3. 1
Lifecycle models
2
Needs and requirements
3
Prototyping
* The contents of this presentation has been adapted from chapters
9, 10 and 11 of
Interaction Design: beyond human-computer interaction (2nd edition)
by Sharp, Rogers and Preece
4. Exercise:
Interactive childrens book
5. 1
Lifecycle models
6. [] a model that captures a set of activities and how they are
related.
7. 8. Three examples:
Software engineering
Interaction Design
HCI
9. Interaction design model
10. Start
Identify needs and establish requirements
Evaluate
(Re)Design
Final
product
Build an interactive version
11. A software engineering
model
12. Requirement analysis
Design
Code
Test
Maintenance
13. A HCI model
14. Requirements / specification
Task analysis / functional analysis
Conceptual design / formal design representation
Prototyping
Implementation
Evaluation
15. ?
16. Identifying needs and establishing requirements
2
17. What are needs and requirements
a
Types of requirements
b
Data gathering for requirements
c
Data analysis and interpretation
d
18. Identify needs and establish requirements
Start
Evaluate
(Re)Design
Final
product
Build an interactive version
19. ?
Needs and requirements
20. Whybother?
21. Involves twoaims
22. Identifying needs:
[] to understand as much as possible about the users, their work,
and the context of that work, so the system under development can
support them in achieving their goals
23. Establishing requirements:
[] to produce, from the needs identified, a set of stable
requirements that form a sound basis to move forward into the
thinking about design
24. Three activities:
Data
gathering
Analysis and interpretation
Establishment of requirements
25. Three activities:
Data
gathering
Analysis and interpretation
Establishment of requirements
26. Two types:
27. Functional requirements:
specifies what the system should do
28. Non-functional requirements:
dictated by constraints on the system and development
29. Data requirements
30. Environmental requirements
31. User characteristics
32. Usability and user experience goals
33. Data gathering
for requirements
34. Interviews
when you want to explore
35. Focus groups
exploring different views
36. Questionnaires
getting initial and general responses
37. Direct
observation
38. Indirect
observation
39. Study documentation
40. Research
similar products
41. Contextual Inquiry
a popular method for uncovering requirements
42. Four main principles
of contextual inquiry
Context
Partnership
Interpretation
Focus
43. Data analysis and interpretation
moving from the collected data to clear requirements:
44. Scenarios
Exploring contexts, needs, and requirements through stories of
human activities or tasks
45. Scenario example:
The Thomson family enjoy outdoor activity holidays and want to try
their hand at sailing this year. There are four members of the
family: Sky who is 10 years old, Eamonn who is 15 years old, Claire
who is 35, and Will who is 40. While out on a shopping trip they
call by at the travel agents in their local town to start exploring
the possibilities ... The travel organizer is located in a quiet
corner of the agents office, where there are comfortable seats and
play things for young children. They all gather around the
organizer and enter their initial set of requirementsa sailing
holiday for four novices. The stand-alone console is designed so
that all members of the family can interact easily and comfortably
with it. The systems initial suggestion is that they should
consider a flotilla holiday, where several novice crews go sailing
together and provide mutual support for first-time sailors
46. Personas
Fictional users synthesized based on information gathered from real
users
47. Properties
