Poll Results
No votes. Be the first one to vote.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Configuration management is typically divided into two key subsystems: Configuration Identification and Configuration Control.
1. Configuration Identification involves identifying the attributes that define every aspect of a configuration item. A configuration item can be a product, system, software, or a distinct part of these (or a combination thereof). This subsystem includes the selection of configuration items to be controlled, and the documentation of their physical attributes and functional capabilities. It encompasses version control and baselining processes, ensuring that everyone involved has a clear understanding of the system’s current state and its history.
2. Configuration Control revolves around the evaluation, coordination, approval or disapproval, and implementation of changes to configuration items after formal establishment of their configuration identification. It ensures that all proposed changes and design modifications are systematically reviewed, evaluated for their impact on the overall system, and approved before implementation to prevent unauthorized changes from occurring. It also involves the management of change requests and maintaining the integrity and traceability of changes throughout the lifecycle.
These two subsystems work together to ensure that a system’s performance, functional and physical attributes are accurately documented and maintained, and that any changes to the system are controlled and accounted for, improving reliability and quality.