The processes involved in software configuration management

Configuration management is a topic that often confuses new practitioners. So, let

me describe it briefly:

· Configuration management determines clearly about the items that make up

the software or system. These items include source code, test scripts,

party software, hardware, data and both development and test

documentation.

· Configuration management is also about making sure that these items are

managed carefully, thoroughly and attentively during the entire project and

product life cycle.

· Configuration management has a number of important implications for testing.

Like configuration management allows the testers to manage their testware

and test results using the same configuration management mechanisms.

· Configuration management also supports the build process, which is

important for delivery of a test release into the test environment. Simply

sending Zip archives by e-mail will not be sufficient, because there are too

many opportunities for such archives to become polluted with undesirable

contents or to harbor left-over previous versions of items. Especially in later

phases of testing, it is critical to have a solid, reliable way of delivering test

items that work and are the proper version.