Paul Naybour
List and Describe 5
elements that would be performed as part of an effective configuration
management process ?
- Planning
- Identification
- Control
- Status Accounting
- Audit
The planning stage involves
defining the process for configuration management (Identification, Control, Status
Accounting, audit), which roles will be responsible and accountable for each
process (e.g. configuration librarian, Configuration Item Control, Project
office), which tools will be employed e.g. version control software for a new software
development, and the mechanism by which the process will be audited and by who.
defining the process for configuration management (Identification, Control, Status
Accounting, audit), which roles will be responsible and accountable for each
process (e.g. configuration librarian, Configuration Item Control, Project
office), which tools will be employed e.g. version control software for a new software
development, and the mechanism by which the process will be audited and by who.
The identification element
consists of uniquely recording each of the products and sub products which will
be produced as part of the project (usually through developing a product breakdown
structure) and recording them within the configuration library with a unique
entry, description and version number. This is not only for the physical
products but also the products that help define them such as the product
description, blueprints.
consists of uniquely recording each of the products and sub products which will
be produced as part of the project (usually through developing a product breakdown
structure) and recording them within the configuration library with a unique
entry, description and version number. This is not only for the physical
products but also the products that help define them such as the product
description, blueprints.
The control element is performed
by the configuration item controller. It has strong links with the change
control process in the once a change is approved the products are checked out
of the configuration library, the changes developed, tested and signed off by
the user before they are checked back in and recorded as a new version. This
ensures items can be consistently and reliably released to a live environment
improving reducing the chances of negative impact on BAU.
by the configuration item controller. It has strong links with the change
control process in the once a change is approved the products are checked out
of the configuration library, the changes developed, tested and signed off by
the user before they are checked back in and recorded as a new version. This
ensures items can be consistently and reliably released to a live environment
improving reducing the chances of negative impact on BAU.
Status Accounting describes the
current position of a product and includes the version number, current status
(whether check out) or not, who has checked out the product and the history of
any changes that have been made to product by who and when. Status Accounting is the responsibility of the
configuration item controller. Through status accounting we can ensure which
products and which versions have been tested signed off and implemented
together.
current position of a product and includes the version number, current status
(whether check out) or not, who has checked out the product and the history of
any changes that have been made to product by who and when. Status Accounting is the responsibility of the
configuration item controller. Through status accounting we can ensure which
products and which versions have been tested signed off and implemented
together.
Audit ensures that all of the
products within the configuration management system match their real world
equivalents. The project usually checks itself and spot checks are performed
within our organisation by the project office. However external verification is
also performed via audit who are external to the project. Audit will also check
that the process for configuration management is being followed which is part
of the PMP. This provides assurance and confidence to the sponsor.
products within the configuration management system match their real world
equivalents. The project usually checks itself and spot checks are performed
within our organisation by the project office. However external verification is
also performed via audit who are external to the project. Audit will also check
that the process for configuration management is being followed which is part
of the PMP. This provides assurance and confidence to the sponsor.