More Related Content
Similar to Software Configuration Management
Software Configuration Management
- 1. Software configuration Management Plan
- 2. Plan • First stepin SCM system • Includes – Objectives – Responsibilities – Approaches – Methods to be used • Contents & checklist
- 3. SCMP contents 1. Overview – SCM objective – System overview 2. SCM organization – SCM responsibilities – Configuration Control Board members – Configuration Control Board charter – Product Assurance relationship 3. SCM methods – Baselines & contents – Identification system – Control system – Auditing – Status accounting – CM support tools
- 4. Cont.. 4. SCM procedures – Procedures manual – Forms & records 5. SCM implementation – Personal plan – System support plan – Budget – Key implementation checkpoints
- 5. SCM Questions • Requirementsphase – Where s the official reqmts stmt? – What changes have been made? – What s the impact of changes in design? • Design phase – Where is the reqmt covered by design? – What is the particular requirement that this design element satisfies? – What is the current approved specification for this interface? – What is the design impact of this reqmts change? • Implementation – How has the particular function been allocated to various implementation areas? – What is the design logic? – What compiler version was used to produce this code? • Testing – Where are the tests that verify this functional requirement? – Where is the test data for use with these tests?
- 6. Requirements phase • Requirementschanges • Requirements baseline & change control • External specifications
- 7. Design control • Changecontrol board • Software configuration identification – Design – creative process – Design – template – Permanent design – later repair / enhancement – Permanent record for design changes – To maintain control the design is subdivided into modules
- 8. Implementation phase • Functions – Source code charge out & charge-in facilities – Read-only access to specifications & object code – Ability to compile modules – Procedure for making approved changes – Any new source code is consistent with module specifications
- 9. Test phase • SCMshould have the following capabilities – Means for creating new bug reports – Means for closing bug reports – Periodic reporting of bug status
- 10. Implementation change controlprocedure change request Change approved? yes No Design Get change approval / needed? stop work No yes Specification Fix change implement needed? yes ation No Adjust Fix design specification To SCM
- 11. Configuration auditing • Tomaintain a continuous record of the state of all baselined items • The information required includes – Time at baseline established – When each configuration item(CI) & change included in baseline – Description of CI – Description of s/w change – Status of s/w change – Documentation status for each baseline
- 12. Items needed forconfiguration accounting • CI index – Creation date – Current released version – Version of its component items • Change logs – History of changes – Release histories • All Discrepancy requests • All Change requests
- 13. S/W configuration audit •Rules – Periodically needed to ensure integrity – To perform before major baseline change – Audit team – qualified technical people – To verify that changes to baseline are implemented as intended – Integral part of SCM system – Continuous with increased frequency and depth – Documented project plan is used as basis
- 14. SCM audit • Checksfor – Requirements – Functional – High-level design – Design – Product – Operational