Artifact: Configuration Audit
Findings
|
The Configuration Audit Findings identify a baseline, any missing required artifacts, and incompletely tested or failed requirements. |
|---|---|
| Role: | Configuration Manager |
| Optionality/Occurrence: | Optional. Prior to acceptance testing. |
| Templates and Reports: |
|
| Examples: | |
| UML Representation: | Not applicable. |
| More Information: |
| Input to Activities: | Output from Activities: |
Purpose
The purpose of the Configuration Audit Findings is to report on whether:
- the performance of the developed software conforms to its requirements
- the required artifacts are physically present
Brief
Outline
The following topics need to addressed in the Configuration Audit Findings:
Introduction
Date of Audit
The Intent of the Audit
Overall Assessment
Physical Configuration Audit
Baseline Identification
Missing Artifacts
Functional Configuration Audit
Untested Requirements
Failed Requirements
Open Change Requests
Corrective Actions
Action
Actionee
Follow-up Date
Timing
The Configuration Audit Findings are prepared as part of getting a baseline ready for release. It occurs after system testing and prior to final acceptance testing.
Responsibility
The Configuration Manager role is responsible for the integrity of the Configuration Audit Findings, ensuring that the corrective actions raised in these findings are addressed in a timely fashion.
Tailoring
Consider documenting the corrective actions as change requests (see Artifact: Change Request). Document tailoring decisions can be found in the Artifact: Configuration Management Plan.
