software configuration management n art of coordinating sw development to minimize confusion n...
Post on 19-Jan-2016
215 Views
Preview:
TRANSCRIPT
Software Configuration Management
Art of coordinating SW development to minimize confusion
Software quality assurance (umbrella) activity
Set of tracking and control activities beginning to end
Why Software Configuration Mgmt?
Change increases confusion
CM necessary when a software system has
Many developers Many versions
CM aims to control the costs and effort involved in making changes to a system
Software Configuration Mgmt Activities
Identifying change
Controlling change
Ensuring change is properly implemented
Reporting changes to interested others
Identifying Changes: Origin of changes
New business or market conditions New customer needs Reorganization or business growth/downsizing Budgetary or scheduling constraints Most changes are justified
Identifying Changes
SW Configuration Items (SCIs) are identified Document, suite of test cases, program
component, software tools Identify relationships among SCIs (part-of,
interrelated, dependencies)
Configuration Items
Repository Content
Baselines
Concept that helps us control change without seriously impeding justifiable change
Before baseline: changes made quickly and informally
Once baseline established: changes can be made, but a formal procedure must be applied to evaluate and verify each change
Baselined SCIs
Controlling Changes
Version control manage many existing versions of SCIs Use evolution graph or object pool
representation
Change Control Process
Distribute the new version
Controlling Changes
before and after release Authority (access control and synchronization
control) Change requests submitted and evaluated Change report (results of evaluation) Change order (for approved change) Check out SCI, make change, apply SQA activities Check in SCI to database and version control
mechanisms Before baseline, informal change control Once baseline est. project level change control After release, formal change control
Ensure change properly implemented
aka Configuration auditing• Formal technical reviews• Software configuration audit
– Change made? Additional modifications?– Formal technical review conducted?– Software process followed/standards
applied?– Change “highlighted” in SCI? change
date/author noted?– SCM procedures followed?– Related SCIs updated?
Reporting Changes
What happened? Who did it? When? What else will be affected?
Keep management and practitioners appraised of important changes.
top related