The Software Configuration Management (SCM) process defines the need to trace changes, and the ability to verify that the final delivered software has all of the planned enhancements that are supposed to be included in the release.
What are the procedures that must be defined for each software project to ensure that a sound SCM process is implemented? Each correct answer represents a complete solution.
Choose all that apply.
Click on the arrows to vote for the correct answer
A. B. C. D. E. F.ABCD.
The SCM process defines the need to trace changes, and the ability to verify that the final delivered software has all of the planned enhancements that are supposed to be included in the release.
It identifies four procedures that must be defined for each software project to ensure that a sound SCM process is implemented.
They are as follows: 1.Configuration identification: Configuration identification is the process of identifying the attributes that define every aspect of a configuration item.
A configuration item is a product (hardware and/or software) that has an end-user purpose.
These attributes are recorded in configuration documentation and baselined.
2.Configuration change control: Configuration change control is a set of processes and approval stages required to change a configuration item's attributes and to re-baseline them.
3.Configuration status accounting: Configuration status accounting is the ability to record and report on the configuration baselines associated with each configuration item at any moment of time.
4.Configuration audits: Configuration audits are broken into functional and physical configuration audits.
They occur either at delivery or at the moment of effecting the change.
A functional configuration audit ensures that functional and performance attributes of a configuration item are achieved, while a physical configuration audit ensures that a configuration item is installed in accordance with the requirements of its detailed design documentation.
The Software Configuration Management (SCM) process is a critical aspect of the software development lifecycle. It helps ensure that changes made to software are tracked, controlled, and verified to ensure that the final software release meets the intended requirements. To implement a sound SCM process, the following procedures must be defined for each software project:
A. Configuration status accounting: This procedure involves tracking and reporting on the status of all configuration items (CIs) throughout the software development lifecycle. This includes recording the version of each CI, the changes made to it, and the status of each CI (e.g., in development, in testing, released).
B. Configuration change control: This procedure involves managing changes made to the software and ensuring that each change is properly authorized, tested, and documented. Change control ensures that changes are made only after careful consideration of the potential impact and that they do not adversely affect other parts of the software or the overall system.
C. Configuration identification: This procedure involves identifying and naming all CIs in the software system, as well as documenting their relationships and dependencies. This ensures that all CIs are tracked and managed throughout the software development lifecycle and that changes to one CI are not made without considering the impact on other CIs.
D. Configuration audits: This procedure involves reviewing the software system to ensure that it conforms to the planned configuration and that all CIs are properly tracked and managed. Configuration audits may be conducted periodically or at specific points in the software development lifecycle (e.g., before a major release).
E. Configuration implementation: This procedure involves deploying the software system and ensuring that all CIs are properly installed and configured. This may involve creating installation packages, documenting installation procedures, and performing installation and configuration testing.
F. Configuration deployment: This procedure involves releasing the software system to end-users or customers. This may involve creating release notes, providing user documentation, and performing user acceptance testing.
In summary, a sound SCM process requires the implementation of procedures for configuration status accounting, configuration change control, configuration identification, configuration audits, configuration implementation, and configuration deployment.