Evaluation
In your evaluation section, you compare your test results to your stated objectives. Below is an example from a proposal or progress report. The version for your final report should be much more detailed.
For the final report, remember to update the verb tense to match the final status, and be sure to honestly state if you were successful or not. If you don't accomplish all your stated objectives, you can simply mention in your final report's discussion section what you would do if you had more time or what you would recommend next year's FYP students do to improve upon your work.
2.4 Evaluation
For the evaluation phase, we will generate a 3D map to show the terrain and flooding simulation results. We will use different colors for different elevations and depths of water. Also, we will provide some time charts to show the total computation times and to illustrate the processing time improvement of our flooding algorithm. Since speed is essential, we will make sure we can obtain fairly accurate results within half an hour.
2.4 Evaluation
The Evaluation Phase will be carried out at every milestone of our project. We will use different aspects to measure and justify our success. There are basically 5 aspects we will use for evaluation:
- Reliability
- Accuracy
- Consistency with the stated objectives
- Comparison with other similar projects
- Feedbacks from classmates, professors and relatives
We will produce graphs, tables or other suitable illustrations to compare the actual results with our expected results. We will also use the data to analyze the overall performance and the effects of each smaller part on the whole.
2.4 Evaluation
We will analyze the system’s performance according to the following areas:
- Reliability - Evaluation criteria include the correctness of messages sent, successful error handling, smooth system failover, etc. (Failover is the capability to switch over automatically to a standby system upon failure or abnormal of the normal system.)
- Latency - The delay of different services and data communication between different components
- Scalability – The maximum number of users the system can handle and the capacity for system expansion
- User interface - Whether the interface design is user-friendly, i.e. simple and easy to use and understand
- Power consumption - The maximum operating/standby time and power recharging efficiency of the system
- Security - Security measures of physical and logical connections between
components