Requirements Management Plan - Documents

Author: Oldřich VašutCourse: SAN 2008

OutlineOutline

• Introduction• What is RM Plan?• RM Plan description, relationships to other

plans• Documents

• Requirements management involves establishing and maintaining agreement between customer and developer on both technical and non-technical requirements. This agreement forms the basis for estimating, planning, performing, and tracking project activities throughout the project and for maintaining and enhancing developed software.

Introduction to Introduction to Requirements ManagementRequirements Management

Introduction to RMIntroduction to RM - Key activities - Key activities

• planning the requirements phase • establishing the requirements process • controlling requirements changes • minimizing the addition of new requirements (scope

creep) • tracking progress • resolving issues with customers and developers • holding requirements reviews

Requirements Management PlanRequirements Management Plan

• A requirements management plan is a component of the project management plan. Generally, the purpose of RM is to ensure customer and developer have a common understanding of what the requirements for an undertaking are. Several subordinate goals must be met for this to take place: in particular, requirements must be of good quality and change must be controlled. The plan documents how these goals will be achieved. Depending on your project standards, a variety of sections might be included in your RM plan.

Sections of RM PlanSections of RM Plan

• introduction to RM and document overview • document scope • issues affecting implementation of the plan, such as training on

the RM tool • applicable documents, such as policies and standards • terms and definitions used in the plan - if your use of the term

“requirement” includes several requirement categories, define it here

• methods and tools that will be used for the RM process (or the requirements for selecting a tool if one is not selected)

• the RM process, including any diagrams of the process • authorities and responsiblities of participants • strategy for achieving requirement quality, including traceability

and change control

Relationship to other Relationship to other plansplans

The following is a mapping of Requirements Management Plan sections to artifacts that may contain complementary information:

Requirements Management Plan Section Complementary Artifact

Definitions, Acronyms, and Abbreviations  Glossary 

Organization, Responsibilities, and Interfaces  Software Development Plan 

Tools, Environment, and Infrastructure Development Case, Software Development Plan

(Infrastructure Plan) 

Requirements Identification  Configuration Management Plan 

Traceability  Development Case, Measurement Plan 

Attributes  Development Case, Measurement Plan 

Reports  Development Case, Measurement Plan 

Requirements Change Management  Configuration Management Plan 

Workflows and Activities  Development Case 

Milestones  Software Development Plan, Iteration Plan 

Training and Resources  Software Development Plan 

Document based Requirement Document based Requirement Artifacts and TypesArtifacts and Types

• Vision (VIS) – Stakeholder Need (NEED), Product Feature (FEAT)

• Glossary (GLS) – Term (TERM)• Business Rule Reference (BR) – Business Rule (BR)• Use-Case Model Survey• Use-Case Specification (UC) – Use-Case Detail Requirement

(UCDR)• Supplementary Specification (SS) – Supplementary

Requirement (SUPP)• Test Plan (TPL) – Test Plan Requirement (TPR)• Test Case (TC) – Test Requirement (TR)• Issues (ISU) – Issue (ISS)• Assumptions (ASM) – Assumption (ASM)

Traceability Traceability CriteriaCriteria

This trace is implied by a relationship to a test script which contains the verification and is under the control of Rational TestManager

Note: This tracability link is optional as ift can be derived from the link between the Product Feature and Use Case Section. This link is often used to relate the Product Features to the Use Cases before the Use Case Sections are written.

Issue

Assumption

Glossary

+definition

Supporting Document

Business Rule

+definition

the great indoors - Requirements Traceability Diagram Created: 29 Feb. 2000 by Stephen Hunt, Rational Software

Impacted Group

Stakeholder

Stakeholder Need

Verification Point

Supplemental Requirement

Test Requirement

1..* 1..*

1..* 1..*

Test Plan Requirement

Product Feature

1..* 1..*

Actor Use Case Detail Requirement

1..* 1..*

1..* 1..*

Use Case

1..*

1

1..*

1

Design

+Lower Element

• 1. Introduction1.1 Purpose1.2 Scope1.3 Definitions, Acronyms, and Abbreviations1.4 References1.5 Overview

• 2. Requirements Management• 2.1 Organization, Responsibilities, and Interfaces• 2.2 Tools, Environment, and Infrastructure• 3. The Requirements Management Program• 3.1 Requirements Identification• 3.2 Traceability

3.2.1 Criteria for <traceability item>• 3.3 Attributes

3.3.1 Attributes for <traceability item>• 3.4 Reports and Measures• 3.5 Requirements Change Management

3.5.1 Change Request Processing and Approval3.5.2 Change Control Board (CCB)3.5.3 Project Baselines

• 3.6 Workflows and Activities• 4. Milestones• 5. Training and Resources

RM Plan TemplateRM Plan Template

ReferencesReferences

• Requirements Management Plan Example http://www.ibm.com/developerworks/rational/library/4421.html

• REQUIREMENTS MANAGEMENT PLAN http://www.baz.com/kjordan/swse625/htm/rm_plan3.htm

• REQUIREMENTS MANAGEMENT http://www.jiludwig.com/Requirements_Management.html

• Requirements Management – SRM http://www.akamonitor.cz/2007/08/sprva-poadavk-v-studijnm-plnu-manaersk.htm

• Requirements Management Plan Template https://cabig.nci.nih.gov/workspaces/TBPT/Templates/caBIG_Reqts_%20Mgt_Plan.doc

EndEnd

• Thanks for favour.