1. The implementation processes contains software preparation and transition activities, such as the conception and creation of the maintenance plan, the preparation for handling problems identified during development, and the follow-up on product configuration management.

2. The problem and modification analysis process, which is executed once the application has become the responsibility of the maintenance group. The maintenance programmer must analyze each request, confirm it (by reproducing the situation) and check its validity, investigate it and propose a solution, document the request and the solution proposal, and, finally, obtain all the required authorizations to apply the modifications.

3. The process considering the implementation of the modification itself.

4. The process acceptance of the modification, by checking it with the individual who submitted the request in order to make sure the modification provided a solution.

5. The migration process (platform migration, for example) is exceptional, and is not part of daily maintenance tasks. If the software must be ported to another platform without any change in functionality, this process will be used and a maintenance project team is likely to be assigned to this task.

6. Finally, the last maintenance process, also an event which does not occur on a daily basis, is the retirement of a piece of software.

validity, to preserve from failure or decline.

e.g. Car maintenance

Software maintenance : modification of a software product

after delivery in order to

- improve performance,

- correct faults,

- adapt the product to a modified environment

In most of the cases, for atomic-scale software,

we restart from existing software to add new functionalities.

Maintenance is essential. Waterfall model is inadequate.