Quiz7 Flashcards
statement about
an intended product that specifies
what it should do or how it should
perform. One of the aims of the
requirements activity is to make the
requirements as specific,
unambiguous, and clear as possible.
A Repwuirement
requirement for a word processor might be that it must be able to
run on a variety of platforms such as PCs, Macs and Unix machines.
Non functional requirement
capture what the product should do.
Functional requirements
capture the type, volatility, sizelamount, persistence, accuracy, and value of the
amounts of the required data.
Data requirements
refer to the circumstances in which
the interactive product will be expected to operate. Four aspects of the environment
must be considered when establishing requirements.
Environmental requirements
how much lighting, noise, and dust is
expected in the operational environment
Physical environment
The issues raised in
Chapter 4 regarding the social aspects of interaction design, such as collaboration
and coordination, need to be explored in the context of the current development.
Social environment
how good is user support
likely to be, how easily can it be obtained
Organizational environment
Environmental requirements types of environments
Physical, social, organizational, technical environments
capture the characteristics of the intended user group. But in addition to these, a
user may be a novice, an expert, a casual, or a frequent user.
User requirements
capture the usability goals and associated measures for a
particular product. Usability requirements are related to other kinds of requirement
we must establish, such as the kinds of users expected to interact with the product.
Usability requirements
Data gathering
Questionnaires, interviews, focus groups and workshops, naturalistic observations, studying documentation,
3 types of task description
Scenarios, use cases, essential use cases
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.
Scenarios
also focus on user goals, but
the emphasis here is on a user-system
interaction rather than the user’s task
itself
Use cases
a structured
narrative consisting of three parts: a
name that expresses the overall user
intention, a stepped description of user
actions, and a stepped description of
system responsibility.
Essential use cases
involves breaking a task down into subtasks and then
into sub-subtasks and so on. These are then grouped together as plans that specify
how the tasks might be performed in an actual situation
Hierarchical task analysis
focuses on the physical and observable actions that are performed, and includes
looking at actions that are not related to software or an interaction device at all. The
starting point is a user goal. This is then examined and the main tasks associated
with achieving that goal are identified. Where appropriate, these tasks are
subdivided into subtasks.
Hierarchical task analysis
