Spm unit iii-configuration mgmt-responsibilities

1. SPM-UNIT IV
CONFIGURATION MANAGEMENT
RESPONSIBILITIES
Prof. Kanchana Devi

2. Baselines
Prof. Kanchana Devi
2
 Foundation for Configuration Management
 Provides official standard for subsequent
work is based - only authorized changes are
made.
 After an initial baseline is established –
every change is recorded as a delta until
next baseline is set.
 Baseline Scope:
 Current level of each module, test cases,
assembler, macros, any installation

3. Responsibilities
Prof. Kanchana Devi
3
 To implement the necessary controls
and procedures:
 Depends on the size of the system and the
number of people involved, they may be
handled by a single individual, several
people,or an entire organization.
 The basic responsibilities are:
 Configuration Manager
 Module Ownership
 Change Control Board(CCB)

4. Sample Test Report Contents
Prof. Kanchana Devi
4
 Responsibilities:
 Developer
 Development Manager
 Tester
 Test identification:
 Test Date
 Product Name(Revision Number)
 Test Cases Used(Identification Number)
 Test Data Used
 Test Configuration(Hardware & Software)
 Test Results:
 Problem Reports(Numbers)
 Test Result Summary(by test case)

5. Sample Problem Report Contents
Prof. Kanchana Devi
5
 Problem Identification:
 Problem Number
 Date Discovered
 Date Reported
 Product(s) involved
 System(s) involved
 Originator Identification:
 Name, address, Phone, Organization,Function
 Problem Description:
 Severity:
 Critical,Severe,Normal,Inconvenience, Suggestion
 Status:
 Waiting,Bypass,Temporary Fix
 Symptom Description
 Probable Cause
 Conditions
 Problem Fix/Bypass Description

6. Some Responsibilities of
Configuration Manager:
Prof. Kanchana Devi
6
 Develop, document, and distribute the SCM
procedure
 Establish the system baseline, including backup
provisions
 Ensure that no unauthorized changes are made
to the baseline
 Ensure all the baseline changes are recorded
 Ensure all the baseline changes are regression
tested
 Provide the focal point for exception resolution.

7. Module Ownership
Prof. Kanchana Devi
7
 Know and understand the module design
 Provide advice to everyone who works on
 Serve as technical control point for all
module modification
 Ensure module integrity by reviewing all the
changes

8. Change Control
Board(CCB)
Prof. Kanchana Devi
8
 For very large projects, a central control
mechanism is needed to ensure that every
change is properly considered and coordinated
 This is the role of “CCB”
 Sometimes called “Configuration Control Board”
 It includes members from development,
documentation, test, assurance, maintenance,
and release.
 Purpose: to ensure that every baseline change is
properly considered

9. CCB needs the following for each
proposed change:
Prof. Kanchana Devi
9
 Size
 Alternatives
 Complexity
 Schedule
 Impact
 Cost
 Severity
 Relationship to other changes
 Test
 Resources
 System impact
 Benefits
 Politics
 Change maturity

10. Change Control Plan
Prof. Kanchana Devi
10

11. Judging Configuration
Management
Prof. Kanchana Devi
11
 Number of defects reported due to incorrect
or inappropriate configuration control
 Goal: Maximizing the productivity by
minimizing the mistakes

12. Link For SCM(Video Lecture)-IIT
Bombay
Prof. Kanchana Devi
12
 http://www.youtube.com/watch?v=lvVvMms
pMYk

13. Prototype
Prof. Kanchana Devi
13
 Definition: Activity of creating prototypes of
software applications
 i.e., incomplete versions of the software
program
 Dimensions of prototype:
 Horizontal Prototype
 Vertical Prototype

14. Horizontal Prototype
Prof. Kanchana Devi
14
 It provides a broad view of an entire system or
subsystem, focusing on user interaction more
than low-level system functionality, such as
database access
 Horizontal prototypes are useful for:
 Confirmation of user interface requirements and
system scope
 Demonstration version of the system to obtain buy-
in from the business
 Develop preliminary estimates of development time,
cost and effort.

15. Vertical Prototype
Prof. Kanchana Devi
15
 A vertical prototype is a more complete
elaboration of a single subsystem or function
 It is useful for obtaining detailed requirements
for a given function, with the following benefits:
 Refinement database design
 Obtain information on data volumes and system
interface needs, for network sizing and performance
engineering
 Clarifies complex requirements by drilling down to
actual system functionality

16. Types of Prototype
Prof. Kanchana Devi
16
 Throwaway prototyping
 Evolutionary prototyping
 Incremental prototyping
 Extreme prototyping

17. Advantages of Prototypes
Prof. Kanchana Devi
17
 Reduce time & Cost
 Improved & increased user involvement

18. Disadvantages of Prototype
Prof. Kanchana Devi
18
 Insufficient analysis
 User confusion of prototype and finished
system
 Developer misunderstanding of user
objectives
 Developer attachment to prototype
 Excessive development time of the prototype
 Expense of implementing prototyping