1 / 12

Change Control Process—I

Change Control Process—I. need for change is recognized. change request from user. developer evaluates. change report is generated. change control authority (CCA) decides. request is queued for action – Engineering change order (ECO) generated. change request is denied.

grimesj
Download Presentation

Change Control Process—I

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. Change Control Process—I need for change is recognized change request from user developer evaluates change report is generated change control authority (CCA) decides request is queued for action – Engineering change order (ECO) generated change request is denied change control process—II user is informed

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

  3. Check-in and check-out • Access and synchronization control • Access control – • who has the authority to check-out the object • Synchronization control – • ensures that parallel changes by two different people do not overwrite one another. • Control on updates • Other copies can be checked out for use • Single writer, multiple readers

  4. lock Request for Configuration object Check- in Check- in Configuration object (modified version) Configuration object (modified version) Configuration object (baseline version) Configuration object (baseline version) Audit info unlock unlock Access control Access control Software engineer Software engineer Project DB Project DB Ownership info Ownership info Configuration object (extracted version) Configuration object (extracted version) lock Check- out Check- out Request for Configuration object Configuration object (baseline version) Configuration object (baseline version)

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

  6. Configuration Audit • Ensuring that a change has been properly implemented • Formal technical reviews • Software Configuration audit • Configuration audit assess a configuration object for characteristics that are generally not considered during audit • Conducted by the SQA group

  7. Configuration audit • Has the change specified in the ECO been made? Have any additional modifications been incorporated?

  8. Configuration audit • Has a FTR been conducted to assess technical correctness? • Has the software process been followed? • Have the SE standards been properly applied?

  9. Configuration audit • Has the change been highlighted in the SCI? • Change date and author • Have the attributes of the configuration object been updated? • Have the SCM procedures for noting the change, recording it, and reporting it been followed? • Have all related SCI’s been properly updated?

  10. Configuration Status reporting (CSR) • Aka status accounting • What happened? • Who did it? • When did it happen? • What else will be affected?

  11. Software Engineering II Lecture 35 Fakhar Lodhi

  12. Recap

More Related