Downloads & Free Reading Options - Results

Configuration management is defined to be management of change. It has two complementary aspects, provision of information about a changing product and controlling changes to the product. Change needs to be controlled and recorded without excessive interference in the development process. A software product changes whenever any component (compiled unit and the source text from which the compiled unit derived) is changed, or the way in which the components are assembled is changed or any associated item (e.g. requirements, designs, user documents or build files) is changed. A component may be part of more than one product. This paper discusses a basis for a flexible approach to software configuration management. It sets out the aims of software configuration management and outlines the traditional method of achieving these aims. It goes on to describe the underlying features that provide a basis for configuration management in the Flex programming support environment. It describes the practical application of these features in easing some of the traditional problems of configuration management. Configuration management across a set of machines is considered as well as configuration management on a single machine.