Software is evolutionary in nature. From the time a software product is defined until it is no
longer used, it changes. Each change results in a different version of the product. Initiating, evaluating, and implementing the changes while maintaining product integrity is the purpose of configuration management.
Software configuration management is a set of activities that have been developed to manage change throughout the life cycle of computer software. SCM can be viewed as a software quality assurance activity that is applied throughout the software process.
It is important to make a clear distinction between software support and software configuration management. Support is a set of software engineering activities that occur after software has been delivered to the customer and put into operation. Software configuration management is a set of tracking and control activities that begin when a software engineering project begins and terminate only when the software is taken out of operation.
As the software process progresses, the number of software configuration items (SCIs) grows rapidly A System Specification spawns a Software Project Plan and Software Requirements Specification (as well as hardware related documents). These in turn spawn other documents to create a hierarchy of information. If these SCIs are not well managed little confusion will result. Unfortunately, another variable enters the process—change. Change may occur at any time, for any reason.
Changes to one configuration item usually require changes in others. For instance, a requirements change means specification, design, code, and testing changes. Configuration management helps maintain the integrity of specific items in an atmosphere of change.Configuration control boards, established under a configuration management plan, evaluate proposed changes and discrepancy reports, authorize or do not authorize change, and track the implementation of the decision either way.
longer used, it changes. Each change results in a different version of the product. Initiating, evaluating, and implementing the changes while maintaining product integrity is the purpose of configuration management.
Software configuration management is a set of activities that have been developed to manage change throughout the life cycle of computer software. SCM can be viewed as a software quality assurance activity that is applied throughout the software process.
It is important to make a clear distinction between software support and software configuration management. Support is a set of software engineering activities that occur after software has been delivered to the customer and put into operation. Software configuration management is a set of tracking and control activities that begin when a software engineering project begins and terminate only when the software is taken out of operation.
As the software process progresses, the number of software configuration items (SCIs) grows rapidly A System Specification spawns a Software Project Plan and Software Requirements Specification (as well as hardware related documents). These in turn spawn other documents to create a hierarchy of information. If these SCIs are not well managed little confusion will result. Unfortunately, another variable enters the process—change. Change may occur at any time, for any reason.
Changes to one configuration item usually require changes in others. For instance, a requirements change means specification, design, code, and testing changes. Configuration management helps maintain the integrity of specific items in an atmosphere of change.Configuration control boards, established under a configuration management plan, evaluate proposed changes and discrepancy reports, authorize or do not authorize change, and track the implementation of the decision either way.
0 Komentar untuk "PRODUCT CREATION AND CREATIVITY"