1. Overview

2. Objectives

3. Identification of Requirements Scope

4. Roles and Responsibilities

4.1. Program Manager

4.2. Configuration Manager (CM)

4.3. Customer

4.4. QA/Test Manager

4.5. Configuration Control Board (CCB)

5. Processes and Procedures

5.1. Identification of Requirements

5.2. Recording Requirements

5.3. Modification of Requirements

5.4. Reconciling Requirements for Final Product Delivery

6. Requirements Management Tools

6.1. Requirements Tracking Matrix

6.2. Requirements Project File

7. Schedule

REQUIREMENTS MANAGEMENT PLAN

1. 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.

2. Objectives

• Identify scope of what is managed. (3.0)

• Identify Roles and Responsibilities of those involved in this management process. (4.0)

• Describe the processes and procedures to be used during this management process. (5.0)

• Identify the tools to be used. (6.0)

3. 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).

4. Roles and Responsibilities

4.1 Program Manager

The Program Manager is responsible for working with the customer to identify all requirements; is responsible for submitting the customer's requirements to the Configuration Control Board for analysis and impact; is responsible for communicating requirements impact to the customer; is responsible for negotiating requirements modification when needed; and is responsible for delivery of the Test Analysis Report to the customer.

4.2 Configuration Manager (CM)

The CM is responsible for maintaining a matrix of all customer approved requirements; is responsible for oversight of the requirements change control process; is responsible for applying changes to requirements matrix; is responsible for maintaining the modification history of requirements.

4.3 Customer

The customer is responsible for defining and approving all requirements, and all modification to requirements.

4.4 QA/Test Manager

The QA/Test Manager is responsible for verifying that the delivered product satisfies the approved requirements; is responsible for documenting the results of the requirements verification in a Test Analysis Report.

4.5 Configuration Control Board (CCB)

The CCB, which is composed of all members of the MJY Team, is responsible for analyzing and evaluating requirements for feasibility and impact to the project.

5. Processes and Procedures

5.1 Identification of Requirements

5.1.1 The Program Manager will confer with the customer to identify the structure of the delivered product, the desired functionality of the product, and any performance issues.

5.1.2 The Program Manager will present the customer's requirements to the CCB for feasibility evaluation.

5.1.3 The Program Manager will meet with the customer 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 customer's approval for the requirements to be implemented.

5.2 Recording Requirements

5.2.1 The Program Manager will deliver to CM the requirements approved by the customer.

5.2.2 CM will number and enter each requirement into a requirements tracking matrix.

5.2.3 CM will keep a project requirements file containing documentation of customer approved requirements, and customer approved modifications to requirements.

5.3 Modification of Requirements

5.3.1 Instituted by the Customer

5.3.1.1 The Program Manager will receive direction from the customer to modify a requirement. The Program Manager will present the request to the CCB for feasibility analysis and project impact.

5.3.1.2 Program Manager will inform the customer of project impact before modifications are implemented.

5.3.1.3 CM will incorporate the approved requirement modification into the requirements tracking matrix, and add the modification request to the Requirements Project File.

5.3.1.4 Approved modification will then be implemented by the project team.

5.3.2 Instituted by Project Team

5.3.2.1 Requirement modification requests must be present to the CCB for analysis.

5.3.2.2 If the CCB agrees to the modification request, the Program Manager will present request to the customer.

5.3.2.3 If the modification is approved by the customer, CM will incorporate the modification into the requirements tracking matrix, and a record of the modification approval will be added to the Requirements Project File.

5.3.2.4 The modification will then be implemented by the project team.

5.4 Reconciling Requirements for Final Product Delivery

5.4.1 The Testing Manager will use the requirements tracking matrix to verify that all approved requirements have been met.

5.4.2 The QA/Test Manager will compile a brief Test Analysis Report to address the products conformity to all approved requirements.

5.4.3 The Program Manager will present the Test Analysis Report to the customer with the delivery of the product.

5.4.4 The QA/Test Manager will give a copy of the Test Analysis Report to CM for inclusion in the Requirements Project File.

6. Requirements Management Tools

6.1 Requirements Tracking Matrix -

Microsoft Excel

6.2 Requirements Project File -

Paper files

7. Schedule