Analisis De Sistema

Requirements Management Plan

Version 1.1

Revision History
|Date |Version |Description |Author |
|25/Jan/2002 |1.0 |Inception |p murphy |
|22/Apr/2002 |1.1|Incorporated input from product management |h moriyuke |
| | | | |
| | | | |

Table ofContents

1. Introduction 4
1.1 Purpose 4
1.2 Scope 4
1.3 Definitions, Acronyms, and Abbreviations 4
1.4 References 4
1.5 Overview 4

2. Requirements Management 4
2.1 Organization, Responsibilities, and Interfaces 4
2.2 Contact Table 5

3. Requirements Artifacts 6
3.1 Artifact Description 6
3.1.1 Document Types 6
3.1.2 Requirement Types 63.1.3 Attributes 6
3.1.4 Attribute Values 9
3.2 Traceability 10
3.2.1 Traceability Criteria for Requirement Types 10
3.3 Reports and Measures 11

4. Requirements Change Management 12
4.1 Change Request Processing and Approval 12
Requirements Management Plan

Introduction

1 Purpose

The purpose of this plan is to establish and document howrequirements for the ClassicsCD.com project will be documented and tracked.

2 Scope

This plan provides guidelines for the management of the Classics CD online CD purchasing system project.

3 Definitions, Acronyms, and Abbreviations

For common vocabulary for this project, please refer to the Glossary document in the project.

4 References

Sample RM plans on the RationalDeveloper Network at www.rational.net

Kruchten, Philippe. 1999. The Rational Unified Process. Menlo Park, CA: Addison Wesley

Leffingwell, D. and Don Widrig. 2000. Managing Software Requirements. Menlo Park, CA: Addison Wesley.

Spence, I. and L. Probasco. 1998. Traceability Strategies for Managing Requirements with Use Cases. Cupertino, CA: Rational Software Corporation.Available at www.rational.net.

The ClassicsCD Change Management Plan. For access and information, consult with Xavier Sanchez-Tobar, Change Control Manager, at xtobar@classicscd.com

5 Overview

This document contains specific details and strategies for managing the requirements of the ClassicsCD.com project. The document details how requirements are organized and administratedwithin our project. It also describes how requirements will be tracked using attributes and traceability links to other requirements.

This document also describes the change management process adopted for this project.

This document specifies milestones to be reached and standards to be adhered to so that we can ensure and evaluate fulfillment of the requirements we specify.Requirements Management

1 Organization, Responsibilities, and Interfaces

|Role |Responsibility |
|Project manager |The role with overall responsibility for the project. The Project Manager needs to ensure that tasks are |
| |scheduled, allocated, andcompleted in accordance with project schedules, budgets, and quality requirements.|
|Quality assurance |The function of Quality Assurance is the responsibility of (reports to) the Project Manager and is |
|(QA) |responsible for ensuring that project standards are correctly and verifiably followed by all project staff. |
|Developer |A person responsible for...