in a standardized comment prologue kept at the beginning of thecomponent. This should reference the change request associated withthe software change. The change management process is very procedural. Each personinvolved in the process is responsible for some activity. They completethis activity then pass on the forms and associated configuration items tosomeone else. The procedural nature of this process means that achange process model can be designed and integrated with a versionmanagement system. This model may then be interpreted so that theright documents are passed to the right people at the right time.
B)Version and Release Management
Version and release management are the processes of identifying andkeeping track of different versions and releases of a system. Versionmanagers must devise procedures to ensure that different versions of asystem may be retrieved when required and are not accidentallychanged. They may also work with customer liaison staff to plan whennew releases of a system should be distributed.A system version
is an instance of a system that differs, in some way,from other instances. New versions of the system may have differentfunctionality, performance or may repair system faults. Some versionsmay be functionally equivalent but designed for different hardware orsoftware configurations. If there are only small differences betweenversions, one of these is sometimes called a variant of the other.A system release is a version that is distributed to customers. Eachsystem release should either include new functionality or should beintended for a different hardware platform. Normally, there are moreversions of a system than releases. Some versions may never bereleased to customers.For example, versions may be created within an organization for internaldevelopment or for testing.A release is not just an executable program or set of programs. It usuallyincludes:(1) Configuration files defining how the release should be configured forparticular installations.(2) Data files which are needed for successful system operation.(3) An installation program which is used to help install the system ontarget hardware.(4) Electronic and paper documentation describing the system.