Please enable JavaScript.
Coggle requires JavaScript to display documents.
10 - Establishing Requirements (Task Description Types (Scenarios ('…
10 - Establishing Requirements
Task Description Types
Scenarios
'Informal narrative description'; it describes human activities or tasks in a story that allows exploration and discussion of contexts, needs and requirements
Use Cases
Also focus on user goals, but the emphasis here is on a user-system interaction rather than the user's task itself
Essential Use Cases or Task Cases
Structured narrative consisting of three parts
A name that expresses the overall user intention
A stepped description of user actions
A stepped description of system responsibilities
What, How & Why?
What
To understand as much as possible about the users, their activities, and the context of that activity
To produce a set of stable requirements that form a sound basis to start designing
A requirement is a statement about an intended product that specifies what it should do or how it should perform
How
First gather some data, then analyze and interpret it, and then extract some requirements from it
Why
There is a significant cost for fixing errors late in the software development cycle rather than early
The term 'establishing requirements' was chosen to represent the fact that requirements have been established from a sound understanding of the users' needs and that they can be justified by and related back to the data collected
Data Gathering for Requirements
The overall purpose of data gathering in the requirements activity is to collect sufficient, relevant, and appropriate data so that a set of stable requirements can be produced
Hierarchical Task Analysis
HTA was originally designed to identify training needs; it involves breaking a task down into subtasks and then into sub-subtasks and so on