A.5 Configuration item record
To provide a record of such information as the history, status, version and variant of each configuration item, and any details of important relationships between them.
The set of configuration item records for a project is often referred to as a configuration library.
The composition of a configuration item record will be defined in the project’s configuration management strategy.
There follows a suggested list of components for each configuration item record (note that the first three uniquely identify the configuration item):
- Project identifier A unique reference. It will typically be a numeric or alpha-numeric value
- Item identifier A unique reference. It will typically be a numeric or alpha-numeric value
- Current version Typically an alpha-numeric value
- Item title The description of the item (for a product this should be as it appears in the product breakdown structure)
- Date of last status change
- Owner The person or group who will take ownership of the product when it is handed over
- Location Where the item is stored
- Copy-holders (if relevant) Who currently has the product?
- Item type Component, product, release
- Item attributes As defined by the configuration management strategy. These are used to specify a subset of products when producing a product status account, such as the management stage in which the product is created, the type of product (e.g. hardware/software), product destination etc.
- Stage When the product will be developed
- Users The person or group who will use the item
- Status As defined by the configuration management strategy, e.g. pending development, in development, in review, approved or handed over
- Product state (if used) As defined by the product description, e.g. dismantled machinery, moved machinery, reassembled machinery
- Variant (if used) For example, language variants
- Producer The person or team responsible for creating or obtaining the item
- Date allocated To the producer
- Source For example, in house, or purchased from a third-party company
- Relationship with other items Those items that:
- Would be affected if this item changed
- If changed, would affect this item
- Issues and risks
- Documentation that defines requirements, design, build, production and verification for the item (specifically this will include the product description).