Software Configuration and Quality Management
What the domain covers
This domain tests configuration management, change control, baselines, audits, and quality management. Expect questions on configuration items, version control, change control boards, status accounting, and the distinction between quality assurance and quality control.
Core rules
- Identify configuration items and place them under version control.
- A baseline is an approved, immutable reference; changes to it follow formal change control.
- A change control board evaluates impact, risk, and cost before approving changes.
- Configuration status accounting records what is in each baseline and what changed.
- Quality assurance focuses on process conformance; quality control focuses on inspecting products and test results.
Worked example
An emergency production fix is needed. The team edits code directly on the production server. This violates configuration management. Correct approach: create a branch from the current baseline, implement and review the fix, run regression tests, obtain expedited change approval, build from version-controlled sources, deploy the build, and record the new baseline. Reasoning: emergency speed changes approval timing, not traceability or repeatability.
Traps
- Treating version control as complete configuration management.
- Confusing quality assurance with testing.
- Changing a baseline without approval or records.
- Omitting configuration audits before release.
Exam focus
Trace a change from request through impact analysis, approval, build, test, and baseline update.