0% found this document useful (0 votes)
9 views25 pages

05 - Software Configuration Management-SCD

The document outlines the concepts and activities involved in Software Configuration Management (SCM), emphasizing the importance of managing software configurations due to collaborative development and evolving user requirements. It details key activities such as configuration identification, change control, and status reporting, along with definitions of baseline and version control. The aim is to ensure that software systems are organized, traceable, and compliant with specified requirements throughout their lifecycle.

Uploaded by

Rachmat Taufik
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
0% found this document useful (0 votes)
9 views25 pages

05 - Software Configuration Management-SCD

The document outlines the concepts and activities involved in Software Configuration Management (SCM), emphasizing the importance of managing software configurations due to collaborative development and evolving user requirements. It details key activities such as configuration identification, change control, and status reporting, along with definitions of baseline and version control. The aim is to ensure that software systems are organized, traceable, and compliant with specified requirements throughout their lifecycle.

Uploaded by

Rachmat Taufik
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/ 25

Manajemen Konfigurasi dan Evolusi

Perangkat Lunak

PERTEMUAN 5
Software Configuration Management
Expected Outcome

Mahasiswa mampu menjelaskan konsep konfigurasi


perangkat lunak dan manajemennya.
Outline

Software Software
Configuration Configuration
Management Management
Concept Activities
Software Configuration
Management
What is Software Configuration?

1. The arrangement of a computer system or component as defined by the number,


nature, and interconnections of its constituent parts
2. In configuration management, the functional and physical characteristics of
hardware or software as set forth in technical documentation or achieved in a
product
3. The arrangement of a system or network as defined by the nature, number, and
chief characteristics of its functional units.
4. The requirements, design, and implementation that define a particular version of
a system or system component.
5. The manner in which the hardware and software of an information processing
system are organized and interconnected.

ISO/IEC/IEEE International Standard - Systems and software engineering --


Vocabulary
Why software configurations
need to be managed?
• There are multiple people working on software which is continually
updating
• It may be a case where multiple version, branches, authors are involved
in a software config project, and the team is geographically distributed
and works concurrently
• Changes in user requirement, policy, budget, schedule need to be
accommodated.
• Software should be able to run on various machines and Operating
Systems
• Helps to develop coordination among stakeholders
• SCM process is also beneficial to control the costs involved in making
changes to a system
What is Software Configuration
Management?

1. A discipline applying technical and administrative direction and


surveillance to: identify and document the functional and physical
characteristics of a configuration item, control changes to those
characteristics, record and report change processing and
implementation status, and verify compliance with specified
requirements
2. Technical and organizational activities comprising configuration
identification, control, status accounting, and auditing.

ISO/IEC/IEEE International Standard - Systems and software engineering -


- Vocabulary
Software Configuration
Management Activities
Software Configuration
Management Activities

Identification Storage

Change Status
Control Reporting
Software Configuration
Management Activities
Configuration Identification

The purpose of the identification activity area is to determine


the metadata for a configuration item—to uniquely identify it
and specify its relations to the outside world and other
configuration items.
Configuration Item
An aggregation of hardware, software, or both, that is designated for
configuration management and treated as a single entity in the configuration
management process

Configuration
Item

Physical Electronic

Hardware Document

Paperware Source code


Software Configuration Item

• Plans
• Specifications and design documentation
• Testing materials
• Software tools
• Source and executable code
• Code libraries
• Data and data dictionaries,
• Documentation for installation, maintenance, operation,
and software use
• Etc.
Configuration Storage

The purpose of storage is to ensure that a configuration


item will not disappear or be damaged, that it can be found
at any time and delivered in the condition in which you
expect to find it, and that a record is kept to indicate who
has been given the item or a copy of it. Storage takes place
in the libraries.
Library
• Where configuration items are stored.

Controlled
• Where items are kept while they are
being produced.
Dynamic • Not part of configuration management
system

• Where items are used.

Static • Items must under no circumstances be


changed.
Change Control

The purpose of change control is to be fully in control of all


change requests for a product and of all implemented
changes. For any configuration item, it must be possible to
identify changes in it relative to its predecessor. Any change
should be traceable to the item where the change was
implemented.
Change Control Phases
Phase Description
Creation of the event The event registration is created, and the event is described.
registration.
Analysis of the event Configuration item(s) affected by possible changes are
registration. determined, and the extensiveness of these changes is
estimated.
Rejection or acceptance of If the event registration is accepted, a change request is created
the event registration. for each configuration item affected.
The change request A new configuration item is identified and created, and the
initiates a new change is implemented. In the course of accepting the new item
configuration item. and placing it in storage, feedback is given to the configuration
control board.
Closing of the change The change request can be closed when the change has been
request. implemented and accepted.
Closing of the event The event registration can be closed when all corresponding
registration. change requests are closed.
Status Reporting

Status reporting makes available, in a useful and readable


way, the information necessary to effectively manage a
product's development and maintenance. Other activity
areas in configuration management deliver the data
foundation for status reporting, in the form of metadata and
change control data. Status reporting entails extraction,
arrangement, and formation of these data according to
demand.
Lifecycle of a Configuration Item
Baseline and Version Control
What is Baseline and Version Control?
Baseline
Formally approved version of a configuration item, regardless of media,
formally designated and fixed at a specific time during the
configuration item's life cycle.

Version control
Establishment and maintenance of baselines and the identification and
control of changes to baselines that make it possible to return to the
previous baseline

https://www.microtool.de/en/knowledge-base/what-is-a-baseline/
Baseline example
Version control

https://www.perforce.com/blog/vcs/what-is-version-control
Thank you

Question & Answer session


References

• Anne Mette Jonassen Hass – Configuration Management Principles


and Practice, Addison-Wesley (2003)
• SWEBOK v.3
• ISO/IEC/IEEE International Standard 24765-2010 - Systems and
software engineering – Vocabulary
• https://www.guru99.com/software-configuration-management-
tutorial.html

You might also like