Software Maintenance And Change Control Process

Software Maintenance and Change Management Process Software Maintenance and Change Management Process Introduction The software maintenance process is a topic that most organizations may pose and is an important issue that needs to be addressed. When software is created, changes and errors often lead to maintenance. It is important to have a process to help you define how these projects are handled and how to complete them. Recording these changes using various tools, requests, or errors is important in order to keep the organization organized and to properly track these items.

Software maintenance can be defined as four separate activities. These activities include corrective maintenance, adaptive maintenance, comprehensive maintenance and preventive maintenance. Fixed maintenance can be explained as including the process of diagnosing and correcting errors. Adaptive maintenance, whether hardware or software, is an activity that changes software to properly connect to changing circumstances. Complete maintenance is responsible for adding new features, changing existing features, and performing periodic enhancements. This accounts for the majority of all the efforts for software maintenance. Preventive maintenance changes software, improves future maintainability and reliability, and provides a better foundation for future enhancements. This activity is rarely used. A new version will normally be released before preventive maintenance is done. All of these activities must be included in the maintenance plan.

Maintenance of existing software may account for more than 60% of all development work. Changes are inevitable, and mechanisms must be developed to evaluate, manage and correct. Software maintenance is a series of software engineering activities performed after software is distributed to customers and operated. 70% of the software cost is used for maintenance. Maintenance work can be divided into two types: correction and debugging. More than two-fifths of the maintenance work is the extension and change requested by the user. The cost of urgent bug fixes will be higher than normal plan modifications. They are executed under pressure, damaging the orderly process of releasing new versions, and often introducing new bugs.