A process which defines a series of tasks that have the following four primary…
2013
A process which defines a series of tasks that have the following four primary objectives is known as
1. to identify all items that collectively define the software configuration.
2. to manage changes to one or more of these items.
3. to facilitate the construction of different versions of an application.
4. to ensure that software quality is maintained as the configuration evolves over time.
- A.
Software Quality Management Process
- B.
Software Configuration Management Process
- C.
Software Version Management Process
- D.
Software Change Management Process
Attempted by 206 students.
Show answer & explanation
Correct answer: B
Answer: Software Configuration Management Process
Explanation: The four primary objectives listed correspond to the scope of Software Configuration Management. This process ensures that all items that make up a software product are identified and controlled, that changes are managed, that different versions can be constructed, and that quality is preserved as the configuration changes.
Identify configuration items: define and record the components (source code, documentation, libraries, build scripts, etc.) that collectively form the software configuration.
Manage changes: control and track changes to configuration items through change control and approval processes.
Facilitate construction of different versions: use version control, branching, and build management to create and reproduce specific releases or variants.
Maintain quality over evolution: ensure integrity, traceability, and consistent builds so that quality is preserved as the configuration changes.
Why the other processes are not the best match:
Software Quality Management focuses on planning, assurance and control activities (testing, audits, metrics) to achieve product quality, rather than the identification and versioning of configuration items.
Software Version Management (version control) is one key part of configuration management but is narrower in scope; it does not by itself cover configuration identification, change control, build/release management and quality preservation.
Software Change Management handles change requests and approvals and overlaps with configuration management, but configuration management additionally includes item identification, version/build management and ensuring configuration integrity over time.