1 / 5

Chapter 27 Change Management

Chapter 27 Change Management. 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. The “ First Law ”. 1/4. Software Configuration Items (SCI). programs. documents. data.

dalit
Download Presentation

Chapter 27 Change 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 27 Change Management

  2. 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 The “First Law” 1/4

  3. Software Configuration Items (SCI) programs documents data 27.1 Software Configuration Management • Software Configuration: The items that comprise all information produced as part of the software process (programs, data, documents, and more …) are collectively called a software configuration. • Baselines (IEEE Std. No.610.12-1990): A specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development, and that can be changed only through formal change control procedures. 2/4

  4. modified Project database SCI approved baselined SCM controls reviews SCI SCI SCI need change 27.1 Software Configuration Management SCI Baselines: System Specification Software Requirements Design Specification Source Code Test Plans / Procedures / Data Operational System 3/4

  5. 27.3 The SCM Process • Identification: How does an organization identify and manage the many existing versions of a program (and its documentation) in a manner that will enable change to be accommodated efficiently? • Version Control: How does an organization control changes before and after software is released to a customer? • Change Control: Who has responsibility for approving and ranking changes? • Configuration Auditing: How can we ensure that changes have been made properly? • Reporting: What mechanism is used to appraise others of changes that are made? 4/4

More Related