Configuration Auditing
- Configuration Auditing
- the configuration management
task of auditing a
baseline
As illustrated in the preceding figure, Configuration Auditing is part of the following inheritance hierarchy:
- Type: Abstract
- Superclass: Configuration Management Task
- Subclasses:
The typical responsibilities of Configuration Auditing are to:
- Verify if the baseline is correctly identified and
properly versioned.
- Verify if the baseline is complete in that it contains
the proper versions of the proper configuration items.
Configuration auditing typically can begin when the
following preconditions hold:
- The
configuration management team is staffed.
- The configuration management members are adequately
trained in configuration auditing.
- A baseline's developers declare that it is ready for
delivery to the customer organization.
Configuration auditing is typically complete when the
following postconditions hold:
- All baselines have been delivered.
- The endeavor has ended.
Configuration auditing typically involves the following
teams performing the following steps in an iterative,
incremental, and parallel manner:
- The
project
team notify the
configuration management (CM) team that a specific version
of a baseline is ready for delivery.
- The CM team determines the correct versions of the
correct configuration items that make up the baseline.
- The CM team audits the baseline.
- The CM team documents the results of the audit in the
configuration audit report.
Configuration auditing typically can be performed using the
following techniques:
Configuration auditing typically results in the production
of the following work products:
