Software Configuration Managment: Configuration Identification of Software Configuration Items

Some good Policies for Configuration Identification of Software Configuration Items will greatly improve the success of your software archive. Suggested policies include:

1. Each application software configuration item must have a specification document, the following are recommended for discussion:

• Business Need/Requirements Statement
• Software Requirements Specification
• Software Design Description
• Source Code/Executable Code
• Test Plan Procedure
• Software User Manual and Run Book
• Training Plan
• Software Product Specification

2. Application software specifications should be contained in separate documents.

3. Each application software specification will be baselined (as part of the Allocated Baseline) and subject to formal change control.

4. Application software specifications should be traceable to the system-level requirements specification.

5. The content of the application software specification establishes the acceptance criteria for that software configuration item.

6. Each application software specification will be numbered with the configuration items identifier as part of the document number, for example, the specification for application software configuration item XYZ Project will be XYZ Project-SPEC.

7. The naming convention used applicable to application software configuration items is to have a maximum of the first six characters be the CI number; for example, XYZ Project-OPEN-WINDOW links the open window module to the XYZ Project CI.