Once the system has been handed over, the system developers may be called in to do some maintenance

Three different approaches:

1. Corrective maintenance

<aside> 🛠 The system devs are called to the organisation to fix any identified problems.

</aside>

Examples:

• Bugs in the system (i.e. an incorrect calculation)
• Logical errors (i.e. wrong postcode)
• Load errors (i.e. too intensive for the hardware being used)

<aside> 💲 The most expensive for developers as it deals with issues that should have been dealt with during testing.

</aside>

2. Adaptive maintenance

<aside> 💰 This is required when the system must be altered to adapt to a new law or environment - allows devs to make some extra money.

</aside>

• Always as a result of an external change
• Additional cost as they weren't in the original brief
• Fixes bugs and adds extra functionality

Examples:

• Changes in legislation/law (e.g. VAT increase)
• Merge with another company
• A new OS has been introduced (i.e. it is also required to run on a mobile phone thus the system must be altered)