Management Plan of

Configuration
CEI Library
Configuration Management Plan
CEI Library

This document describes

all activities of
Configuration Management
and Changes that will be
carried out throughout the
project life cycle.

He provides us
detailed planning
of the activities
responsibilities
assigned resources
necessary items that include
personal, tools and
equipment.

Name of the Development Group or Subject

Page 2 of 16
Author's Name
 Configuration Management Plan
CEI Bookstore

Table of contents
Introduction 4
Purpose 5
Scope 5

Configuration Management 5
Tools, Environment, and Infrastructure 5
Tools 5

Configuration Management Program 6

Identification of the Configuration 6
Configuration Elements 6
Nomenclature of Elements 6
Elements of the Project Baseline 12
Configuration Control 12
Change Request 12
Approval of Changes 12
Implementation of Changes 13
Configuration State 13
Reports and Audits 13

Calendar 14

Training and Resources 14

Maintenance of the Configuration Management Plan 14

Name of the Development Group or Subject

Page 3 of 16
Author Name
Configuration Management Plan
CEI Bookstore

Management Plan of
Configuration

Introduction
Configuration planning:

The activities of software configuration management are described that

must be carried out during the project development process. It
define both the products that will be placed under configuration control
how the procedures that must be followed by the members of the
work team.

Definition of the Baseline:

Report on the verification carried out on the configuration objects

what components the current version has to ensure that they are in working condition
consists of the Project's Baseline.

Baseline Monitoring

Receive, record, and maintain all products received through all

their versions.

Change Control:

Tracking the life cycle of a change.

Final Configuration Report:

Prepare the Final Configuration Report, which contains a summary of

the activities carried out of SCM and their results throughout the project.

Produce the Product Version to be Released:

Prepare the Final Configuration Report, which contains a summary of

the activities carried out by SCM and their results throughout the project.

Name of the Development Group or Subject

Page 4 of 16
Author's Name
Configuration Management Plan
CEI Bookstore

Purpose
This document describes the configuration management activities.
software that must be carried out during the development process of the
project. Here, both the products that will be put under control are defined.
configuration as the procedures that must be followed by the
members of the work team.

Scope
The scope of this document is the project <Project Name> and
establish a plan to manage the project's work products,
including both the software deliverables and the documentation of the
project.

Configuration Management
The responsibilities are:

Configuration Planning

Define the Baseline

Baseline Tracking

Change Control

Preparation of the Final Configuration Report

Produce the Product Release Version

Tools, Environment and Infrastructure

Tools

During the configuration management process, the tool will be used.

Subversion for him product version control. When someone
member make a modification in the project, you must access the server
Where is this application hosted to store the part
modified in it, with the rest of the development team having the latest
updated version on that server. This access management to the server

Name of the Development Group or Subject

Page 5 of 16
Author's Name
Configuration Management Plan
CEI Bookstore

The update will be done using the Tortoise tool for the
documents and the Subclise plugin for the source code.

Change control, as well as defect management, will be carried out

through the 'Change Request' template, allowing the team to
developing in detail the defects found so that the person
manager can correct them

All team members will have access to these.

tools.

Configuration Management Program

Identification of the Configuration

Configuration Elements

For this project, the configuration elements will correspond to

the deliverables defined in the Process Model, although not
necessarily all deliverables must be elements of
configuration.

The decision of which of the deliverables will be configuration items

will be taken by the SCMR, which must consider which products
they will be necessary when one wants to recover a complete version of the
system.

A baseline must be generated for each iteration in each phase, according to the
next:

The events that give rise to the baseline.

The elements that will be controlled in the baseline.

The procedures used to establish and change the baseline.

The authorization required to approve changes to the documents of

the baseline.

Nomenclature of Elements

In this section, the identification and unique description of each is specified

configuration element.

Name of the Development Group or Subject

Page 6 of 16
Author's Name
Configuration Management Plan
CEI Library

It also specifies how the different versions of each will be distinguished.

element.

For all configuration elements, they must be added afterwards

of the name of it, information about the group to which it belongs
element and its version.

The format for this nomenclature is: [Link],

where:

Nomenclature is specified below for each element.

X is a 1-digit number that identifies the group.

And indicate the version of the configuration element or deliverable.

Extension indicates the extension of the configuration element or

deliverable.

For the deliverables, it will be necessary to identify which Phase and iteration
they correspond manually. That is: for the elements under control of
Configuration will be stored in such a way that it can be retrieved given the
Phase and iteration to which they correspond, and for the elements that do not
will be stored under configuration control by
example in folders that identify the Phase and iteration to which
belong.

The following nomenclature is indicated for each deliverable in the model of

process, according to the discipline (in case there is any element of
configuration that is added to those detailed below must be included
in the following tables according to the discipline to which it belongs,
indicating the nomenclature used:

Requirements:

Deliverable Nomenclature

RQACT Meeting Minutes of Requirements

RQDRQ Requirements Specification

RQMOD Use Case Model

RQRSU Supplementary Requirements

RQDVC Client Validation Document

RQPIU Guidelines for User Interface

RQRCA Candidate Requirements

Name of the Development Group or Subject

Page 7 of 16
Author Name
Configuration Management Plan
CEI Library

RQALS Scope of the System

RQGLO Glossary

RQOOMDO Domain Model

RQOODRP Requirements Document for the Prototype

RQGXNOM Nomenclature

Name of the Development Group or Subject

Page 8 of 16
Nombre del Autor
Configuration Management Plan
CEI Bookstore

Design:

Nomenclature
Deliverable
DSMDI
Design Model
DSARQ
Description of Architecture
DSOOMDA
Data Model
DSOODDP
Prototype Design Document

Implementation:

Nomenclature
Deliverable
IMEDT
Technical Documentation Standard
IMEI
Implementation Standard
IMPR
Prototype
IMIIN
Integration Report
IMDT
Technical documentation

IMIVU Unit Verification Report

IMOOPII Integration Plan of the Iteration

IMOOMIM Implementation Model

IMOOEJI Executable of the Iteration

IMOORRP Peer Review Report

IMOOCVU Unit Testing Module Classes

IMGXICO Consolidation Report

IMGXEST BC With Styles

IMGXCON BC Consolidated

IMGXNUC BC Core

IMGXMOD BC Module

Name of the Development Group or Course

Page 9 of 16
Author's Name
Configuration Management Plan
CEI Library

Verification:

Nomenclature
Deliverable

VRPVV Verification and Validation Plan

VRDAP Evaluation and Adjustment Document of the V & V Plan

VRPVI Verification Plan of the Iteration

VRMCP
Test Case Model

VRIVD Document Verification Report

VRIVI Integration Verification Report

VRIVS System Verification Report

VRRPR Test Reports

VREV Verification Assessment

VRIFV Final Verification Report

Implementation (IP):

Nomenclature
Deliverable
IPMSU
Materiales para Soporte al Usuario

Suffixes can be used to identify each item.

within the material Ej. IPMSUMU for Manual of
User)

IPMCA Training Materials

IPPS System Presentation

IPPLA Implementation Plan

IPVPR Product Version

IPOOEDU User Documentation Standard

IPOORFPA Final Acceptance Test Report

Name of the Development Group or Subject

Page 10 of 16
Author Name
Configuration Management Plan
CEI Bookstore

Configuration Management and Change Control (SCM):

Nomenclature
Deliverable

SCMPLA Configuration Plan

SCMMAC
Controlled Environment Management
SCMGC
Change Management
SCMRV
Version Log
SCMILB
Baseline Report of the Project
SCMIF
Final Report of SCM

Quality Management (SQA):

Nomenclature
Deliverable
SQAPLA
Quality Plan
SQADAP
Evaluation and Adjustment Document of the Plan
Quality

SQARTF RTF Report

SQAES
Weekly SQA Delivery

SQAIR SQA Review Report

SQADV Version Description

SQANV Release Notes

SQAIF
Final SQA Report

Name of the Development Group or Subject

Page 11 of 16
Author Name
Configuration Management Plan
CEI Bookstore

Project Management (PM):

Nomenclature
Deliverable
GPPLA
Project Plan
GPISP
Project Situation Report
GPEM
Estimations and Measurements
GPDRI
Risk Document
GPRAC
Activity Log
GPIFP
Final Project Report
GPARE
Minutes of the Team Meeting
GPPIT
Iteration Plan
GPPDE
Development Plan
GPICF
Conclusions Report of the Phase
GPPDP
Presentation to the Project Director
GPARD
Minutes of the Meeting with the Project Director
GPOODAP
Evaluation and Adjustment Document for the Plan
Project
GPIARI
Minutes of the Integration Meeting

Communication (COM):

Nomenclature
Deliverable
COMDI
Informative Document
COMENS
Customer Satisfaction Survey
COMEVS
Customer Satisfaction Assessment

Group Name of Development or Subject

Page 12 of 16
Nombre del Autor
Configuration Management Plan
CEI Bookstore

Elements of the Project Baseline

N/A

Configuration Control
This section details the activities of request, evaluation,
approval and implementation of changes to the baseline elements.

The changes aim at both correction and improvement.

The procedure described below is the one that will be used each
a time when it is necessary to introduce a change to the system.

Change to the system refers to the modifications that affect the line.
system base, such as:

Changes in the Requirements.

Changes in the Design.

Changes in Architecture.

Changes in development tools.

Changes in the project documentation. (add new

documents or modify the structure of the existing ones

Change Request

When a request for a change is made, the document is updated.

Change request to register this request.

All necessary information, detailed in the document, must be provided.

Approval of Changes

Se debe formar el “Comité de Control de Configuración” y determinar su

authority for the approval of changes.

The composition of this committee may vary according to the exchange rate and the
work lines involved in it.

They are suggested as possible members:

Name of the Development Group or Subject

Page 13 of 16
Author Name
Configuration Management Plan
CEI Bookstore

Administrator (mandatory)

Architect (optional)

Analyst (optional)

Implementer (optional)

SCM (mandatory)

Client (optional)

A higher-level Configuration Control Committee is defined,

composed of the Project Manager, to whom the requests will be submitted.
changes whose approval or disapproval cannot be resolved by the
first committee.

Implementation of Changes

Once the change assessment is completed, it is decided when

implement it. This stage involves the necessary processes to
implement the request and monitor the progress of the work.

It will also specify the moment of the change release; as well as

also those responsible for the activities involved in the change.

Remembering that we are based on an incremental development process and

iterative, where in each iteration tasks of Analysis are performed
requirements, Design, Implementation and Verification; it must be introduced the
change in the area that originated it and continue with the activities of the cycle
(Requirements, Analysis, Design, Implementation, Verification) that
they will impact the baseline elements corresponding to each
activity.

Configuration Status
N/A

Name of the Development Group or Subject

Page 14 of 16
Author's Name
Configuration Management Plan
CEI Bookstore

Reports and Audits

Every now and then, the configuration and change manager will carry out a
report for the project manager in order to review the progress of the
defects that are recorded in it.

This report ('Defect Evolution Report') will detail the

defectos detectados, sus prioridades, responsables de corregirlos, su estado
and the procedure that has been followed or will be followed at the time of
to solve them.

This will allow us to obtain a series of indicators to determine the

quality of the product being developed, allowing the manager to
project to inform the client about this aspect.

The audits that will be conducted to verify if the changes have been made
done correctly will be at the end of each iteration, but before that
a baseline is created. In these, both the functional requirements will be reviewed.
and performance, as the product meets the specifications
detailed in which it is defined. The client and the boss will participate in these.
project and the configuration manager.

Calendar
The definition of the baseline will be determined at the beginning of each
week in the following way: svn_repository_path/trunk/weekX
where X corresponds to the current week.

There is no implementation of Change Control yet.

Training and Resources

SVN is used for version management.

Maintenance of the Management Plan of the

Configuration
The person responsible for monitoring the SCM Plan is the SCM manager.

There is no stipulated time for the frequency of modifications, they will be

the necessary ones, always limited to the time of completion of the iteration.

This Plan must be reviewed at the beginning of each phase, modified accordingly
to the necessary, approved and distributed to the project team.

Name of the Development Group or Subject

Page 15 of 16
Author's Name
Configuration Management Plan
CEI Bookstore

Name of Development Group or Subject

Page 16 of 16
Author Name