Which term best describes the process that maintains a system's configuration across its life cycle and provides technical insight into design decisions?

Which term best describes the process that maintains a system's configuration across its life cycle and provides technical insight into design decisions?

• A. Requirements Management
• B. Change Control
• C. Quality Assurance
• D. Configuration Management

Answer: (D)

Configuration management focuses on identifying, baselining, and controlling the system’s components—hardware, software, and documentation—throughout its life cycle. It maintains versioned baselines, tracks changes, and preserves a complete record of how the system evolves. That history provides technical insight into design decisions because you can see why certain choices were made, how they interrelate, and what impact they had on other components. By ensuring consistency and traceability across development, deployment, and maintenance, configuration management supports reliable progress and informed decision-making. The other terms address different concerns—requirements management deals with what the system should do, change control with approving proposed changes, and quality assurance with ensuring processes and products meet quality standards—whereas configuration management integrates these ideas into maintaining the actual built configuration over time.

Configuration management focuses on identifying, baselining, and controlling the system’s components—hardware, software, and documentation—throughout its life cycle. It maintains versioned baselines, tracks changes, and preserves a complete record of how the system evolves. That history provides technical insight into design decisions because you can see why certain choices were made, how they interrelate, and what impact they had on other components. By ensuring consistency and traceability across development, deployment, and maintenance, configuration management supports reliable progress and informed decision-making. The other terms address different concerns—requirements management deals with what the system should do, change control with approving proposed changes, and quality assurance with ensuring processes and products meet quality standards—whereas configuration management integrates these ideas into maintaining the actual built configuration over time.