Configuration Management Process
Manual
(QMS-ISPL-M-CMP)
|
Version No |
V20 |
Prepared by |
|
|
Date |
30-01-2015 |
Name |
Suman |
|
Signature |
|
||
|
Date |
30-01-2015 |
||
|
Copy No |
|
Approved by |
|
|
Issued to |
|
Name |
Sai Prasad Koneru |
|
Signature |
|
||
|
Date |
30-01-2015 |
||
Document Amendment Record
A-
A-
Added,
M- Modified, D- Deleted
|
Sl.No |
Date |
Version No |
Page No |
Change Mode(A/M/D) |
Brief description of change |
|
1 |
|
V01 |
N/A |
A |
Initial Release |
|
2 |
|
V02 |
N/A |
A |
Included
Section 8 Records |
|
3 |
|
V03 |
N/A |
M |
In section 8 (records) Modified the
Naming conventions for documents / records with inclusion of Purchase Tracker
and Approved Vendor's List |
|
4 |
06-06-2012 |
V03 |
N/A |
D |
The Company address information is
removed from the Footer |
|
5 |
30-01-2015 |
V20 |
N/A |
N/A |
Reviewed and base lined |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
5 Entry criteria, Activities, Input, Output,
Exit criteria
7.1 Preparation, review and approval of
configuration management plan
7.2 Creation of configuration items
7.6 Configuration status accounting
1
Purpose
To establish and maintain a configuration management
process to manage versions and releases of
all the components of a project throughout the software development life cycle.
2
Objective
The objectives of software configuration management are to
Ř
Identify,
record and control configuration item (CI) versions and changes throughout the
software development life cycle.
Ř
Track
and report the status and history of each CI as it is developed, modified and
base lined.
Ř
Record
the status of each new build of the project.
Ř
Control
and authorize new versions and releases.
3
Scope
Configuration
management is applicable to all the projects undertaken by Inooga
Solutions.
4
Terms and definitions
|
Abbreviations/Terms |
Description |
|
QMS |
Quality
Management System |
|
ISPL |
Inooga
Solutions Pvt. Ltd. |
|
CEO |
Chief
Executive Officer |
|
CTO |
Chief
Technology Officer |
|
CI/Configuration Item |
An entity within a configuration that
satisfies an end use function and that can be uniquely identified at a given
reference point. An
aggregation of hardware, firmware, computer software, or any of their
discrete portions, which satisfies an end use function and is designated for
separate configuration management. Configuration items may vary widely in
complexity, size, and type. Any item required for logistic |
|
Baseline |
A
formally approved version of a configuration item, regardless of media,
formally designated and fixed at a specific time during the configuration
items life cycle. |
5
Entry criteria, Activities,
Input, Output, Exit criteria
|
Sl.No |
Entry Criteria |
Input |
Activity |
Output |
Exit Criteria |
|
1 |
Completion
of requirements analysis. |
SRS |
Preparation,
review and approval of configuration management plan. |
Configuration
management plan and review of records. |
Approval
and release of configuration management plan. |
|
2 |
CI
is ready for approval. |
Approved
CI. |
Configuration
control. |
CI
is moved to the configuration control area. |
CI
is put under configuration control. |
|
3 |
Availability
of CI’s which work together. |
Availability
of required CI’s under configuration control. |
Baseline. |
Baseline
record. |
Availability
of base lined product. |
|
4 |
Need
for changes in CI. |
Change
request. |
Change
control. |
Change
is approved, implemented and reviewed, updated CI in the configuration
control library. |
Closure
of change request. |
6
Responsibilities
|
Sl.No |
Activity |
Responsibility |
|
1 |
Preparation
of configuration management plan |
Project
leader/Project manager |
|
2 |
Review
and approval of configuration management Plan |
CEO/CTO |
|
3 |
Implementation
of configuration management plan |
Project
leader/Project manager |
|
4 |
Change
request |
Project
leader/Project manager |
|
5 |
Review
and approval of change request |
CTO/Project
manager |
|
6 |
Implementation
of changes |
Team
members |
7 Process description
7.1 Preparation,
review and approval of configuration management plan
The project manager studies the
configuration management requirements for the project and identifies the
following:
Ř
Configuration items in the project.
Ř Possible configuration management tools/methods
Ř
Directory structure and naming
conventions of all project-related items.
Ř Baseline type and phase during which baseline are to be
completed.
Ř Process to be handled the change request.
The configuration management aspects identified above are
recorded in the respective project management plan. Project manager prepares a
configuration management plan for the project as a part of the project
management plan. Configuration management plan is reviewed and approved by CTO.
Configuration management plan reflects the configuration management activities
as outlined in this process, applicable for a specific project or product. In
case the customers provide the development environment including configuration
management tool then the same are used.
7.2 Creation of configuration items
For items identified in the
configuration management plan, project manager creates project directory and
sub directories along with access permission in the project server by using
suitable tools such as Visual Source Safe (VSS) or any other applicable
tool. Project manager ensures that the
project's configuration items as per configuration management plan are
identified, created, reviewed, approved and checked into the configuration
library. In case no tools are used for configuration management, these items
are physically checked into the software library.
7.3 Check out
Whenever a
software item in the configuration library requires to be taken out, the
responsible person of the item checks out a copy of the item from the VSS and
configuration library.
7.4 Baseline
Baseline is defined as “product that
has been formally reviewed and approved, that thereafter serves as a basis for
further development, and that can be changed only through formal change control
procedure”. When all items required for the project/product are ready, project
manager creates a baseline of the product consisting of all the required
software items. Master copy of the baseline is checked in to the software
library. The master copy of the baseline is used for making replication and
delivery to the customer. Baseline is created as per format baseline creation
record.
7.5 Change control
7.5.1
Need for changes in software
items
Changes to
software items that have been kept under configuration management need to be
implemented formally by following change control method described herein.
Changes to the software items originate due to product non-conformities
observed during product integration, installation or usage. Whenever such
product non-conformities are reported, project manager initiates change control
activities.
7.5.2
Change request
Any change to
configuration items, which have been base lined, are initiated through a change
request in accordance with the change request form to the project manager. A
change request from a customer or external entity may come by email, fax, or
telephone. The request is logged using the change request form
(QMS-ISPL-F-CHR). Project manager assigns a unique change request number to
each of the change requests for tracking purpose and record the assignment of
the same in the WBS.
Project
manager evaluates the impact of the changes in terms of –
Ř Effort.
Ř Schedule.
Ř
Cost of not
incorporating the change.
Ř Contract/ work order.
Ř
Configurable
items impacted and the extent of impact.
The findings
of the impact analysis are documented in the change request form. In case the
change request has impact on schedule/cost or contractual items and conditions
the same are escalated to the customer and approval is obtained before
implementing the change request whenever a change request is rejected/not
approved, the reason is documented in the change request form by project
manager and the change request initiator is intimated. The project manager
checks the impacted components to the allocated team members. The team members
incorporate the requisite change in accordance with the change request. On
incorporation of change into impacted component & completion of regression
testing, the changed component is base lined. Change request indicates software
items on which change is proposed, nature of change and justification for the
change.
7.5.3
Review and approval of
change request
Project leader
submits the change request to the head development for review and approval.
Head development reviews the change request and approves the change request
only if the change is justifiable. Otherwise the change request is rejected.
Only approved change requests are taken up for implementation.
7.5.4
Implementation of changes
Project
leader takes up implementation of changes only on the approved change requests.
Steps
involved in the implementation of approved change requests are:
a) Checking a copy of the item from the configuration library.
b) Implementation of the approved
changes on the item.
c)
Verification and validation of
the changes implemented on the software item. If the software Item is a product, testing is done on
the product and a test report is generated. If the item is a non-product,
review is done as per review record. The test or review observation
are corrected and verification is repeated.
d) After the implementation of
changes is found to be satisfactory, the software item is
checked into the
configuration library.
e) Project leader maintains a log
of changes implemented in the project.
f)In case the customer reports
non-conformity, corrected product is delivered to the customer.
g)
Based upon the analysis of the changes done by the quality assurance
department, project coordinator/project leader initiates corrective and
preventive actions.
7.6 Configuration status accounting
Project
leader keeps track of the change requests and implementation status on a
monthly basis. These observations are recorded in change request log.
7.7 References
Change request form (QMS-ISPL-F-CHR).
Change request log (QMS-ISPL-L-CHR).
Naming conventions for documents/records (QMS-ISPL-F-NCD).
|
Sl.
No |
Required
Record |
Custodian |
Retention
Period |
Record
ID |
|
1. |
Change
Request Form |
Project
Manager |
N/A |
|
|
2. |
Change
Request Log |
Project
Manager |
N/A |
|
|
3. |
Naming
conventions for documents / records |
MR |
N/A |