what is configuration management...please explain... thanx
Answers were Sorted based on User's Feedback
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 |
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 |
What are the interview question on insurance domain in manual testing
who will assign the seviourity & priority for a BUG in a project ? tester or any other.......... ????
could u pls anyone tel me .."which is the best instute that provides eficient practical knowledge and also real-time oriented knowldge to do a project in manual and automation testing..in hyd" pls send me to dis mail-id if u find any..? sinducute17@gmail.com
1) Can you tell me the High severity and low priority bug,High priority and low severity bug?
is functional and black box testing same or not
what is data guidelines
can any one tell me the exact testing process of stand alone application, what type of testing i can perform on stand alone application and how can i track the bugs(from starting to ending), and online demo for logistics software if any one knows please send me the link.
Can you do system testing at any stage of sdlc?
what is defect leakage?
Write test cases on Travel bag?
who is perform user acceptance testing and when it will conduct? is it before alpha testing or after alpha testing? Please post the answer as soon as possible
Can test condition,testcase and testscript help u in performing the static testing