• Software change is unavoidable process

  • Software change occurs because of following reasons.

  1. New requirements emerge when the software is used.

  2. The buisness environment changes.

  3. Errors needs to be repaired.

  4. New equipment must be accommodated.

  5. The performance or reliability may have to be improved.

  • A key problem for organisations is implementing and managing change to their legacy systems.

  • Organisations have huge investments in their software systems- they are crucial buisness assets. To maintain the value of these buisness assets these software systems must be changed and updated at appropriate time.

  • The software change strategies that could be applied separately or together are as given below.

  1. Software maintenance: The changes are made on the software due to requirements.

  2. Architectural transforms: It is the process of changing one architecture into another form.

  3. Software re-engineering: New features can be added to existing system and then the system is reconstructed for better use of it in future.

  • Evolution Processes

  • The software evolution process is dependent upon the type of software being maintained.

  1. In the maintenance process initially the request for change is made.

  2. Change management In this phase the status of all the change requests is identified

  3. Impact analysis following activities are performed in this phase:

  • Identify all systems and system products affected by a change request.

  • Make an estimate of the resources needed to affected by a change request.

  • Analyze the benefits of the change.

4.system release -planning in this phase the schedule and contents of software release is planned. The changes can be made to all types of software maintenance.

5. Change implementation -The implementation of changes can be done by first designing the changes, then coding for these changes and finally testing the changes. Preferably the regression testing must be performed while testing the changes.

6. System release During the software release

  1. Documentations

  2. Software

  3. Training

  4. Hardware changes

  5. Data conversion should be described.

  • Software Maintenance

  1. Software maintenance is an activity in which program is modified after it has been put into use.

  2. software maintenance usually it is not preffered to apply major software changes to system 's architecture.

  3. Maintenance is a process in which changes are implemented by either modifying the existing system's architecture or by adding components to the system.

  • Need for maintenance

  • Maintenance is applicable to software developed using any software life cycle model. The system changes and hence maintenance must be performed in order to:

  1. Correct faults

  2. Improve the design

  3. Implement enhancement

  4. Interface with other systems.

  5. Adoption of environment

  6. Migrate legacy software

  7. Replacement of old software by new software.

  • In software maintenance report four keys should be mentioned

  1. Maintaining control over the software's day to day functions.

  2. Maintaining control over software modification.

  3. Repairing of functions.

  4. Performance degradation should be avoided.