Software Configuration Management

Sponsored Links:

Configuration Management (CM) is a key part of the infrastructure of a application development organization. The ability to maintain control over the amendment all the artifacts of the project is to implement changes to both the application and its supporting devices in a controlled manner.

Most organizations understand the importance of managing the source code and changes made to it, but all project artifacts ought to be managed, the requirements and models to test cases and test information. For example, if a requirement is changed or added in the project after the requirements are common, facts of design and construction to validate the requirement must even be updated. The appropriate version of the test must be executed by the update code, or incorrect results will be obtained.
For large projects, the Configuration Manager is often full-time members of the project team. This person provides and supports the general infrastructure of CM and the environment for the project team. Small efforts may not be able to support a full-time Configuration Manager, and may share a resource with other projects from paper to somebody from the project team, in addition to their other duties.
The function ensures that the environment CM reference installations of products, review, change and defect tracking. Duties also include Witting CM plan and reporting statistics change request based on the progress. CM The role supports the development of the product is so active workspace and appropriate integrator developers to build and test your work, and that all devices are available when needed.
The following types of project artifacts to be managed and controlled in the environment CM:
• Source Code
• Requirements
• Analysis Model
• Design Models
• Test cases and procedures
• Automated test scripts
• Documentation of user manuals and online help
• Hardware and application configuration settings
• Other devices as needed

No comments: