what is configuration management...please explain... thanx

Answers were Sorted based on User's Feedback



what is configuration management...please explain... thanx..

Answer / rajendra prasad

Configuration Management:
Definition-1:
Software configuration management (SCM) is the task of
tracking and controlling changes in the software.

Definition-2:
"Set of activities designed to control change by
identifying the work products that are likely to change,
establishing relationships among them, defining mechanisms
for managing different versions of these work products,
controlling the changes imposed, and auditing and reporting
on the changes made."

In a generic way Management includes ADD,Update,Delete
Repleace operations.

software development process is a Team activity, All team
members will share the work to develop the software.

The development activity may take from months to years based
on complexity and size of the project.

To explain configuration management indeatail,eg:
A software product is under development, so some 25 people
are working for that project.

These 25 people may include developpers,Development leads,
Project managers,Test Leads,Test engineers..etc.

All people should have some common repository(Like library)
to keep the documents,Code available for remaining team.
Ofcourse based on their designnation different people will
have different access permisions(Read/Write).

This repository will consists different folders and sub
folders.
>$
Deveopment
-Project Plans
-Design Documents
-Code
QC
-Test Plan
-Test Case Documents
-Traceability Doc
-Test Results
-Test Results Build QC 1.0
-Test Results Build QC 1.1
-Test Results Build QC 1.2....etc
For testing people will have access permission to view the
Requirement document folder(Read Only),
Test Plan folder(Read,write permissions)
Test Case documents folder(Read,write permissions)
Test Results documents folder(Read,write permissions)

If three test engineers(A,B,C) are working on this project
all three people will have acccess to read and write
testcases.

'Test Engineer A' prepared Test Case document and kept in
configuration management system.
Keeping the Documents in configuration management system is
called as 'Checkin' of documents
These Test Case document will be available for remaining
test Engineers B,C.
If Test Engineer 'B' Want update the existing testcase or
add some new test cases the then 'B' check the document 'B'
check out the document and Makes changes to it and
Again 'Checkin''s the updated document.
When 'B' check in the document 'configuration management'
will ask to enter some information regarding the updation
details.

Remaining i will explain later
byee
Rajendra Prasad
rajendra_penumalli@yahoo.com



If Tester A modified the

Is This Answer Correct ?    6 Yes 0 No

what is configuration management...please explain... thanx..

Answer / glamorous

thanks rajendra i am expecting more sharing from uuuu than
this.....ur answers r very useful to all....

Is This Answer Correct ?    2 Yes 0 No

Post New Answer

More Manual Testing Interview Questions

Explain?V?model?

1 Answers   Covansys,


Did any one worked on banking domain? banking projects? can anyone pls share their experience with me?

5 Answers  


Metrics in QA

2 Answers   CSSI,


Can you please provide me the answers for google page, yahoo home page, elevator, traffic signals. Thanks, Rama

2 Answers  


How do we estimate the number of test cases?

3 Answers  






What are the critical defect can find in web based testing(Like if any interview asked what critical defect you found in web based testing)????

1 Answers  


Hello people...im planning to jump into Manual Testing field. How should i start. Please guide me.. Thank you

12 Answers  


what is cause effect graph & exp its types?

3 Answers  


What is Smoke testing,in smoke testing time u will prepare the test cases or not?

10 Answers   Sonata,


what is the meaning of the negative testing?

7 Answers  


what is agile testing

2 Answers  


We can check many things in one test case, then Is it necessary to write separate test case for checking each functionality? Example : For Login Window --> Test Case is---> 1) Enter valid user id & password --> For this expected result --> 1) User should login. My question --> while executing above valid test case, we can expect more than one result such as "Visibility of password should be as ****" So Should I have to write separate test case for "Visibility of Password" OR Not? Please guide me properly.

5 Answers  


Categories