 |
 |
 |
SOFTWARE CONFIGURATION MANAGEMENT
Configuration Management (CM) is a key component of the infrastructure for any software development organization. The ability to maintain control over the change made to all project artifacts it is to implement change to both the application and its supporting artifacts in a controlled manner.
Most organizations understand the importance of managing source code and the chnges made to it, but all project artifacts need to be managed; from requirements and models, to test cases and test data. For example, if a requirement is changed or added during the project after the requirements have been base lined, the tests designed and build to validate the requirement must also updated. The appropriate version of the tests must be executed for the updated code, or incorrect results will be obtained.
For large projects, the Configuration Manager is often full time member of the project team. This person provides and supports the overall CM infrastructure and environment for the project team. Smaller efforts might not be able to support a full time Configuration Manager, and might share a resource with other projects the role to someone on the project team in addition to their other responsibilities.
The CM function ensures that the CM environment facilities product baseline, review, change, and defect tracking. Responsibilities also include witting the CM plan and reporting change request based progress statistics. The CM function supports product development activates so that developer and integrator ha appropriate workspace to build and test their work, and that all artifacts are available as required.
The list below illustrte the types of the project artifacts that must be managed and controlled in the CM environment:
·Source Code
·Requirements
·Analysis models
·Design Models
·Test Cases and procedures
·Automated Test Scripts
·User documentation, including manuals and online Help
·Hardware and Software configuration settings
·Other artifacts as needed
Configuration Management (CM) is a key component of the infrastructure for any software development organization. The ability to maintain control over the change made to all project artifacts it is to implement change to both the application and its supporting artifacts in a controlled manner.
Most organizations understand the importance of managing source code and the chnges made to it, but all project artifacts need to be managed; from requirements and models, to test cases and test data. For example, if a requirement is changed or added during the project after the requirements have been base lined, the tests designed and build to validate the requirement must also updated. The appropriate version of the tests must be executed for the updated code, or incorrect results will be obtained.
For large projects, the Configuration Manager is often full time member of the project team. This person provides and supports the overall CM infrastructure and environment for the project team. Smaller efforts might not be able to support a full time Configuration Manager, and might share a resource with other projects the role to someone on the project team in addition to their other responsibilities.
The CM function ensures that the CM environment facilities product baseline, review, change, and defect tracking. Responsibilities also include witting the CM plan and reporting change request based progress statistics. The CM function supports product development activates so that developer and integrator ha appropriate workspace to build and test their work, and that all artifacts are available as required.
The list below illustrte the types of the project artifacts that must be managed and controlled in the CM environment:
·Source Code
·Requirements
·Analysis models
·Design Models
·Test Cases and procedures
·Automated Test Scripts
·User documentation, including manuals and online Help
·Hardware and Software configuration settings
·Other artifacts as needed
Configuration Management