CS 426 Senior Projects. Chapter 3: The Requirements Workflow [Arlow & Neustadt, 2005] January 26, 2011. Outline. The requirements workflow Metamodel for software requirements Requirements workflow details The importance of requirements Defining requirements. The Requirements Workflow.
Chapter 3: The Requirements Workflow
[Arlow & Neustadt, 2005]
January 26, 2011
Fig. 3.2 [Arlow & Neustadt 2005] shows that most of the work
in requirements workflow occurs in Inception and Elaboration phases
Arlow & Neustadt’s approach for requirements engineering is shown in
Fig. 3.3 [Arlow 2002]. Details can be found in Section 3.3
Specific tasks for UP (Unified Process) requirements workflow
Fig. 3.4 [Arlow & Neustadt 2005]
Arlow and Neustadt extend slightly the UP requirements workflow with
the addition of new tasks: find functional requirements, find non-
functional requirements, prioritize requirements, &trace requirements
to use cases. As such, non-functional requirements can be addressed
as well, along with the traditional UP/UML treatment of functional
requirements via use cases. Fig. 3.5 [Arlow & Neustadt 2005]
<id> The <system> shall <function>
1 The ATM shall check the validity of the ATM card inserted.
2 The ATM shall validate the PIN number entered by the client.
3 The ATM shall dispense no more than $500 against any ATM card in any 24-hour period
1 The ATM shall be written in C++.
2 The ATM shall validate the PIN in three seconds or less.