CS 691z / 791z Topics on Software Engineering. Software Requirements Based on Chapter 3: The Requirements Workflow [Arlow & Neustadt, 2002] February 6, 2007. Outline. Requirements: The requirements workflow Metamodel for software requirements Requirements workflow details
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Based on Chapter 3: The Requirements Workflow
[Arlow & Neustadt, 2002]
February 6, 2007
Fig. 3.2 [Arlow & Neustadt, 2002] 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 2002]
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 2002]
<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.
1 The ATM shall be written in C++.
2 The ATM shall validate the PIN in three seconds or less.