Maintenance and Evaluation (Maintenance Categories (Corrective (Fixing…
Maintenance and Evaluation
maintenance is seen as an additional stage that starts when implementation stage is done
Maintenance will involve repeating the entire lifecycle, on a much smaller scale
Testing during Maintenance
Checking changes do not cause issues with previously working code
'Simple' fixes can have a ripple effect
Changes to variable format/size
Changes to parameter format/ size
Incremental, Spiral, Iterative and Agile
Maintenance is inherent in the approach as each release will 'maintain' earlier releases.
Fixing software faults / failures
Fixing requirements that were incorrectly defined and implemented
Implementing new or changed requirements into the software product
Could be due to organisational or legislative changes
Making improvements to the software product quality
Non-functional requirements such as performance or usability
Why is evaluation being carried out?
Who, should be involved and why?
What is being evaluated?
The project, system, benefits or a combination?
What is the timeframe?
How and what is done?
To review how well the development project went
Post-Project Review Report
Risks and issues
To review how well the software product meets the requirements
To identify any problem areas or unresolved issues
Post-Implementation Review Report
The system itself - Hardware, software
Training, user guides
To determine whether the business benefits for the project have been realised
A report or document that outlines the benefits delivered by the project
Focus all areas that have an influence on the benefits of the project