Assignment 9

Module 9 Configuration Management

__________________________________________________________________
1. What do you understand by Software Configuration Management (SCM)?
Ans:-
The purpose of configuration management is to establish and maintain the
integrity of the product of the software or system through the project and
product life cycle.

CM is about keeping track of different versions and iteration of the projects.

For testing, configuration management will involve controlling both the

versions of code to be tested and the documents used during the development
process (e.g. requirements, design and plans), so that traceability can be
maintained throughout the test process.

Approval/Rejection of requirement done by configuration management team.

During test planning, the configuration management procedures and

infrastructure (tools) should be chosen, documented and implemented.
Configuration Management Activities
Configuration Item Identification:
Identify software configuration items in a baseline.

Change Control:
Controlling the release of a product and changes to it throughout the
software life cycle.

Status Accounting:
The process of recording and reporting configuration item descriptions and
changes from the baseline over the items life-cycle.
If a problem arises, this allows for a quick determination of the baseline
configuration and changes that have taken place over time.
 Audits:
Validating the completeness of a product and that Software Configuration
Management procedures are being followed.

2. Name the items that are identified for Configuration Management?

Ans:- Process of identifying documents of SDLC which has to be baseline.
Configuration Items Identification
Identify which configuration item has to change.
Product concept documents
Software Requirements
Software Design descriptions
Source Code
Software Release Process
Software Test Documents
Project Plan
Development Plan
User Documentation

3. Who are the Project people involved in the Configuration Control Board
(CCB)?
Ans:-
A board composed of technical and administrative representatives who
recommend the approval or disapproval of proposed requirement changes to
a baselined config item.

Basically the CCB is responsible for baselining specific configuration items:

documents, designs, requirements, products, product components, etc.

Once a configuration item has been baselined, the CCB is then responsible for
reviewing and approving Change Requests to a baselined configuration item.

If the CCB approves a change to a configuration item, after the item and other
associated changes have been updated, then there is a new baseline version.
Configuration Control Board
Project Manager:- The project manager approves to indicate:
All tasks associated with the change are completed.
 All deliverables required for the change are implemented, tested, and
integrated into the release.

User Representative:- It is representative from client Site

Funding Manager:-
The funding manager approves to indicate that the financial impacts or risks
are understood and they are acceptable.

Configuration Manager:- The Configuration manager approves to indicate:

The CM team has received and checked into the project repository all new
and changed components, documents, and other associated deliverables, and
identified those deliverables in the repository with the appropriate change
request/bug report identifier.
The CM team is prepared to integrate the change into the scheduled or
emergency release/patch , build, and package a release containing the change
as part of the scheduled release or emergency release/patch, as appropriate.

Quality Manager:- The Quality Manager approves to indicate:

The test team has subjected the change an agreed-upon set of tests.
The quality manager has presented the test results to the CCB, including a
discussion of the business and technical risks assessed and mitigated and those
business and technical risks not assessed or mitigated.

System Engineers:- The System engineers approves to indicate:

The change has not introduced any major technical or business impact issues
or risks.
Any issues introduced have a corresponding customer response documented
and posted on the support database and any risks introduced have been
appropriately mitigated.