QA Testing - Difference between Configuration Management and Version Control.

GeekInterview.com > Interview Questions > Testing > QA Testing

Go To First | Previous Question | Next Question

QA Testing | Question 48 of 176

Difference between Configuration Management and Version Control.

Total Answers and Comments: 3

Last Update: May 28, 2009 Asked by: upendra

Sponsored Links

Best Rated Answer

—

Submitted by: Sreekanth Reddy Lingala

Version Control is part of Configuration Management.

Read the following, you will understand.

Configuration Management is the approach used in managing the individual components (software & hardware) that make up the ‘System’. It is important not to confuse ‘Configuration Management’ with ‘Change Management’.

Change management is concerned with changes made to an item/s. Whereas Configuration Management is concerned with managing all of the individual items, and all of the items as a whole (System).

Software exists in two forms; non-executable (source code) and executable code (object code). When errors are found in the software, changes may be required to be made to the source code. When this situation occurs, it is imperative to be able to identify which version of code to change. There may also arise a situation where two Developers need to make changes to the code. If the Developers are unaware of the other updating the version, then both updated versions could be saved causing lost changes or worse. Also, Testers may not be aware of which version of code to test with causing further problems.

When testing is complete, a Test Leader will need to demonstrate that the testing has been completed on a specific version of code, a necessity to ensure correct test coverage.

It is not only software and hardware components that need to be controlled, but also documentation, as project members will need to ensure they work from the correct versions.

Configuration Management consists of the following four parts:

Configuration Identification
Configuration Control
Status Accounting
Configuration Auditing

Configuration Identification

This is the process of identifying all of the individual items that will be subject to version control within the project. Details such as version and status may be recorded.

Configuration Control

This activity ensures that any changes are controlled and monitored. A master copy should be kept in order for people to be able to check out the latest version of the document to avoid two people working on the same document version. Items such as ‘dates’, ‘version numbers’ and ‘updated by’ are details that may be recorded. Once the item has been updated, the item can be checked back in, resulting in it becoming the master copy. A history will be displayed when multiple versions exist.

Status Accounting

This is the process of recording and reporting on the current status of the item. It is in effect the ability to be able to view the current state of the item.

Configuration Auditing

Configuration Auditing is used to ensure that the control process that is used is being correctly adhered to

Above answer was rated as good by the following members:
jimmy_vaswani

May 15, 2006 14:54:11

add2vishu

Member Since: May 2006 Contribution: 4

RE: Difference between Configuration Management and Ve...

Cofiguration Management : is changing the H/W according to the customer requirements without making any changes to the application

Version Control: Is making changes in the application w.r.t to the customers requirements.

Is this answer useful? Yes | No

June 20, 2006 05:55:35

Sreekanth Reddy Lingala

RE: Difference between Configuration Management and Ve...

Version Control is part of Configuration Management.

Read the following you will understand.

Configuration Management is the approach used in managing the individual components (software & hardware) that make up the System . It is important not to confuse Configuration Management with Change Management .

Change management is concerned with changes made to an item/s. Whereas Configuration Management is concerned with managing all of the individual items and all of the items as a whole (System).

Software exists in two forms; non-executable (source code) and executable code (object code). When errors are found in the software changes may be required to be made to the source code. When this situation occurs it is imperative to be able to identify which version of code to change. There may also arise a situation where two Developers need to make changes to the code. If the Developers are unaware of the other updating the version then both updated versions could be saved causing lost changes or worse. Also Testers may not be aware of which version of code to test with causing further problems.

When testing is complete a Test Leader will need to demonstrate that the testing has been completed on a specific version of code a necessity to ensure correct test coverage.

It is not only software and hardware components that need to be controlled but also documentation as project members will need to ensure they work from the correct versions.

Configuration Management consists of the following four parts:

Configuration Identification
Configuration Control
Status Accounting
Configuration Auditing

Configuration Identification

This is the process of identifying all of the individual items that will be subject to version control within the project. Details such as version and status may be recorded.

Configuration Control

This activity ensures that any changes are controlled and monitored. A master copy should be kept in order for people to be able to check out the latest version of the document to avoid two people working on the same document version. Items such as dates version numbers and updated by are details that may be recorded. Once the item has been updated the item can be checked back in resulting in it becoming the master copy. A history will be displayed when multiple versions exist.

Status Accounting

This is the process of recording and reporting on the current status of the item. It is in effect the ability to be able to view the current state of the item.

Configuration Auditing

Configuration Auditing is used to ensure that the control process that is used is being correctly adhered to

Is this answer useful? Yes | No

1 0

Overall Rating: +1

May 28, 2009 06:43:59

SUSHALL

Member Since: May 2009 Contribution: 10

RE: Difference between Configuration Management and Version Control.

Hi Sreekanth

I could not exactly get what you are trying to say. May be am not used to most of the technical words you have used. I request you to clarify me in a simple way for my questions.

1. We say 'Star Team' (where we manage the stages of CR) the is one of the 'Configuration Management' tools. So please let me know how can i relate it to your definition.

2. Also what is meant by version control and how is it a part of CM?

Thanks
Suhasini.R

Is this answer useful? Yes | No

0 1

Overall Rating: -1

Go To Top

User Name		Remember Me?
Password

Question Bank