Configuration Management (managing change)

Slides:



Advertisements
Similar presentations
Configuration Management
Advertisements

Software Quality Assurance Plan
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?
CSC 395 – Software Engineering Lecture 25: SCM –or– Expecting Change From Everything But Vending Machines.
Software Configuration Management (SCM)
Configuration Management
Software Configuration Management
Chapter 27 Change Management
Software Configuration Management
Software Configuration Management (SCM)
CSSE 375 Software Construction and Evolution: Configuration Management
Configuration Management Avoiding Costly Confusion mostly stolen from Chapter 27 of Pressman.
SE-02 CONFIGURATION MANAGEMENT Today we talk about Software Configuration Management (SCM for short): - What? - Why? - How?
Software Configuration Management (SCM)
Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?
Component-level testing – Equivalence partitioning, boundary value analysis, path testing Navigation testing – Testing navigation syntax and semantics.
Software Configuration Management
Software Configuration Management (SCM)
Configuration Management (managing change). Starter Questions... Which is more important?  stability  progress Why is change potentially dangerous?
Software Quality Assurance
© Mahindra Satyam 2009 Configuration Management QMS Training.
Software Engineering 2003 Jyrki Nummenmaa 1 CONFIGURATION MANAGEMENT Today we talk about Software Configuration Management (SCM for short): -
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
SOFTWARE CONFIGURATION MANAGEMENT. Change is inevitable when computer software is built. And change increases the level of confusion among software engineers.
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 29 Slide 1 Configuration management.
Management of Software Project CSM Software Configuration Management (SCM)
Software Configuration Management (SCM) Source: Pressman, R., Software Engineering: A Practitioner ’ s Approach. Boston: McGraw Hill, Inc., 2005; Ghezzi,
Software Configuration Management n Art of coordinating SW development to minimize confusion n Software quality assurance (umbrella) activity n Set of.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Configuration Management
Software Configuration Management SEII-Lecture 21
Software Engineering Lecture 9: Configuration Management.
Configuration Control (Aliases: change control, change management )
Configuration & Build Management. Why Software Configuration Management ? The problem: Multiple people have to work on software that is changing More.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 27 Change Management Software Engineering: A Practitioner’s Approach, 6/e Chapter 27 Change.
Software Configuration Management (SCM)
Software Configuration Management -Subversion- RTLAB YuJin Park.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Software Configuration Management (SCM)
Configuration Management
Software Configuration Management
Configuration Management
Software Configuration Management CSC-532
Software Configuration Management
Software Project Configuration Management
Chapter 10, Software Configuration Management
Software Configuration Management (SCM)
Chapter 11: Software Configuration Management
Software Configuration Management
Software Engineering (CSI 321)
Configuration Management
Software Configuration Management
Chapter 27 Change Management
Chapter 29 Software Configuration Management
Lecture 3 Change Management
Chapter 29 Software Configuration Management
Software Configuration Management
Chapter 27 Change Management
Chapter 27 Change Management
Baseline – IEEE definition
Chapter 11: Software Configuration Management
Chapter 27 Change Management
Chapter # 6 Software Configuration Management
Chapter 27 Change Management
Coupling Interaction: It occurs due to methods of a class invoking methods of other classes. Component Coupling: refers to interaction between two classes.
I&C requirements and configuration management
Software Engineering: A Practitioner’s Approach, 6/e Chapter 27 Change Management copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Software Configuration Management
Presentation transcript:

Configuration Management (managing change)

Starter Questions... Which is more important? stability progress Why is change potentially dangerous? What causes configuration problems? multiple developers multiple releases components used in multiple products changing requirements etc...

Confusion is NOT inevitable. Change is inevitable. AND Change creates confusion. BUT, Confusion is NOT inevitable.

Outline for Tonight "Baselines" CM Repository and Config Tools CM Plan Much of this Software Configuration Management presentation is based on Chapter 27 of Pressman's Software Engineering: A Practitioners Approach 6th Edition

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 Data Documents source code object code 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 repository. Therefore, further change requires formal review, notifications, etc.

Baseline - Standard Change Process 9 of 22 Baseline - Standard Change Process Change Request is made (see next slide) 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 10 of 22 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

http://satc.gsfc.nasa.gov/GuideBooks/Image4.jpg

12 of 22 Version Numbering Item After Modify Build 1 Build 2 Release 1… Test Plan 0.0.0 (original version) 0.0.1 --> 0.1.0 0.1.1 --> 0.2.0 --> 1.0.0 Module 1 0.0.0 --> 0.1.0 --> 0.2.0 --> 1.0.0 Module 2 0.0.0 ... 0.0.8 --> 0.1.0 0.1.1 --> 0.2.0 0.2.1 0.2.2 --> 1.0.0

Question... Use Good CM Tools Have a Sound CM Procedure How do we keep track of all these versions, dependencies among components, approval records, etc. etc. etc.? Use Good CM Tools Have a Sound CM Procedure

CM Repository - Common Jargon 14 of 22 CM Repository - Common Jargon CM Objects CM probably organized as object-oriented database Basic Objects Aggregate Objects Configuration Item standard term for entities in the CMR

CM Tools - Necessary Features 15 of 22 CM Tools - Necessary Features Versioning Dependency Tracking!!! Audit Trails!!! Reporting of Changes Supports the Change Rules Requirements Tracing Repository arranged as "basic objects" and "aggregate objects" Supports both Linear evolution and Trees

16 of 22 Get a copy of the module tc: $ cvs checkout tc Get a copy of the module tc as it looked one day ago: $ cvs checkout -D yesterday tc If you had to create a patch to the 1.2 version of the product, even though the 2.0 version is already under development, you might do: $ cvs rtag -b -r FCS1_2 FCS1_2_Patch product_module $ cvs checkout -r FCS1_2_Patch product_module $ cd product_module [[ hack away ]] $ cvs commit Other very handy commands annotate - for each line, print the version that created it diff - differences in versions, LOTS of options history - version dates, etc. log - who last edited each line release - stop editing, but don't save changes update - reconcile your copy with recent changes made by other developers

Parts of a CM Plan Process Elements Component Elements collection of procedures that define approach to change management Component Elements set of tools and file management system that enable access to and management of items Construction Elements tools that automate the construction of software, test suites, etc. Human Elements

Standard for Software Configuration Management Plans IEEE / ANSI 828 18 of 22 Standard for Software Configuration Management Plans 1. Introduction a) purpose b) scope c) definitions and acronyms d) references 2. Management a) organization b) SCM responsibilities c) interface control d) SCMP implementation e) policies, directives, procedures (naming conventions, version designations, problem report process) 3. SCM Activities a) configuration identification b) configuration control (change history, review authority, read/write control, member identification) c) configuration status accounting (status of change requests, status of approved changes, …) d) audits and reviews 4. Tools, Techniques, and Methodologies 5. Supplier Control 6. Records Collection and Retention

Guide to Software Configuration Management IEEE 1042 Guide to Software Configuration Management Defines terms such as baseline and version Discusses configuration management as a management discipline and its role in the engineering process Includes checklists of issues for sections of the SCMP (IEEE Std 828) Includes four complete examples of SCMPs

CM Audits % of unapproved changes % of Change Orders completed on schedule % of affected Configuration Items that were not checked % of properly documented Configuration Items number of CM Process Failures

Summary Change is inevitable. Baselines are milestones of a configuration item. Use a tool or set of tools to control change access control version tracking etc Adopt a Change Management Plan

Next Class Exam Two