REQUIREMENTS MANAGEMENT PLAN

Overview

This plan documents the Requirements Management processes and procedures to be used by the MJY team during the planning and implementation of the Team Project for SWSE 625. This Plan defines how requirements will be recorded; how requirements will be modified; and how requirements will be reconciled for final delivery of the product.

Objectives

• Identify scope of what is managed.
• Identify Roles and Responsibilities of those involved in this management process.
• Describe the processes and procedures to be used during this management process.
• Identify the tools to be used.

Identification of Requirements

Scope

This Plan sets out the processes and procedures to be used during the planning and implementation of SWSE 625 - Team Project, by MJY Team. The overall objective of the team Project is to establish a web site that can be used as a resource for information concerning Software Project Management. The project requirements will define, in general terms, the setup of the web site, topics for available information concerning Software Project Management, and user activities (if any).

Roles and Responsibilities

Program Manager: is responsible for working with the client to identify all requirements; is responsible for submitting the client's requirements to the Configuration Control Board for analysis and impact; is responsible for communicating requirements impact to the client; and negotiating requirements modifications when needed.

Configuration Manager (CM): is responsible for maintaining a matrix of all client approved requirements; is responsible for oversight of the requirements change control process; is responsible for applying changes to the requirements matrix; is responsible for maintaining the modification history of requirements.

Client: is responsible for defining and approving all requirements, and all modifications to requirements.

Configuration Control Board (CCB): is responsible for analyzing and evaluating requirements for feasibility and impact to the project.

Processes and Procedures

Identification of Requirements:

1. The Program Manager will confer with the client to identify the structure of the delivered product, the desired functionality of the product, and any performance issues.
2. The Program Manager will present the client's requirements to the CCB for feasibility evaluation.
3. The Program Manager will meet with the client to review the CCB's findings and negotiate any changes to requirements as a result of the CCB's findings. The Program Manager will obtain the client's approval for the requirements to be implemented.

Recording Requirements:

1. The Program Manager will deliver to the CM the requirements approved by the client.
2. The CM will enter and number each requirement into a requirements tracking matrix.
3. The CM will keep a project requirements file containing documentation for client approved requirements, and client approved modifications to requirements.

Modification of Requirements:

Instituted by the Client -

1. The Program Manager will receive direction from the client to modify a requirement. The Program Manager will present the request to the CCB for analysis of feasibility and project impact.
2. The Program Manager will inform the client of project impact before modifications are implemented.
3. The CM will incorporate the approved requirement modification into the requirements tracking matrix, and add the modification request to the Requirements Project File.
4. Approved modifications will then be implemented by the project team.

Instituted by the Project Team -

1. Request must be presented to the CCB for analysis.
2. If the CCB agrees to the modification request, the Program Manager will present the request to the client.
3. If the modification is approved by the client, the CM will incorporat the modification into the requirements tracking matrix, and a record of the modification approval will be added to the Requirements Project File.
4. The modification will then be implemented by the project team.

Reconciling Requirement for Final Product Delivery:

1. The Testing Manager will use the requirements tracking matrix to verify that all approved requirements have been met.
2. A brief Test Analysis Report should be compiled to address the product's conformity to all approved requirements.
3. This report will be presented to the client with the delivery of the product.
4. A copy of this report will be given to the CM for inclusion in the Requirements Project File.

Requirements Management Tools

1. Requirements Tracking Matrix - Microsoft Excel
2. Requirements Project File - Paper files