Configuration Management (CM) comprises, identification & management of configurable items. Its a vast subject which involves baselining, change control, version control etc.
U will find ample of info on that if u search on google.
I am totally confused about this. Actually I will give u the information what i have learnt all these days.
3. Purchase Order from Client
4. Project Requirement Document
5. System Design Document
6. Functional Specifications
7. Database Design Document
8. Kindly clarfiy whether we have to create User Acceptance Test after the Unit test case / Integration / Regression Test preparation internally by a tester.
9. If any changes required we have to follow the Change Management
10. Project Closure Document.
I have a very clear confusion in CM and Testing and Metrics and roles and responsibilities assigining to Project Managers / Project Leaders / Developers and Testers.
I hope you read all the theory already - I will try to describe some practical considerations: If your goal is ISO certification, then whole idea or CM is to describe how all the items you mentioned are changed. And you have to add product itself to the list – source code and executables. Any item is placed under CM only at some moment, for example when it is completed (while it is at draft status any changes are allowed without CM). Again if your goal is ISO, I suggest to DEFINE that moment as late as possible, for example “Database Design Document“ is placed into CM only when user acceptance tests starts or even after finishes.
Regarding testing – your test documents are also items for CM. Not sure about Metrics – I don’t remember that ISO requires them.
Software Configuration Management is a set of engineering procedures for tracking and documenting software throughout its life cycle to ensure that all changes are recorded and that the current state of the software is known and reproducible
It consists of 4 components ...
1. Configuration Identification
2. Configuration Control
3. Configuration Status Accounting
4. Configuration Audits
Configuration Identification is the process of identifying the configuration items (CI’s) and their components that makes a complete application
Configuration control can be identified by Change Management(ie defect tracking) and Configuration Management
Configuration Status Accounting is the process of identifying the status of any change during the development of an application
Configuration Audits is the process of auditing any released application to internal or external customers
You need to have a process in place to handle all of the above, to comple with ISO/CMM/CMMi