1. RUP Requirements RUP Artifacts and Deliverables
RUP Requirements Workflow

2. Purpose of Requirements
To establish and maintain agreement with the customers and other stakeholders on what the system should do.
To provide system developers with a better understanding of the system requirements.
To define the boundaries of (delimit) the system.
To provide a basis for planning the technical contents of iterations.
To provide a basis for estimating cost and time to develop the system.
To define a user-interface for the system, focusing on the needs and goals of the users.

3. Requirements Workflow

4. Analyze the Problem - Purpose
Gain agreement on the problem being solved,
Identify stakeholders,
Define the system boundaries, and
Identify constraints imposed on the system

5. Analyze the Problem Workflow

6. Vision Document Introduction Positioning
Stakeholder and User Descriptions
Product Overview
Product Features
Constraints
Quality Ranges
Precedence and Priority
Other Product Requirements
Documentation Requirements
Appendix 1 - Feature Attributes

7. Vision Document Positioning
Business Opportunity
Problem Statement
Positioning Statement

8. Sample Problem Statement

9. Sample Position Statement

10. Use Case Diagram

11. Requirements Management Plan
1. Objectives
2. Scope
3. References
4. Requirement Attributes
4.1. Attributes for Product Requirements
4.2. Attributes for Use Case Requirements
4.3. Attributes for Test Cases
5. Traceability Criteria
5.1. Criteria for Product Requirements
5.2. Criteria for Use Case Requirements
5.3. Criteria for Test Requirements

12. Product Requirements Attributes
Status
Benefit
Effort
Risk
Target Release
Assigned To

13. Use Case Requirements Attributes
Status
Priority
Effort Estimate
Technical Risk
Target Development Iteration
Assigned To
Rose model

14. Test Requirements Criteria
Test Status
Build Number
Tested By
Date Tested
Test Notes

15. Requirements Workflow

16. Understand Stakeholder Needs - Purpose
The purpose of this workflow detail is to collect and elicit information from the stakeholders of the project in order to understand what their needs really are.
The collected stakeholder requests can be regarded as a "wish list" that will be used as primary input to defining the high-level features of our system, as described in the Vision,b

17. Stakeholder Needs Workflow

18. Requirements Workflow

19. Define the System - Purpose
Align the project team in their understanding of the system.
Perform a high-level analysis on the results of collecting stakeholder requests.
Refine the Vision to include the features to include in the system, along with appropriate attributes.
Refine the use-case model, to include outlined use cases.
More formally document the results in models and documents.

20. Define the System Workflow

21. Use Case Diagram

22. Sample Sequence Diagram

23. Requirements Workflow

24. Manage Scope - Purpose
Prioritize and refine input to the selection of features and requirements that are to be included in the current iteration.
Define the set of use cases (or scenarios) that represent some significant, central functionality.
Define which requirement attributes and traceabilities to maintain.

25. Manage Scope Workflow

26. Requirements Workflow

27. Refine the System - Purpose
Describe the use case's flow of events in detail.
Detail Supplementary Specifications.
Develop a Software Requirements Specification, if more detail is needed
Model and prototype the user interface.

28. Refine the System Workflow

29. Login Use Case Report Brief Description Flow of Events
Special Requirements
Pre-Conditions
Post-Conditions
Extension Points

30. Login – Brief Description
This use case describes how a user logs into the Course Registration System.
The actors starting this use case are Student, Professor, and Registrar.

31. Login – Flow of Events 1. Basic Flow - Login
1.1. The system validates the actor’s password and logs him/her into the system.
1.2. The system displays the Main Form and the use case ends.
2. Alternative Flows
2.1. Invalid Name / Password - If in the basic flow the system cannot find the name or the password is invalid, an error message is displayed. The actor can type in a new name or password or choose to cancel the operation, at which point the use case ends.

32. RUP Use Case Storyboard
Flow of Events – Storyboard
Interaction Diagrams
Class Diagrams
Usability Requirements
Reference to User Interface Prototype
Trace Dependency

33. RUP User Interface Prototype
Paper sketches or pictures;
Bitmaps from a drawing tool;
An interactive executable prototype (e.g., in Microsoft®Visual Basic®).

34. Requirements Workflow

35. Manage Changing Requirements
Evaluate formally submitted change requests and determine their impact on the existing requirement set.
Structure the use-case model.
Set up appropriate requirements attributes and traceabilities.
Formally verify that the results of the Requirements workflow conform to the customer's view of the system.

36. Manage Changing Requirements Workflow

37. Requirements Activity Overview

38. Requirements Artifact Overview

39. Questions?