of 27
8/8/2019 SW Configuration Mgmt
1/27
GSFC
SPI
Software Configuration
Management
Presented by: Susan SekiraSoftware Process Improvement (SPI) Project
8/8/2019 SW Configuration Mgmt
2/27
Software Configuration Management, March 2008 2
GSFC
SPI
Agenda
s Configuration Management (CM) Background CM Concepts
CM Benefits
Process Overviews Configuration Management Implementation
Planning and Startup Tasks
Execution Taskss CM Support Information
8/8/2019 SW Configuration Mgmt
3/27
Software Configuration Management, March 2008 3
GSFC
SPI
Purpose and Objectives
s Purpose: Describe CM Concepts and theimplementation approach
s Objective: After this session you should
understand: Four key functions of CM
How to apply CM to your project
Which CM records to maintain
Where to find additional information on CMprocesses and tools
8/8/2019 SW Configuration Mgmt
4/27
Software Configuration Management, March 2008 4
GSFC
SPI
Configuration Management Overview
s The purpose of Software ConfigurationManagement (CM) is to establish and maintain theintegrity of products throughout the software lifecycle
s Software CM involves four key functions:1. identification of work products and baselines that are
subject to configuration control
2. control (i.e., approval/rejection) of proposed changes toconfiguration items
3. status accounting of configuration data and changes
4. audits to maintain the integrity of the configurationbaselines
8/8/2019 SW Configuration Mgmt
5/27
Software Configuration Management, March 2008 5
GSFC
SPI
CM Benefits
s
Improves Product protection
Product visibility
Product control
Team communication
Customer Confidences Decreases
Rework
Confusion
Project Risk
8/8/2019 SW Configuration Mgmt
6/27
Software Configuration Management, March 2008 6
GSFC
SPI
Key Definitions
s Configuration Item (CI) - an aggregation of workproducts (e.g., hardware, software, firmware, or documentation) that is designated for configuration management and treated as asingle entity in the configuration managementprocess
s Baseline a set of specifications or workproducts that has been formally reviewed andagreed on, which thereafter serves as the basis
for further development, and which can bechanged only through change controlprocedures. Typically defined for each projectlife-cycle phase
8/8/2019 SW Configuration Mgmt
7/27
Software Configuration Management, March 2008 7
GSFC
SPI
Configuration Management Rolesand Responsibilities
s Product Development Lead (PDL) - Responsible for CMplanning and overall control and approval of CMactivities and tools. Develops and maintains theprojects CM Plan
s Configuration Management Officer (CMO) Implements and maintains the CM system according tothe projects CM Plan. Coordinates, supports, andperforms CM activities and reports those activities tothe PDL
s Control Board composed of technical andadministrative representatives who recommendapproval/disapproval of changes to a CI or baseline(e.g., Configuration Control Board (CCB), InternalReview Board (IRB))
8/8/2019 SW Configuration Mgmt
8/27
Software Configuration Management, March 2008 8
GSFC
SPI
Configuration Management ProcessOverview
Work products;change
requests
Controlled work products;
approved changerequests
Status reports;audit results
CM Plan
Project Management Processes
Project Planning
ProjectMonitoring &
Control
Project Startup
Project Closeout
ProjectFormulation
Product Development Processes
Requirements
Engineering
Product ReleaseSustaining
Engineering &Maintenance
Design
Implementation
Testing
Systems
Engineering
ConfigurationManagement
Process
Planning Data
8/8/2019 SW Configuration Mgmt
9/27
Software Configuration Management, March 2008 9
GSFC
SPI
Configuration Management Tasks
CM planning and startup tasks
Establish thesoftware
project CCBSetup CM toolsand libraries
Define levels of control and
responsibilities
Identifyconfiguration
items
Define CMprocedures
Prepare the CMPlan
CM execution tasks
Identify workproducts/baselines
Perform
configurationcontrol
Perform
configurationstatus accounting
Perform
configurationaudits
NOTE: See the ISD Software Configuration Management Asset, 3.1, for complete task descriptions
8/8/2019 SW Configuration Mgmt
10/27
GSFC
SPI
CM Planning and Startup Tasks
Establish thesoftware
project CCB
Setup CM toolsand libraries
Define levels of control and
responsibilities
Identifyconfiguration
items
Define CMprocedures
Prepare the CMPlan
8/8/2019 SW Configuration Mgmt
11/27
Software Configuration Management, March 2008 11
GSFC
SPI
CM Planning/Startup Tasks (1 of 2)
s Identify the CIs (e.g., deliverable products,interim products, requirements, software) anddefine the naming conventions
s Identify the levels of control for each CI
s List the identified items in the datamanagement list ( DML)
s Determine when each item will be placed under configuration control (i.e., Baselined )
s Select a role that is responsible for maintainingthe integrity of items under CM
s Establish a CCB or IRB to manage, assess, andcontrol changes to configured items
8/8/2019 SW Configuration Mgmt
12/27
Software Configuration Management, March 2008 12
GSFC
SPI
CM Planning/Startup Tasks (2 of 2)
s Define the mechanism used to control changes Change requests (e.g., What forms / tools will be
used?) CCB / IRB (e.g., What meetings (if any) will be
held? How will changes be dispositioned, logged ,and tracked ?) Audits to confirm the approved changes and
ensure the integrity of the configuration baseliness
Identify tools used to support CM and how theywill be used (e.g., MKS, CVS, ClearCase)s Document approaches, procedures, and tools in
a separate CM Plan or as part of your SMP/PP
8/8/2019 SW Configuration Mgmt
13/27
GSFC
SPI
CM Execution Tasks
Performconfiguration
control
Performconfiguration
status accounting
Performconfiguration
audits
Identify workproducts/baselines
8/8/2019 SW Configuration Mgmt
14/27
Software Configuration Management, March 2008 14
GSFC
SPI
1 - Configuration IdentificationIdentify Work Products and Baselines
s Document the baseline items in the BaselinesTable in the SMP/PP
s Identify by phase (per your life cycle model) the CIsthat will be baselined or re-baselined
Go to http://software.gsfc.nasa.gov/tools.cfm and look for CM Baselines Template
.
8/8/2019 SW Configuration Mgmt
15/27
Software Configuration Management, March 2008 15
GSFC
SPI
Recording the Baselines
s
Update the Baselines Table at the conclusion of each phase to record the baseline date and thebaseline versions for each configured item
s Save your updated Baselines Table asspecified in your DML
.
8/8/2019 SW Configuration Mgmt
16/27
Software Configuration Management, March 2008 16
GSFC
SPI
Document CIs in Data Management List (DML)
Go to http://software.gsfc.nasa.gov/tools.cfm and look for Data Management List
8/8/2019 SW Configuration Mgmt
17/27
Software Configuration Management, March 2008 17
GSFC
SPI
2 - Configuration Control
sIdentify and record desired changes to abaselined item
s Define the need / problem rather than thedesired resolution
s Document the analysis of change Impact analysis, costs, urgency
s Review and disposition each change requests
Use a tool* to record and track the status of all change requests
*Go to http://software.gsfc.nasa.gov/tools.cfm and look for Change Request Formand Change Request Log Template
8/8/2019 SW Configuration Mgmt
18/27
Software Configuration Management, March 2008 18
GSFC
SPI
Change Request Form and Log
Describing
the desiredchange
Thoroughlyanalyzing the
change
Decision andformal
approval
ProjectName:
TrackingNumber Item Type Systems/Subsystems Short Description of Change Urgency Requestor
DateSubmitted
Analysis AssignedTo: Result
Change Request Log
Keeping track of all the desired changes
8/8/2019 SW Configuration Mgmt
19/27
Software Configuration Management, March 2008 19
GSFC
SPI
3 Configuration Status Accounting
s Maintain records of the CIs throughout theprojects life cycle
s Record and monitor all changes to CIss Document the contents of versions, builds,
and baseliness Generate periodic status reports your CM
tool may provide the reporting for you!
8/8/2019 SW Configuration Mgmt
20/27
Software Configuration Management, March 2008 20
GSFC
SPI
4 Configuration Audits
s Conduct audits to maintain the integrity of theconfiguration baselines
s Three types of CM Audits are required: Baseline Audit
Functional Configuration Audit (FCA)
Physical Configuration Audit (PCA)
s Audits correspond to major milestones andmust be planned and on your schedule
8/8/2019 SW Configuration Mgmt
21/27
Software Configuration Management, March 2008 21
GSFC
SPI
Baseline Audit
s Conducted at the end of each life cycle phaseor at each major delivery
s Conducted by the teams CMO or designatedteam personnel; reviewed by the teams
Software Quality Engineer (SQE)s Baseline Audit -- verifies the content of the
baseline Correct versions of CIs were used to build the
baseline
Correct version of documentation are includedin the baseline
8/8/2019 SW Configuration Mgmt
22/27
Software Configuration Management, March 2008 22
GSFC
SPI
FCA and PCA
s
Functional Configuration Audit ( FCA ) -- Verifiesfunctionality of baseline after final testing Ensures that CIs achieve the performance and functional
requirements Ensures that operational and support documents are
complete and satisfactorys Physical Configuration Audit ( PCA ) -- Verifies content of
baseline for major builds or deliveries Ensures that baseline items of a delivery match the
documentation that defines it (e.g., Version DescriptionDocument (VDD), design documents)
s Both conducted by the teams CMO or designatedteam personnel; verified by the teams SQE
8/8/2019 SW Configuration Mgmt
23/27
Software Configuration Management, March 2008 23
GSFC
SPI
CM AssetsProcedures, Guidelines, and Tools
Go to http://software.gsfc.nasa.gov/process.cfm and look under Organizational Support
8/8/2019 SW Configuration Mgmt
24/27
8/8/2019 SW Configuration Mgmt
25/27
Software Configuration Management, March 2008 25
GSFC
SPI
Summary
s Software Configuration Management establishesand maintains the integrity of products throughout thesoftware life cycle
s CM planning and implementation support
include: Configuration Identification
Configuration Control
Configuration Status Accounting Configuration Audits
s CM records must be organized and maintained
8/8/2019 SW Configuration Mgmt
26/27
Software Configuration Management, March 2008 26
GSFC
SPI
Questions?
8/8/2019 SW Configuration Mgmt
27/27
Software Configuration Management, March 2008 27
GSFC
SPI
Acronyms
CCB Configuration Control BoardCI Configuration ItemCM Configuration ManagementCMO Configuration Management Officer CR Change Request
DML Data Management ListFCA Functional Configuration AuditIRB Internal Review BoardISD Information Systems DivisionPCA Physical Configuration AuditPDL Product Development LeadSMP/PP Software Management Plan/Product PlanSPI Software Process ImprovementSQE Software Quality Engineer VDD Version Description Document