Software configuration management
Download as PPTX, PDF4 likes5,888 views
The document discusses software configuration management (SCM) which controls the evolution of complex software systems. SCM provides capabilities like identification, control, status tracking, auditing and reviewing of software work products. The goals of SCM include planning activities, identifying and controlling selected work products, managing changes, and informing groups of status. Objectives include remote administration, reliability, setup ease and more. The document also discusses configuration management processes, baselines, change management processes and tools, and version control.
Software configuration management
- 1. SOFTWARE CONFIGURATION MANAGEMENT
- 2. What is configuration management? • “SCM is the control of the evolution of complex systems,…, for the purpose to contribute to satisfying quality and delay constraints.” – Jacky Estublier • “SCM provides the capabilities of identification, control, status accounting, audit and review, manufacture, process management, and teamwork.” – Susan Dart
- 3. Goals of CM • SPM activities are planned. • Selected s/w work products are identified,controled and available.. • Change to identified s/w work products are controlled. • Affected groups and individuals are informed of the status and contents s/w baseline.
- 4. Objectives of CM • Remote system administration. • Reduced user down-time. • Reliable data backup. • Easy worstation set up. • Multi user support. • Remote s/w installation.
- 5. Configuration Management process Configuration Planning Data Project Management Processes Management CM Plan Project Formulation Project Planning Process Status reports; audit results Project Monitoring & Control Project Startup Controlled work Work products; products; approved Project Closeout change requests change requests Product Development Processes Systems Requirements Design Engineering Engineering Implementation Sustaining Engineering & Product Release Testing Maintenance
- 6. CM Benefits • Improves – Product protection – Product visibility – Product control – Team communication – Customer Confidence • Decreases – Rework – Confusion – Project Risk
- 7. BASELINE • “A specification or product that has been formally reviewed and agreed to by responsible management, that thereafter serves as the basis for further development, and can be changed only through formal change control procedures.” Examples: Baseline A: The API of a program is completely defined; the bodies of the methods are empty. Baseline B: All data access methods are implemented and tested; programming of the GUI can start. Baseline C: GUI is implemented, test-phase can start.
- 8. BASELINE IN SCM Baseline A (developmental) All changes relative to baseline A Baseline B (functional) All changes relative to baseline B Baseline C (beta test) All changes relative to baseline C Official Release
- 9. What is Change ? • Change is defined as anything hardware, software, system components, services, documents, or processes that is deliberately introduced into the production environment and which may affect a Service Level Management(SLA) or otherwise affect the functioning of the environment or one of its components.
- 10. Change Management • Software change management encompasses all of the processes necessary to determine where you are at compared to where you planned to be and the activities required to get back on track if those are not aligned.
- 11. Change Management cont.. • Change management is the handling of change requests – A change request leads to the creation of a new release. • General change process – The change is requested (this can be done by anyone including users and developers) – The change request is assessed against project goals – Following the assessment, the change is accepted or rejected – If it is accepted, the change is assigned to a developer and implemented – The implemented change is audited.
- 12. Change Request form • The definition of a change request form is part of the CM planning process. • This form records the change proposed, requestor of change, the reason why change was suggested and the urgency of change(from requestor of the change). • It also records change evaluation, impact analysis, change cost and recommendations (System maintenance staff).
- 13. Change Request form Chan ge Reques t Form Project: Prot eus/PCL-T lsoo Numbe r: 23 /0 2 Chan ge r ques ter:I. So mmerv ille e Date: 1/12 /0 2 Requested change: Whena component isselectedfrom thestructu display re, t he name of t he file wh ere it is sto red. Chan ge ana ly ser: Dean G. Ana lys is date: /1 2/02 10 Compo nents affe cted: Disp lay-Ico n.Select , Disp lay-Ico n.Display As socia ted compo nents: FileTable Chan ge as ses smen t: Relatively simp le t o implemen t as a file name t able is availab Requ the desig and implementation of a display field No chan le. ires n . ges t o associated co mpon ent s are required. Chan ge prio ri ty: w Lo Chan ge imple me nta ti on: Es ti mated effo rt:0.5 days Date to CCB:15 /1 2/02 CCB decis io n date: 1/2/03 CCB decis io n: Accep t ch ange. Chan ge t o be implement ed in Release 2 .1 . Chan ge imple me nto r: Date of chan ge: Date su bmitte d to Q A: Q A decis io n: Date su bmitte d to CM: Comments
- 14. Controlling Changes • Two types of controlling change: - Promotion: The internal development state of a software is changed. - Release: A set of promotions is distributed outside the development organization. Promote Release Policy Policy User Programmer Master Software Promotion Directory Release Repository • Approaches for controlling change to libraries (Change Policy) – Informal (good for research type environments) – Formal approach (good for externally developed CIs and for releases)
- 15. Change Tracking Tools • A major problem in change management is tracking change status. • Change tracking tools keep track the status of each change request and automatically ensure that change requests are sent to the right people at the right time. • Integrated with E-mail systems allowing electronic change request distribution.
- 16. Version Control • Manages file sharing for Concurrent Development. • Keeps track of changes with Version Control • SubVersion (SVN) http://subversion.tigris.org/ is a version control system. • keeps log of any changes made to any file. Ever! Also keeps copies of those changes. For ever! • Participants can go back and receive older versions of a file or even an older version of an entire project state