Version Control and Change Control
- Moreover, Version control combines procedures and tools to manage different versions of configuration objects that are created during the software process.
- A version control system implements or directly integrated with four major capabilities:
- A project database (repository) that stores all relevant configuration objects.
- Moreover, A version management capability that stores all versions of a configuration object.
- A make facility that enables you to collect all relevant configuration objects and construct a specific version of the software.
- Also, In addition, version control and change control systems often implement an issues tracking capability that enables the team to record and track the status of all outstanding issues associated with each configuration object.
- A number of version control systems establish a change set—a collection of all changes (to some baseline configuration) that are required to create a specific version of the software.
- Moreover, A change-set “captures all changes to all files in the configuration along with the reason for changes. And details of who made the changes and when.”
- A number of named changesets can identify for an application or system.
- Moreover, This enables you to construct a version of the software by specifying the changesets (by name) that must apply to the baseline configuration.
- To accomplish this, a system modeling approach applied. The system model contains:
- A template that includes a component hierarchy. And a “build order” for the components that describes how the system must construct.
- Construction rules.
- Verification rules.
- The primary difference in approaches the sophistication of the attributes that used to construct specific versions and variants of a system and the mechanics of the process for construction.
- For a large software project, uncontrolled change rapidly leads to chaos.
- In such projects, change control combines human procedures and automated tools to provide a mechanism for the control of change.
- Also, A change request submitted and evaluated to assess technical merit, potential side effects. The overall impact on other configuration objects and system functions, and the projected cost of the change.
- The results of the evaluation presented as a change report, which used by a change control authority
- (CCA)—a person or group that makes a final decision on the status and priority of the change.
- Moreover, An engineering change order (ECO) generated for each approved change.
- Similarly, The ECO describes the change to make, the constraints that must respect, and the criteria for review and audit.