rajesh

• Nov 13th, 2006

 

the configuration management comes in the maintenance phase of the life cycle. once the s/w is released 2 the customer and client stats using it,the maintenance phase is entered.when the client reports errors or a defect r when client asks 4 modification in the software ,the changes to the source code and also the related documents such as srs,design doc have to be done systematically.the work products (Srs,design doc,source code etc) hav to be kept under configuration control. if u have relesased version1 ,if there are any modifications done 4 it again a version 1.1 wil b released in the same way version 1.2 and 1.3 and 2 is the finally modified version. unless a systematic procedure is follwed to handle multiple versions, the work products wil be unmanagable. EACH VERSION OF THE S/W WORK PRODUCTS HAS T0 BE MAINTAINED WITH THE REQUIRED DOCUMENTATION. MAKING CHANGES TO THE WORK PRODUCTS SYSTEMATICALLY IS CALLED CONFIGURATION MANAGEMNT.rajesh

G.D.S.Prasad

 Profile Answers by G.D.S.Prasad Questions by G.D.S.Prasad

• Mar 8th, 2009

 

Configuration Management or CM is the management and control of the technical
resources required to construct a software artifact.

We require CM for
1. To ensure Integrity of requirements
2. We have Conformance to requirements
3. We are using the right version of any work product at any point in time
4. All components of the delivered software are consistent with each other
5. Right versions of software components are shipped to customer site