Appendix B - Software Configuration Management
How to control baselines, changes, and audits
Learning Objectives
- Identify what to baseline and when
- Use the CCR process to control changes
- Run SCM audits with a concise checklist
Overview
Appendix B defines SCM practices to keep artifacts controlled and traceable. Baselines, CCRs, and audits protect product integrity.
Baselines & Items
| Artifact | Baseline When | Notes |
|---|---|---|
| SRS | After inspection | Changes via CCR |
| SDS + Integration Test Plan | After inspection | Baseline together |
| Code | Per build/release | Tag/label versions |
| Test Plans/Cases | Before execution | Control updates |
Change Control Requests (CCR)
- Include ID, requester, reason, affected items, impact, approvals.
- No baseline change without CCR approval.
- Track status; update baselines and logs after approval.
SCM Audit Checklist
- Are baselines defined and stored with access control?
- Have all changes used CCRs?
- Are backups current?
- Are branches/tags documented?
- Do build/release notes match baselines?