Chapter 9 software configuration management
Download
1 / 10

Chapter 9 Software Configuration Management - PowerPoint PPT Presentation


  • 93 Views
  • Uploaded on

Chapter 9 Software Configuration Management. The “First Law”. No matter where you are in the system life cycle, the system will change, and the desire to change it will persist throughout the life cycle. Bersoff, et al, 1980. What Are These Changes?. changes in. business requirements.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Chapter 9 Software Configuration Management' - mikkel


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Chapter 9 software configuration management
Chapter 9Software Configuration Management


The first law
The “First Law”

No matter where you are in the system life cycle, the system will change, and the desire to change it will persist throughout the life cycle.

Bersoff, et al, 1980


What are these changes
What Are These Changes?

changes in

business requirements

changes in

technical requirements

changes in

other

documents

user requirements

software models

Project

Plan

data

Test

code


The software configuration
The Software Configuration

programs

documents

The pieces

data


Change scm
Change & SCM

Software Engineering

SCM

• identification

tools

• version control

methods

• change control

procedures

• auditing

a TQM foundation

• reporting

• construction


Change control process i
Change Control Process—I

need for change is recognized

change request from user

developer evaluates

change report is generated

change control authority decides

request is queued for action

change request is denied

user is informed

change control process—II


Change control process ii
Change Control Process-II

assign people to SCIs

check-out SCIs

make the change

review/audit the change

establish a “baseline” for testing

change control process—III


Change control process iii
Change Control Process-III

perform SQA and testing activities

check-in the changed SCIs

promote SCI for inclusion in next release

rebuild appropriate version

review/audit the change

include all changes in release


Auditing
Auditing

Change

Requests

SQA

Plan

SCIs

SCM Audit


Status accounting
Status Accounting

Change

Reports

Change

Requests

ECOs

SCIs

Status Accounting

Reporting


ad