|



 
á  

á|
|  
What Is SCM PLANS..?
(Software Configuration management)
‡ Changes occur at any time during
software development but these changes
to be done in controlled manner.

‡ SCM is the discipline for systematically

controling the changes that occur during
development.
Cont«

‡ Development process can handel µnormal¶

changeas such as during in code while
programmer is developing it.
‡ If coding is being done then changes
cannot properly handel
‡ This types of changes are handle by SCM
activity.
‡ SCM is control the changes, minimal
efffect cost ,shedule and quality of
products
 Components of SCM
1. Software Configuration identification

2. Change control

3. Status Accounting and auditing

1. Software Configuration identification
‡ Whenever any changes have to be done,
it should be clear to what the changes has
been applied.
‡ A baseline is arrengement of set of SCIs
(Software Configuration items).
‡ An SCI is a document that is a basic unit
of modification.
EX. Of SCIs are requerment document,
code of a module,test plane etc.
2.Change Control

‡ After configuration identification of

changed item, The change control
procedure can be applied.
‡ The changes are generaly taken by the
CCB (configuration control board).
‡ Which is group of people for Configuration
Management.
‡ Headed by CM (Configuration Manager)
3. Status Accounting and auditing
‡ What is the status of a change request(cr):
approved or not
‡ What is the status of an approved of CR
‡ What is frequency of CR
‡ What is the average time and effort for
fixing a CR and so on.
‡ The main aim of auditing is SCM goals are
met or not.
Wh

|
|   

‡ To ensure that the final product is of heigh

quality.
‡ Some quality control activities that must be
performed throughout the development of
software.
‡ If quality control is not there, correting the
errors in the final stages can be very
expensive.
 


‡ SQAP (software Quality Assurance Plan)

is specify all the work product.

‡ That need to be performed for checking

the quality of each product and the tools
and the methods use for SQAP activies.
Techniques for quality assurance plan
1. Verification & validation (V&V)
‡ Verification is the process of determining, the
product of a given phase of software
development fulfill the specification established
during the previous phases.

‡ Validation is the process evaluating at the end

of the software development validity with the
software requirement.
2. Inspection & Review

‡ It is technique in which software

requirement, design, code are examined in
detail by a person of group and it is delete
the faults and other problem.

mReason for having Inspection & Review

‡ Fault removal
‡ Productivity increase
‡ Provide information for project monitoring
 |