Identified for Configuration Management
The term configuration item (CI) refers to the fundamental structural unit of a configuration management system. Examples of CIs include individual requirements documents software models and plans. The configuration-management system oversees the life of the CIs through a combination of processes and tools by implementing and enabling the fundamental elements of identification change management status accounting and audits. This system aims to avoid the introduction of errors related to lack of testing as well as incompatibilities with other CIs.
Configuration Management Activities :
1. Configuration Item Identification :
In this phase, the item will be identified for making changes. Example: Requirement document design document source code etc
2. Change Control :
Controlling the release and changes of the product throw out the software life cycle here CCB team will approve or disapprove changes prioritize the changes and schedule the changes for the next releases.
3. Status Accounting :
Recording and reporting status of configuration items will be done in this phase. configuration status report will be created.
4. Status Audit :
In this phase, checking is done that is all the changes are implemented properly or not. The goal of configuration management is achieved or not.
There are two types of Status Audit :
● Functional Audit: It will check the proposed changes are implemented in software properly.
● Physical Audit: This will check software and documentation are internally consistent.
A configuration item is an entity designated for configuration management which may consist of multiple related wor products that form a baseline. This logical grouping provides ease of identification and controlled access. The selection of wor products for configuration management should be based on criteria established during planning.
CI types are:
● Hardware
● Software
● CommunicationsNetwors
● location
● documentation
● people (Staff and Contractors)
Configuration Management Activities :
1. Configuration Item Identification :
In this phase, the item will be identified for making changes. Example: Requirement document design document source code etc
2. Change Control :
Controlling the release and changes of the product throw out the software life cycle here CCB team will approve or disapprove changes prioritize the changes and schedule the changes for the next releases.
3. Status Accounting :
Recording and reporting status of configuration items will be done in this phase. configuration status report will be created.
4. Status Audit :
In this phase, checking is done that is all the changes are implemented properly or not. The goal of configuration management is achieved or not.
There are two types of Status Audit :
● Functional Audit: It will check the proposed changes are implemented in software properly.
● Physical Audit: This will check software and documentation are internally consistent.
A configuration item is an entity designated for configuration management which may consist of multiple related wor products that form a baseline. This logical grouping provides ease of identification and controlled access. The selection of wor products for configuration management should be based on criteria established during planning.
CI types are:
● Hardware
● Software
● CommunicationsNetwors
● location
● documentation
● people (Staff and Contractors)
Comments
Post a Comment