1 / 10

Chapter 9 Software Configuration Management

This chapter explores software configuration management (SCM) and the vital change control processes that ensure software systems can adapt to evolving business and technical requirements. It discusses the various changes that occur throughout a system's life cycle, from user requirements to software models and project plans. The text covers identification tools, version control methods, and auditing practices, emphasizing the change control process steps. This includes recognizing change requests, evaluating them, and ensuring proper documentation and testing for software releases.

mikkel
Download Presentation

Chapter 9 Software Configuration Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chapter 9Software Configuration Management

  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. What Are These Changes? changes in business requirements changes in technical requirements changes in other documents user requirements software models Project Plan data Test code

  4. The Software Configuration programs documents The pieces data

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

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

  7. 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

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

  9. Auditing Change Requests SQA Plan SCIs SCM Audit

  10. Status Accounting Change Reports Change Requests ECOs SCIs Status Accounting Reporting

More Related