Software Configuration Management
- Foundations of SCM
- Definition of configuration management
- SCM in CMMI, ISO, IEEE, and other standards
- How different software development paradigms impact SCM planning and practice
- Relationship of SCM to other project disciplines
- Using SCM to maintain product integrity and quality
- SCM planning
- Principles of Software Configuration Identification
- CMMI guidelines for the identification function
- Which work products to manage, and level of management
- COTS, licenses, royalties, and data rights
- Key role of requirements management in SCM
- Project manager’s role and responsibilities
- Baselines
- Principles of Configuration and Change Management
- CMMI guidelines for software change control/management
- How change management relates to configuration identification
- Versions, revisions, variants, and branches
- How to control baselines
- How to integrate subcontractors and vendors
- Establishing a change control authority
- Controlling changes to interfaces
- Principles of Configuration Status Accounting (CSA)
- CMMI guidelines for software CSA
- Using software CSA in baseline management
- Handling releases
- Relationship with subcontractor or vendor CSA
- Creating release notes and version description documents
- Principles of Configuration Audits
- CMMI guidelines for configuration audits
- Methodologies and techniques
- Differences between functional and physical configuration audit
- Reporting results to stakeholders
- Scheduled and unscheduled reviews and audits
- Auditing subcontractors and vendors
- Managing deviations and waivers
- Creating SCM work products
- Course Summary
- Lessons learned
- Where to go from here
