ppt课件-configurationmanagement-winthrop.pptVIP

Configuration Management Managing Change Points to Ponder Which is more important? stability progress Why is change potentially dangerous? Outline for Today Baselines CM Repository and Config Tools CM Plan Industry Standards Goals of CM Identify Change Control Change Stability vs Progress Ensure Change is Properly Implemented Report Changes to people who Need to Know What Changes? Software Code source code object code Data Documents SRS designs project schedules test plans, test results … Key Concept: Baseline A specification or product that has been formally reviewed and agreed upon, that there-after serves as the basis for further development, and that can be changed only through formal change control procedures. IEEE Std 729 Standard Glossary of Software Engineering Terminology Baseline Use Establishment of a baseline is a milestone. Before that milestone, change can be made informally. Once reviewed and accepted, the product becomes an established baseline. Everyone proceeds using that version, which is located in a central database. Therefore, further change requires formal review, notifications, etc. Baseline - Basic Change Process Change Request is made Request is Approved or Denied Check Out the item(s) Make Changes Testing or Reviews formal review of design changes, regression testing of modules, etc Review the Change Order Notify all Dependencies when baseline change will occur what changes were made to baseline Check In the new baseline Template for Baseline Change Requests Name, Date, yadda yadda Type of change Goal of making the change Priority / Urgency Detailed description of the changes Expected Effects Timetable for making changes, testing, release, Estimated Costs Points to Ponder How do we keep track of all these versions, dependencies among components, approval records, etc. etc. etc., and still assure quality? Use Good CM Tools Have a Sound CM Procedure CM Repository - Common Jargon CM Objects CM probably organized as objec