software configuration management

Software Configuration Management

By: Julia Carolina Daud5209100059

Frequently asked questions

1. What is the correct version of the software module that I have to continue it’s coding?

2. Who can provide me with an accurate copy of last year’s version 4.1 of the JCD software system?

3. What version of the software system is installed at JCD Industries?

2

So, Whats SCM Definition?

• Configuration Management tools are used to strore versions of system components, building systems from components. And monitor the release version of the system tot he customer along with the report

3

SCM Puposes

1. Identify Change2. Control Change3. Ensure the change is properly

implemented4. Report changes to all the people

who need to know

4

What Changes?

• Software Code• Source Code• Object Code

• Data • Test Cases and test scripts• Parameters, code, ...

• Documents• Test Report• Test plan

5

Factor affecting the proposed changed

• Expected contribution of the proposed change

• Urgency of the change• Effect of the proposed change on

project timetables, level of service,etc• Efforts require in making the change

operational• Required software quality assurance

efforts6

Baseline

Is a software configuration management concept that helps us to control chages without seriously distrubing changes that may be warranted, define baseline as:

“A specification or product that has been formally reviewed and agreed upon that there-after serves as the basis for further development, and that can be changed only through formal change control procedures”

IEEE Std 729 Standard Glossary of Software Engineering Terminology

7

Baseline Purposes

• Creation of a baseline is usually a milestone in the schelude

• Everyone uses the same current baselines

• To change the baseline requires a formal process

8

Audits

• Software configuration audit complements the formal technical review to assess the configuration of an object to the characteristics that are generally not considered during the review

9

The Format of CM Plan1. Introduction

a) purpose b) scope c) definitions and acronyms d) references2. Management

a) organizationb) SCM responsibilitiesc) interface controld) SCMP implementatione) policies, directives, procedures (naming conventions, version designations, problem report process)

3. SCM Activitiesa) configuration identificationb) configuration control (change history, review authority, read/write

control, member identification)c) configuration status accounting (status of requests, status of

approved changes, …)d) audits and reviews

10

The Format of CM Plan (cont’d)

4. Tools, Techniques, and Methodologies

5. Supplier Control6. Records Collection and Retention

• According to IEEE Standard 828-standard for• Software Configuration Management Plans

11