Scribd
Upload
5 views3 pages

Unit V - SCM

Uploaded by

PARTHIBAN M
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
5 views3 pages

Unit V - SCM

Uploaded by

PARTHIBAN M
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/ 3

Overview of Software Configuration Management

Deliverables: Software development results include various objects like

source code, design documents, and manuals.

Lifecycle Management: Objects are modified by multiple developers

throughout the software's lifecycle.

State Changes: The state of each deliverable changes as development

progresses and bugs are fixed.

Configuration Definition: The configuration of software is the state of

all project deliverables at any given time, and SCM tracks and controls

this configuration.

SCM Process:

Software Configuration Management (SCM) involves tasks like identifying

objects, controlling versions, managing changes, auditing configurations,

and reporting status.

Identification: Objects are categorized as basic (individual components)

or aggregate (collections of components), each with unique characteristics.


Version Control: Manages different versions of software components,

allowing users to select and construct configurations based on specific

attributes.

Change Control: Evaluates change requests for technical merit and

impact, ensuring proper access and synchronization among developers.

Configuration Audit: Verifies that the software meets requirements and

maintains traceability between configuration items and modifications.

Status Reporting: Provides current configuration information to

developers, testers, and stakeholders through various documents like

guides and release notes.

Software Revision vs. Version

New Version: Created with significant changes in functionality, technology,

or hardware.

New Release: Issued for bug fixes or minor enhancements.

Multiple Versions: Initial deliveries may have several versions for

different platforms (e.g., Unix, Windows).

Error Correction: As users find errors, corrections and enhancements lead

to new releases.

Necessity of Software Configuration Management

Concurrent Access Issues: Manages access to deliverables, preventing

conflicts among developers.

Stable Development Environment: Ensures team members have a

consistent environment for progress.

System Accounting: Tracks changes, including who made them and when.
Handling Variants: Manages multiple versions of software, ensuring bugs

are fixed across all variants efficiently.

Configuration Management Activities

Configuration Identification: Decides which parts of the system require

tracking.

Configuration Control: Manages changes to controlled objects, ensuring

smooth transitions.

Configuration Management Tools: Tools help track the project's current

state and manage changes effectively (e.g., Source Code Control System

(SCCS) and Revision Control System (RCS) for Unix).

You might also like