1. 1 Chapter 9 Software Configuration Management

2. 2 The “First Law” No matter where you are in the system life cycle, the system will change, and the desire to change it will persist throughout the life cycle. Bersoff, et al, 1980

3. 3 What Are These Changes? data otherdocuments code Test Project Plan changes in technical requirements changes in business requirements changes in user requirements software models

4. 4 Software Configuration Items (SCIs) programs documents data The pieces

5. 5 Baseline

6. 6 Software Configuration Items (SCIs)

7. 7 SCM Tasks Software Engineering a foundation procedures methods tools SCM identification identification version control version control change control change control auditing auditing reporting reporting

8. 8Identification  Object-oriented approach  Types basic objectbasic object aggregate objectaggregate object FeaturesFeatures name name description description set of resources set of resources realization realization RelationshipRelationship Data model design specification Data model design specification Data model data flow model Data model data flow model EvolutionEvolution Evolution graph Evolution graph

9. 9

10. 10 Change & SCM Software Engineering a TQM foundation procedures methods tools SCM identification identification version control version control change control change control auditing auditing reporting reporting

11. 11 Version Control  Techniques Evolution GraphEvolution Graph Attribute TupleAttribute Tuple Object PoolObject Pool

12. 12 Evolution Graph

13. 13 Attribute Tuple  Attributes customercustomer development languagedevelopment language development statusdevelopment status hardware platformhardware platform creation datecreation date

14. 14 Object Pool

15. 15 Change & SCM Software Engineering a TQM foundation procedures methods tools SCM identification identification version control version control change control change control auditing auditing reporting reporting

16. 16 Change Control Process—I change request from user developer evaluates change report is generated change control authority decides request is queued for action ECO generated ECO generated change request is denied user is informed need for change is recognized change control process—II

17. 17 Change Control Process-II assign people to SCIs check-out SCIs make the change review/audit the change establish a “baseline” for testing change control process—III “Check in” the SCIs that have been changed

18. 18 Change Control Process-III perform SQA and testing activities promote SCI for inclusion in next release rebuild appropriate version review/audit the change include all changes in release distribute the new version

19. 19

20. 20 Change & SCM Software Engineering a TQM foundation procedures methods tools SCM identification identification version control version control change control change control auditing auditing reporting reporting

21. 21 Configuration Audit  Has the change specified in the ECO been made? Have any additional modifications been incorporated?  Has a formal technical review been conducted to assess technical correctness?  Has the software process been followed and have software engineering standards been properly applied?

22. 22  Has the change been “highlighted” in the SCI? Have the change date and change author been specified? Do the attributes of the configuration object reflect the change?  Have SCM procedures for noting the change, recording it, and reporting it been followed?  Have all related SCIs been properly updated?

23. 23 Configuration Status Reporting (CSR) SCIs ChangeRequests ChangeReports ECOs Status Accounting Reporting

24. 24 Software Project Plan