meljun cortes jedi slides-7.9 software configuration management

7/29/2019 MELJUN CORTES JEDI Slides-7.9 Software Configuration Management

1/16

Software Engineering 1

Basic Software Project

Management

SoftwareConfiguration

ManagementTOPIC NINE


2/16


It is the management of change within the softwaredevelopment process.

It consists of:

Identifying change. Controlling the change.

Ensuring that change is being properly implemented.

Reporting change to others.

It has the responsibility to control change.

Software Configuration

Management


3/16


Software Configuration Items

or Units These are items in the software development that are

changed.

They can be computer programs, documents or data.


4/16



or Units Project Planning Phase

Software Project Plan

Requirements Engineering

System Specifications

Requirements Model

Analysis Model

Screen Prototypes


5/16



or Units Design Engineering

Database Design

Dialog and Screen Design

Report Design Forms Design

Software Architecture

Component Design

Deployment Design


6/16



or Units Implementation

Source Code Listing

Executable or Binary Code

Linked Modules Testing

Test Specifications

Test Cases


7/16



or Units Manuals

User Manuals

Technical Manuals

Installation and Procedures for Software Engineering Standards and Procedures for Software Engineering


8/16


Baseline

It is a specification or product that has been formallyreviewed and agreed upon to be the basis for furtherdevelopment.

It can only change through a formal change procedure.


9/16


Baseline Dynamics

SCI

SE Tasks

FormalTechnicalReview

SCISCI

Modified

Extracted withSCM Controls Must be

Reviewed

New Baseline


10/16


Five Tasks

Change Identification

Version Control

Change Control

Configuration Audit

Reporting


11/16



It is the task of identifying items that change throughout thesoftware development process.

It specifically identifies the software configuration items(SCIs) and uniquely gives it an identifier and name.


12/16


Version Control

It is the procedures and tools to manage the differentversion of configuration objects that are created during thesoftware development process.

A version is a collection of SCIs.


13/16


Change Control It consists of human procedures and automated tools to provide a

mechanism for the control of change.

It has the following subset of task:

A change request is submitted and evaluated to assess

technical merit, potential side effects, overall impact on otherSCIs.

A change report is created to identify the final decision on thestatus and priority of the change.

The Engineering Change Order (ECO) is created that

describes the change to be make, the constraints, and thecriteria for review and audit.

The SCIs is checked out for modification.

It is, then, checked in after the review and subject to versioncontrol.


14/16


Configuration Audit

It is the process of assessing a SCIs for characteristics thatare generally not considered during a formal technicalreview.

It answers the following questions:

Was the change specified in the ECO done? Are there anyadditional modification made?

Did the formal technical review assessed the technicalcorrectness of the work product?

Did the software engineering procedures been followed? Did the SCM procedures been followed?

Have all appropriate SCIs been updated?


15/16


Status Reporting

It is the process of informing people that are affected by thechange.

It answers the following questions:

What happened? Who did it?

When did it happen?

What else will be affected?


16/16


Summary

Software Configuration Management Software Configuration Items or Units

Baseline

SCM Tasks


Version Control

Change Control

Configuration Audit

Status Reporting

meljun cortes jedi slides-7.9 software configuration management

Documents