Data Interpretation and Analysis

 first data-gathering session has been conducted, interpretation and analysis

can begin.
 start interpretation as soon after the gathering session as possible.
 It is also a good idea to discuss the findings with others to get a variety of
perspectives on the data.
The aim of the interpretation is to begin structuring and recording
descriptions of requirements.

1
Task Description

 There are different flavors of task descriptions, three of

them here: scenarios, use cases, and essential use cases.
 Each of these may be used to describe either existing tasks or envisioned tasks
with a new device.
 They are not mutually exclusive and are often used in combination to capture
different perspectives or to document different stages during the development
lifecycle.

2
 Scenarios
A scenario is an "informal narrative description“.
 It describes human activities or tasks in a story that allows exploration and
discussion of contexts, needs, and requirements.
 It does not explicitly describe the use of software or other technological
support to achieve a task .

3
 Use cases
focus on user goals, but the emphasis here is on a user-system
interaction rather than the user's task itself

 Essential use cases

the limitations of both scenarios and use cases
represent abstractions from scenarios

4
5
6
7
8
9
10
11
12
13
14
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31