Disciplines > Configuration & Change Management > Concepts > Configuration Status Reporting
Configuration Status Accounting (Measurement) – is used to describe the ‘state’ of the product based on the type, number, rate and severity of defects found, and fixed, during the course of product development. Metrics derived under this aspect of Configuration Management are useful in determining the overall completeness status of the project.
The four principle sources for software Configuration Status Reports are:
A Change Request (CR) is a general term for a request to change an artifact or process. The general process associated with CRs is described in Concepts: Change Request Management.
The status ‘tags’ provide the basis for reporting CR (aging, distribution or trend) statistics as described in the CRM process steps.
Change Request based defect reports fall under the following categories:
Build Reports list all the files, their location, and incorporated changes that make up a build for a specific version of the software.
Build Reports can be maintained both at the system and subsystem level.
Similar to Release Notes, Version Descriptions describe the details of a software release. As a minimum the description needs to include the following:
There two kinds of audits that are covered in the context of Configuration Management:
A Physical Configuration Audit (PCA) identifies the components of a product to be deployed from the Project Repository.
A Functional Configuration Audit (FCA) confirms that a baseline meets the requirements targeted for the baseline.
The detailed activity for performing Audits is described in Perform
Rational Unified Process