rup requirements rup artifacts and deliverables rup requirements workflow

RUP Requirements

• RUP Artifacts and Deliverables

• RUP Requirements Workflow

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.

Requirements Workflow

Analyze the Problem - Purpose

• Gain agreement on the problem being solved,

• Identify stakeholders,

• Define the system boundaries, and

• Identify constraints imposed on the system

Analyze the Problem Workflow

Vision Document

1. Introduction 2. Positioning 3. Stakeholder and User Descriptions 4. Product Overview 5. Product Features 6. Constraints 7. Quality Ranges8. Precedence and Priority9. Other Product Requirements10. Documentation Requirements 11. Appendix 1 - Feature Attributes

Vision Document Positioning

• Business Opportunity

• Problem Statement

• Positioning Statement

Sample Problem Statement

The problem of The outdated and largely manual student registration process at Wylie College affects Students, professors, and College administration. The impact of which is A slow and costly process combined with dissatisfied students and professors. A successful solution would Improve the image of the College, attract more students, and streamlin e administrative registration functions.

Sample Position Statement

For Wylie College students, professors, and the course registrar Who Attend, teach, or administer college courses The Course Registration System Is a tool That Enables online course registration and access to course and grade information Unlike The existing outdated mainframe registration system Our product Provides up -to-date information on all courses, registrations, teachers, and grades to all users from any PC connected via the College LAN or internet.

Use Case Diagram

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

Product Requirements Attributes

• Status

• Benefit

• Effort

• Risk

• Target Release

• Assigned To

Use Case Requirements Attributes

• Status

• Priority

• Effort Estimate

• Technical Risk

• Target Development Iteration

• Assigned To

• Rose model

Test Requirements Criteria

• Test Status

• Build Number

• Tested By

• Date Tested

• Test Notes

Requirements Workflow

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

Stakeholder Needs Workflow

Requirements Workflow

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.

Define the System Workflow

Use Case Diagram

Sample Sequence Diagram

: Student : System

Start System

Display Login Screen

Enter User Name

Enter Password

Submit Login Information

Display Login Successful

Requirements Workflow

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.

Manage Scope Workflow

Requirements Workflow

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.

Refine the System Workflow

Login Use Case Report

1. Brief Description

2. Flow of Events

3. Special Requirements

4. Pre-Conditions

5. Post-Conditions

6. Extension Points

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.

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.

RUP Use Case Storyboard

• Flow of Events – Storyboard

• Interaction Diagrams

• Class Diagrams

• Usability Requirements

• Reference to User Interface Prototype

• Trace Dependency

RUP User Interface Prototype

• Paper sketches or pictures;

• Bitmaps from a drawing tool;

• An interactive executable prototype (e.g., in Microsoft®Visual Basic®).

Requirements Workflow

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.

Manage Changing Requirements Workflow

Requirements Activity Overview

Requirements Artifact Overview

Questions?