Requirements Management OverviewNIGMS Software Development

Agenda/Overview Purpose and importance of

requirements Requirements management process Project artifacts Tools Case study

What is Requirements Management?

Requirements Management is a systematic approach to eliciting, organizing, documenting, and targeting system requirements

Descriptions of necessary system functionality

Descriptions of how the system should respond to user interactions

Constraints on system design

Requirements vs. design decisions Allows flexibility Reduces overhead

What Are Requirements?

To... Establish agreement with the

stakeholders on what the system must do Provide system developers with an

understanding of the functionality a system must provide

Provide a basis for planning development Provide a means of measuring progress

and success

Purpose of Requirements

Kinds of Requirements

System Vision

Use Case Specification

Supplemental Specification

Stakeholder Needs

Functional Requirements

Global and Non-functional Requirements

Use Cases Provide description of system behavior Give context to functional requirements Supported by supplemental specs to

capture non-functional requirements Use case example (following page)

Importance of Managing Requirements Common causes for failure

Poor stakeholder involvement Unclear vision and objectives Changing requirements

Requirements errors are costly Need to reduce errors Need to find errors sooner Need to reduce cost of change

Approach and Traceability Agree on scope for current release Document and implement in-scope

requirements Changes may affect schedule

Record out of scope requirements for future releases May be identified during any stage of

development or operations

Process Flow

Input

Need Identified Disposition Request Assign Resources

RA

Preliminary Requirements Gathered

PM

Conduct PCRB

RA

Detailed Requirement(s) Finalized

RA

Document Requirement(s)

Output

Code Developed Based on Requirements

This Includes:Technical Meetings

NegotiationsRisk Identification

Customer Needs DocumentedFeatures Documented

PrioritizationTargeting

Screen ShotsMock-upsWireframe

(visual aids)

Prioritization and Targeting Activities

RUP Phase Color-Code Legend

Inception Elaboration Construction

Mapping RUP to EPLC

TransitionInception ConstructionElaborationCPIC

Pre-Select phase

RUP Phases

EPLC Phases

InceptionConcept

DevelopmentPlanning

Requirements Definition

Design DevelopmentIntegration &

TestImplemen-

tationOperations & Maintenance

Disposition

Preliminary Draft Version

 

Final BaselinedVersion

 

Artifacts / Phase Inc El Con Tran

Vision        

Use Case Summary        

Use Case    

Supplemental Specs        

UI Prototype        

Software Architecture Document      

Data Model (Logical & Physical)

PIA        

System Executables        

Test Plans        

TAR        

ISDS Project DeliverablesArtifacts / Phase Inc El Con Tran

UAT

Deploy Plan        

User Guide        

Training Material        

Security Plan

CM Plan        

SVD

Project Plan        

Project Schedule

Risk Plan        

Baselining vs. gate reviews

Requisite Pro Store current

requirements Store working

documents Rational Clear

Quest Track work flow Store future

requirements

Rational Clear Case Manage versions Publish baselined

documents Rational Rose

Modeling & Design

Requirements Tools

CMR Meeting Support System (CMS2) Case Study

Putting it All Together

Requirements Management Success Delivered critical functionality

On time Within budget

Stakeholder satisfaction Positioned for future enhancements

CMS2 Inception Stakeholder needs Schedule driven Agreement on scope Vision & Use Case Summary

CMS2 Elaboration Gathering of detailed requirements Mock-ups & wire-frames Current requirements in Req Pro

Use case specifications Supplemental specifications

Future requirements in Clear Quest

CMS2 Construction Documents baselined into Clear Case Code created using Clear Case for CM Initial functionality split

Core functionality readied for original date

Additional requirements targeted for enhancement release (in Clear Quest)

CMS2 Transition Testing using test manager

Link to Req Pro with new version Demo to users and service desk User acceptance testing (UAT)

Defects remedied immediately New requirements entered in CQ

Operations and future releases Enhancements vs. defects Enhancement requests in CQ

Enhancements for Version 1.1

Future Enhancement Requests

Wrap Up ... Q & A