Scribd
Upload
116 views

Lec25 - Software Configuration Management Process

The document discusses the software configuration management (SCM) process, which has four primary objectives. It defines five key SCM tasks: (1) identification - identifying discrete software elements, (2) version control - managing different versions of software and documentation, (3) change control - controlling changes before and after release, (4) configuration auditing - assessing the impact of changes, and (5) reporting - apprising others of changes. Each task is then discussed in more detail, including how identification aggregates objects, version control systems store versions and enable constructing specific versions, change control manages the change process, auditing checks that changes were properly implemented, and reporting communicates change status.

Uploaded by

Owais Taha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
116 views

Lec25 - Software Configuration Management Process

The document discusses the software configuration management (SCM) process, which has four primary objectives. It defines five key SCM tasks: (1) identification - identifying discrete software elements, (2) version control - managing different versions of software and documentation, (3) change control - controlling changes before and after release, (4) configuration auditing - assessing the impact of changes, and (5) reporting - apprising others of changes. Each task is then discussed in more detail, including how identification aggregates objects, version control systems store versions and enable constructing specific versions, change control manages the change process, auditing checks that changes were properly implemented, and reporting communicates change status.

Uploaded by

Owais Taha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

Software Configuration

Management Process.

Lecture 25
SCM Process
The software configuration management process defines a series
of tasks that have four primary objectives:
The following questions lead to the definition of five SCM tasks—
identification, version control, change control, configuration auditing,
and reporting, as shown in previous fig.
• How does a software team identify the discrete elements of a
software configuration?
• How does an organization manage the many existing versions of a
program (and its documentation) in a manner that will enable change
to be accommodated efficiently?
• How does an organization control changes before and after software
is released to a customer?
• How does an organization assess the impact of change and manage
the impact effectively?
• Who has responsibility for approving and ranking requested changes?
• How can we ensure that changes have been made properly?
• What mechanism is used to apprise others of changes that are made?
Identification of Objects

aggregate objects.
Version Control
A version control system implements or is directly
integrated with some major capabilities:
(1) a project database (repository) that stores all relevant
configuration objects,
(2) a version management capability that stores all
versions of a configuration object (or enables any
version to be constructed using differences from past
versions),
(3) a make facility that enables you to collect all relevant
configuration objects and construct a specific version
of the software. In addition, version control and
change control systems often implement an issues
tracking (also called bug tracking) capability that
enables the team to record and track the status of all
outstanding issues associated with each configuration
object.
For example:
GitHub is a code hosting platform for version
control and collaboration. It lets you and others
work together on projects from anywhere.
Change Control
Fig: The change control
process.
Configuration Audit
The audit asks and answers the following questions:
1. Has the change specified in the ECO (Engineering
change order) been made? Have any additional
modifications been incorporated?
2. Has a technical review been conducted to assess
technical correctness?
3. Has the software process been followed and have
software engineering standards been properly applied?
4. Has the change been “highlighted” in the SCI? Have the
change date and change author been specified? Do the
attributes of the configuration object reflect the change?
5. Have SCM procedures for noting the change, recording
it, and reporting it been followed?
6. Have all related SCIs been properly updated?
Status Reporting
SCM Standards

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy