6/8/2020

Chapter 10
10.1 Introduction
10.2 What, How, and Why?
10.3 What Are Requirements?
10.4 Data Gathering for Requirements
10.5 Data Analysis, Interpretation, and
Presentation
Chapter 10 10.6 Task Description
ESTABLISHING REQUIREMENTS 10.7 Task Analysis

www.id-book.com 2

10.1 Introduction Examples

• The importance of requirements
1. Smart phone, tablet
• Different types of requirements
2. Reader
• Data gathering for requirements (ch.7) 3. Smart watch
• Data analysis and presentation (ch.8) 4. Máy ATM
• Task description: Scenarios 5. Máy bán hàng tại siêu thị 24h
Use Cases 6. Thiết bị cầm tay của nhân viên phục vụ ăn
uống
Essential use cases
7. Thiết bị cầm tay của nhân viên giao hàng
• Task analysis

www.id-book.com 3 www.id-book.com 4

1
6/8/2020

2
 6/8/2020

10.2 What, how and why?

10.2.1 What needs to be achieved?
1. Understand as much as possible about
users, activity, context of activity
2. Produce a stable set of requirements
10.2.2 How can this be done?

• Data gathering activities (ch.7)

• Data analysis activities (ch.8)
• Expression as ‘requirements’
• All of this is iterative

www.id-book.com 10

Process of ID 10.2 What, how and why?

10.2.3 Why
Establish requirements bother?
Requirements
definition is the
Evaluation Solutions stage where
failure occurs
most commonly

Prototype
Getting requirements right is crucial
11 www.id-book.com 12

3
 6/8/2020

10.2 What, how and why? 10.3 What are requirements

10.2.4 Establishing requirements • Requirements: specific, unambiguous, clear
• What do users want? What do users ‘need’?
— Ex: smartwatch GPS app
Requirements need clarification, refinement, completion,
re-scoping • Example requirement: atomic requirement
Input: Requirements document (maybe)
sell (next slide)
Output: stable requirements

• Why ‘establish’?

Requirements arise from understanding users’ needs

Requirements can be justified & related to data
www.id-book.com 13 www.id-book.com 14

Volere shell 10.3.1 Different kinds of requirements

1. Functional:
—What the system should do
—Ex: new video game challenging for a range of user
abilities
2. Non-functional:
—Constrains
—Ex: many platforms, security, response time,…
—Ex: telecare system
3. Data:
—What kinds of data need to be stored?
—How will they be stored (e.g. online database,
15
banking,…)? 16

4
Slide 15

1 This is the same as the one in our book, but it's not the same as the one in the refernce. The date in the 'history' field should be 2013 -
see original handover of figure
Helen Sharp, 1/17/2015
 6/8/2020

Volere requirements template

www.id-book.com 17

5
 6/8/2020

Box 10.1
10.3.1 Different kinds of requirements Environmental requirements: Underwater computing
3

4. Environment or context of use:

• physical: dusty? noisy? vibration? light? heat?
humidity? …. (e.g. ATM)
• social: sharing of files, of displays, in paper, across
great distances, synchronous, privacy for clients
• organisational: hierarchy, IT department’s attitude
and remit, user support, communications structure
and infrastructure, availability of training
5. User Characteristics

www.id-book.com 21 www.id-book.com 22

Underwater computing – SeaSlate

Display “what you see is what you press”

Kord Key Pad

www.id-book.com 24

6
Slide 22

3 From figures 10.2 and 10.3

Helen Sharp, 1/17/2015
 6/8/2020

10.3.1 Different kinds of requirements What are the users’capabilities?

Humans vary in many dimensions:
Users: Who are they? (user profile) — size of hands may affect the size and positioning of
input buttons
— Characteristics: nationality, educational background,
attitude to computers — height if designing a physical kiosk

— System use: novice, expert, casual, frequent — strength - a child’s toy requires little strength to
operate, but greater strength to change batteries
— Novice: prompted, constrained, clear
— disabilities (e.g. sight, hearing, dexterity)
— Expert: flexibility, power of control

— Frequent: short cuts

— Casual/infrequent: clear menu paths

www.id-book.com 25 www.id-book.com 26

Personas Box 10.2 Example Persona

4

• Capture a set of user characteristics (user

profile): skill, attitudes, tasks, enviroments.

• Not real people, but synthesised from real users

• Should not be idealised

• Bring them to life with a name, characteristics,

goals, personal background

• Develop a small set of personas with one primary

www.id-book.com 27 www.id-book.com 28

7
Slide 28

4 Replace this image with one from figure 10.4 (a)

Helen Sharp, 1/17/2015
 6/8/2020

Box 10.2 Example Persona Activity 10.1

Suggest some key requirements in each
category above (functional, data,
environmental, user characteristics, usability
goals, and user experience goals) for the
following situations:

An interactive product for use in a university's

self-service cafeteria that allows users to pay
for their food using a contactless card or
smartphone.
www.id-book.com 29 www.id-book.com 30

10.4 Data gathering for requirements 10.4 Data gathering for requirements
• Interviews:
• Questionnaires:
— Props, e.g. sample scenarios of use, prototypes, can be used in
interviews — Often used in conjunction with other techniques
— Good for exploring issues — Can give quantitative or qualitative data
— Development team members can connect with stakeholders
— Good for answering specific questions from a large,
• Focus groups: dispersed group of people
— Group interviews • Researching similar products:
— Good at gaining a consensus view and/or highlighting areas of
conflict — Good for prompting requirements
— But can be dominated by individuals

www.id-book.com 31 www.id-book.com 32

8
 6/8/2020

10.4 Data gathering for requirements

Data gathering for requirements
• Direct observation: Studying documentation:
— Gain insights into stakeholders’ tasks — Procedures and rules are often written down in
manuals
— Good for understanding the nature and context of the
tasks — Good source of data about the steps involved in an
activity, and any regulations governing a task
— But, it requires time and commitment from a member of
the design team, and it can result in a huge amount of data — Not to be used in isolation
• Indirect observation: — Good for understanding legislation, and getting
background information
— Not often used in requirements activity
— No stakeholder time, which is a limiting factor on the
— Good for logging current tasks other techniques

www.id-book.com 33 www.id-book.com 34

Some examples Some examples

Ethnographic study, interviews, usability tests, and user
participation

Cultural probes

www.id-book.com 35 www.id-book.com 36

9
 6/8/2020

Contextual Inquiry Considerations for data gathering (1)

• An approach to ethnographic study where user is expert, • Identifying and involving stakeholders: users, managers,
developers, customer reps?, union reps?, shareholders?
designer is apprentice
• A form of interview, but • Involving stakeholders: workshops, interviews, workplace
studies, co-opt stakeholders onto the development team
— at users’ workplace (workstation)
— 2 to 3 hours long • ‘Real’ users, not managers

• Four main principles: • Political problems within the organisation

— Context: see workplace & what happens
• Dominance of certain stakeholders
— Partnership: user and developer collaborate
— Interpretation: observations interpreted by user and developer • Economic and business environment changes
together
— Focus: project focus to understand what to look for • Balancing functional and usability demands

www.id-book.com 37 www.id-book.com 38

Considerations for data gathering (2) Data gathering guidelines

• Requirements management: version control, ownership • Focus on identifying the stakeholders’ needs
• Communication between parties: • Involve all the stakeholder groups
—within development team • Involve more than one representative from
—with customer/user
each stakeholder group
—between users… different parts of an
organisation use different terminology • Use a combination of data gathering
• Domain knowledge distributed and implicit: techniques
—difficult to dig up and understand
—knowledge articulation: how do you walk? • Support the process with props such as
• Availability of key people prototypes and task descriptions
www.id-book.com 39 www.id-book.com 40

10
 6/8/2020

10.5 Data interpretation and analysis 10.6 Task descriptions

• Scenarios
• Start soon after data gathering session ― an informal narrative story, simple, ‘natural’,
personal, not generalizable
• Initial interpretation before deeper analysis • Use cases
— assume interaction with a system
• Different approaches emphasize different — assume detailed understanding of the interaction
elements e.g. class diagrams for object- • Essential use cases (task case)
oriented systems, entity-relationship — abstract away from the details
diagrams for data intensive systems — does not have the same assumptions as use cases

www.id-book.com 41 www.id-book.com 42

Scenario for University

Scenario for movie rental service
admissions office

11
 6/8/2020

Scenario for travel organizer

“The Thomson family enjoy outdoor activities and want to try their hand at
sailing this year. There are four family members: Sky (10 years old),
Eamonn (15 years old), Claire (35), and Will (40). One evening after dinner
they decide to start exploring the possibilities. They all gather around the
travel organizer and enter their initial set of requirements – a sailing trip for
four novices in the Mediterranean. The console is designed so that all
members of the family can interact easily and comfortably with it. The
system’s initial suggestion is a flotilla, where several crews (with various
levels of experience) sail together on separate boats. Sky and Eamonn
aren’t very happy at the idea of going on vacation with a group of other
people, even though the Thomsons would have their own boat. The travel
organizer shows them descriptions of flotillas from other children their ages
and they are all very positive, so eventually, everyone agrees to explore
flotilla opportunities. Will confirms this recommendation and asks for detailed
options. As it’s getting late, he asks for the details to be saved so everyone
can consider them tomorrow. The travel organizer emails them a summary
of the different options available.”
www.id-book.com 45

Scenario for skinput Scenarios and Personas

http://youtu.be/g3XPUdW9Ryg

www.id-book.com 47 www.id-book.com 48

12
 6/8/2020

Use case for travel organizer

Activity 10.3 for scenario 1. The system displays options for investigating visa and vaccination
requirements.
1. Hãy viết 1 kịch bản/ngữ cảnh về việc bạn đi chọn 2. The user chooses the option to find out about visa requirements.
mua một chiếc xe hơi mới. Có thể là mua 1 chiếc 3. The system prompts user for the name of the destination country.
hoàn toàn mới hoặc mua xe cũ. 4. The user enters the country’s name.
Trong lúc viết, hãy nghĩ các khía cạnh quan trọng 5. The system checks that the country is valid.
của việc bạn ưu tiên điều gì và thích cái gì (*). 6. The system prompts the user for her nationality.
7. The user enters her nationality.
2. Sau đó tưởng tượng ra một sản phẩm (có tính 8. The system checks the visa requirements of the entered country for a
tương tác) hỗ trợ bạn đạt được mục tiêu mua xe và passport holder of her nationality.
quan tâm đến những vấn đề bạn đặt ra (*). 9. The system displays the visa requirements.
3. Viết một kịch bản cho thấy sản phẩm đó hỗ trợ 10. The system displays the option to print out the visa requirements.
bạn như thế nào. 11. The user chooses to print the requirements.

www.id-book.com 49 www.id-book.com 50

Alternative courses for travel organizer Example use case diagram for travel organizer
Some alternative courses:

6. If the country name is invalid:

6.1 The system displays an error message.
6.2 The system returns to step 3.
8. If the nationality is invalid:
8.1 The system displays an error message.
8.2 The system returns to step 6.
9. If no information about visa requirements is found:
9.1 The system displays a suitable message.
9.2 The system returns to step 1.
www.id-book.com 51 www.id-book.com 52

13
 6/8/2020

Activity 10.4 for use case Essential Use Cases (task case)
Ví dụ về dịch vụ cho thuê phim. Một use case
là “thuê phim” và nó liên quan đến actor • To combat the limitation of scenarios and
Subcriber. use case
1. Hãy xác định một actor quan trọng khác và • Task case represent abstractions from
một use case có liên quan; và vẽ một biểu scenarios
đồ use case cho dịch vụ thuê phim.
2. Liệt kê use case “thuê phim” bao gồm các
normal course và alternative course nào. Có
thể giả thiết normal case là cho user vào
website để tìm kiếm phim theo đạo diễn.
www.id-book.com 53 www.id-book.com 54

Example essential use case for retrieving visa

requirements in travel organizer Activity 10.5 for essential use case

Hãy xây dựng một essential use case (task

case) cho user role “Subscriber” của dịch vụ
thuê phim đã được đề cập trong activity
trước.

www.id-book.com 55 www.id-book.com 56

14
 6/8/2020

10.7 Task analysis Hierarchical Task Analysis

• Task descriptions are not used to envision new systems or
devices • Involves breaking a task down into subtasks, then sub-
sub-tasks and so on. These are grouped as plans which
• Task analysis is used mainly to investigate an existing specify how the tasks might be performed in practice
situation

• It is important not to focus on superficial activities • HTA focuses on physical and observable actions, and
includes looking at actions not related to software or an
– What are people trying to achieve? interaction device
– Why are they trying to achieve it?
• Start with a user goal which is examined and the main
– How are they going about it?
tasks for achieving it are identified
• Many techniques, the most popular is Hierarchical Task
Analysis (HTA) • Tasks are sub-divided into sub-tasks

www.id-book.com 57 www.id-book.com 58

Example Hierarchical Task Analysis

Example Hierarchical Task Analysis
(graphical)
0. In order to buy a DVD
1. locate DVD
2. add DVD to shopping basket
3. enter payment details
4. complete address
5. confirm order

plan 0: If regular user do 1-2-5.

If new user do 1-2-3-4-5.
www.id-book.com 59 www.id-book.com 60

15
 6/8/2020

Summary
Activity 10.6 for HTA • Getting requirements right is crucial

• There are different kinds of requirement, each is

Xét ví dụ về công ty tổ chức du lịch. significant for interaction design

Hãy thực hiện HTA với mục đích xác định • The most commonly-used techniques for data
gathering are: questionnaires, interviews, focus
vacation của người dùng sẽ có những gì. groups, direct observation, studying documentation
and researching similar products
HTA phải bao gồm plan.
• Scenarios, use cases and essential use cases can be
Diễn đạt sự phân tích tác vụ bằng văn bản used to articulate existing and envisioned work
và đồ họa. practices.

• Task analysis techniques such as HTA help to

investigate existing systems and practices
www.id-book.com 61 www.id-book.com 62

16