Final Evaluation Report Template
Use this page to structure the written evaluation completed in Unit 4 after development, testing and evidence collection.
How to use this template
The evaluation should assume the software solution is implemented with the client, even if full real-world implementation is not practical.
Cover Information
| Field | Student entry |
|---|---|
| Project title | |
| Student name | |
| Date | |
| Version |
1. Evaluation Overview
Write a short paragraph that explains:
- what has been developed
- what this evaluation report is assessing
- which evidence has been collected to support the evaluation
2. Evaluation Strategy
Explain how the software solution will be evaluated.
2.1 Evaluation criteria being used
State that these are the criteria developed in Unit 3 Outcome 2 and carried into Unit 4.
2.2 Evidence to be collected
List the evidence used to evaluate the software, such as:
- testing tables
- beta-testing feedback
- observations of users
- screenshots
- annotated drafts
- progress notes
2.3 Methods used to collect the evidence
- observation
- survey
- interview
- testing record
- annotated screenshots
3. Evaluation of the Software Solution
Use a table so each criterion is clearly judged.
| Criterion question | Evidence used | Evaluation result | Overall judgement |
|---|---|---|---|
| Met / Partly met / Not met | |||
After the table, write a short summary paragraph that explains the overall effectiveness and efficiency of the software solution.
4. Testing Summary
Summarise the main results from testing.
4.1 Alpha testing
- what was tested:
- major issues found:
- major fixes made:
4.2 Beta testing
- who tested the software:
- what feedback was collected:
- what issues or improvements were identified:
5. Evidence of Efficiency and Effectiveness
5.1 Efficiency
Comment on items such as:
- speed of processing
- time taken to complete tasks
- effort required by the user
- cost of data or file handling if relevant
5.2 Effectiveness
Comment on items such as:
- accessibility
- accuracy
- attractiveness
- clarity
- completeness
- maintainability
- readability
- relevance
- timeliness
- usability
6. Evaluation of the Project Plan
Assess how effective the project plan was in managing the project.
Address:
- whether the original timeline was realistic
- where the project stayed on schedule
- where delays or changes occurred
- how the Gantt chart was updated or annotated
- whether the project plan helped manage the work successfully
Student writing prompt
Use actual evidence here. Refer to changed dates, moved tasks, annotated milestones or adjustments to the development plan.
7. Recommendations for Improvement
List realistic improvements that could be made if the project continued.
These might relate to:
- appearance
- behaviour
- features
- performance
- usability
- maintainability
- privacy or security
8. Final Conclusion
Write a short concluding paragraph that states:
- how successful the software solution was overall
- how well it met the criteria
- how effective the project plan was
- what the most important future improvements would be
Final Check Before Submission
- [ ] The report evaluates the criteria developed in Unit 3.
- [ ] Evidence is named clearly.
- [ ] Efficiency and effectiveness are both addressed.
- [ ] Project plan effectiveness is evaluated.
- [ ] Recommendations are realistic and specific.
- [ ] The conclusion is clear and supported by evidence.