Artifacts > Requirements Artifact Set > {More Requirements Artifacts} > Requirements Management Plan


Requirements Management Plan
Describes the requirements documentation, requirement types, and their respective requirements attributes, specifying the information and control mechanisms to be collected and used for measuring, reporting, and controlling changes to the product requirements. 
Role: System Analyst
Enclosed in: Software Development Plan
Templates:
Examples:
More Information:

Input to Activities: Output from Activities:

Purpose To top of page

A Requirements Management Plan should be developed to specify the information and control mechanisms that will be collected and used for measuring, reporting, and controlling changes to the product requirements. 

The purpose of the Requirements Management Plan is to describe how the project will set up requirements documents and requirement types, and their respective requirement attributes and traceability.  

Timing To top of page

The Requirements Management Plan is developed during the Inception phase and is updated at each major milestone.

ResponsibilityTo top of page

The System Analyst is responsible for creating the Requirements Management Plan.

Tailoring To top of page

Tailoring should, at a minimum, include defining the traceability items, constraints, and attributes applicable to your project.  Other significant traceability concerns include:

  • relationship to other plans
  • tool considerations

Relationship to Other PlansTo top of page

The Requirements Management Plan contains information that may be covered to a greater or lesser extent by other plans.  The following approaches can be used to handle this potential overlap:

  • Reference the content in another plan.
  • Provide the overview in another plan and provide greater detail in this plan. References from these other plans to the Requirements Management Plan may be useful.  This often works well on large projects with a separate organization that is responsible for managing requirements.
  • Tailor the document sections to cover only those areas that are not covered elsewhere.

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

Tool ConsiderationsTo top of page

Rather than document the traceability attributes and their usage into a formal Requirements Management Plan, you may choose to enter this information directly into an online help tool or Web site, or into the tool that you use for managing attributes and traceability.

The Requirements Management Plan is often used to document more than just traceability items.  For example, users of Rational RequisitePro often use this document to capture other items managed by the tool, such as action items, glossary terms, and so forth.

Copyright  1987 - 2001 Rational Software Corporation


Display Rational Unified Process using frames

Rational Unified Process