Appendix O: List of Metrics

The following information can be used to structure your policies. See Chapter 16 for more information.

Requirements Management (RM) Policy

1.0 Purpose

The purpose of Requirements Management (RM) is to manage the requirements of the project's products and product components and to identify inconsistencies between those requirements and the project's plans and work products.

2.0 Scope

This policy applies to software projects within the xxx Division of the xxx organization. The term "project," as used in this policy, includes system and software engineering, maintenance, conversion, enhancements, and procurement projects.

3.0 Responsibilities

The project manager shall ensure that the RM process is followed. Each project will follow a process that ensures that requirements will be documented, managed, and traced.

4.0 Verification

RM activities will be reviewed with higher-level management, and the process will be objectively evaluated for adherence by the Quality Assurance (QA) staff.

5.0 Sign-offs

The following shall review and approve this policy:

• Associate Director

• Quality Assurance

• EPG Chairman