(Z)<RUP>Requirements Management Plan-优快云博客

Requirements Management Plan

<o:p> </o:p>

Version <1.0><o:p></o:p>

<o:p> </o:p>

[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).]

[To customize automatic fields in Microsoft Word (which display a gray background when selected), select File>Properties and replace the Title, Subject and Company fields with the appropriate information for this document. After closing the dialog, automatic fields may be updated throughout the document by selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field and press F9. This must be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and the field contents. See Word help for more information on working with fields.]

Revision History

Date<o:p></o:p>	Version<o:p></o:p>	Description<o:p></o:p>	Author<o:p></o:p>
<dd/mmm/yy>	<x.x>	<details>	<name>
<o:p> </o:p>	<o:p> </o:p>	<o:p> </o:p>	<o:p> </o:p>
<o:p> </o:p>	<o:p> </o:p>	<o:p> </o:p>	<o:p> </o:p>
<o:p> </o:p>	<o:p> </o:p>	<o:p> </o:p>	<o:p> </o:p>

<o:p> </o:p>

Table of Contents

1. Introduction 2<o:p></o:p>

1.1 Purpose 2<o:p></o:p>

1.2 Scope 2<o:p></o:p>

1.3 Definitions, Acronyms, and Abbreviations 2<o:p></o:p>

1.4 References 2<o:p></o:p>

1.5 Overview 2<o:p></o:p>

2. Requirements Management 2<o:p></o:p>

2.1 Organization, Responsibilities, and Interfaces 2<o:p></o:p>

2.2 Tools, Environment, and Infrastructure 2<o:p></o:p>

3. The Requirements Management Program 2<o:p></o:p>

3.1 Requirements Identification 2<o:p></o:p>

3.2 Traceability 2<o:p></o:p>

3.2.1 Criteria for <traceability item> 2<o:p></o:p>

3.3 Attributes 2<o:p></o:p>

3.3.1 Attributes for <traceability item> 2<o:p></o:p>

3.4 Reports and Measures 2<o:p></o:p>

3.5 Requirements Change Management 2<o:p></o:p>

3.5.1 Change Request Processing and Approval 2<o:p></o:p>

3.5.2 Change Control Board (CCB) 2<o:p></o:p>

3.5.3 Project Baselines 2<o:p></o:p>

3.6 Workflows and Activities 2<o:p></o:p>

4. Milestones 2<o:p></o:p>

5. Training and Resources 2<o:p></o:p>

Requirements Management Plan

1. Introduction

[The introduction of the Requirements Management Plan provides an overview of the entire document. It includes the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Requirements Management Plan.]

1.1 Purpose

[Specify the purpose of this Requirements Management Plan.]

1.2 Scope

[A brief description of the scope of this Requirements Management Plan.]

1.3 Definitions, Acronyms, and Abbreviations

[This subsection provides the definitions of all terms, acronyms, and abbreviations required to properly interpret the Requirements Management Plan. This information may be provided by reference to the project’s Glossary.]

1.4 References

[This subsection provides a complete list of all documents referenced elsewhere in the Requirements Management Plan. Identify each document by title, report number if applicable, date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.]

1.5 Overview

[This subsection describes what the rest of the Requirements Management Plan contains and explains how the document is organized.]

2. Requirements Management

2.1 Organization, Responsibilities, and Interfaces

[Describe who is going to be responsible for performing the various activities described in the requirements workflows.]

2.2 Tools, Environment, and Infrastructure

[Describe the computing environment and software tools to be used in fulfilling the Requirements Management functions throughout the project or product lifecycle.

Describe the tools and procedures used to version control Requirements items generated throughout the project or product lifecycle.]

3. The Requirements Management Program

3.1 Requirements Identification

[Describe traceability items and define how they are to be named, marked, and numbered. (A traceability item is any project element that needs to be explicitly traced from another textual or model item in order to keep track of the dependencies between them. With respect to Rational Requisite Pro, this definition can be rephrased as: any project element represented within RequisitePro by an instance of a RequisitePro requirement type.)]

[For each type of requirement document or artifact in your project, list the traceability items contained in it and briefly explain what it is used for. You may also wish to list the responsible role.]

<o:p> </o:p>

Artifact<o:p></o:p> (Document Type)	Traceability Item<o:p></o:p>	Description<o:p></o:p>
Stakeholder Requests (STR)	Stakeholder Request (STRQ)	Key requests, including Change Requests, from stakeholders [If you use a Change Request Management tool, such as Rational ClearQuest, then stakeholder requests are often stored in that tool and not duplicated in the requirements management tool.]
Vision (VIS)	Stakeholder Need (NEED)	Key stakeholder or user need
Vision (VIS)	Feature (FEAT)	Conditions or capabilities of this release of the system
Use-Case Model	Use Case (UC)	Use cases for this release, documented in Rational Rose
Supplementary Specification (SS)	Supplementary Requirement (SUPP)	Non-functional requirements that are not captured in the use-case model