Conclusions
In your Final Report you need a Conclusions section. In this section you bring together the salient points (要點) of your project. In addition, areas for future research and analysis should be addressed. Try to focus on the following:
- The major accomplishments of your project and its key features
- Problems not addressed in your paper
- Questions that were not answered in your paper
The Conclusion doesn't need to be long - about half a page to a page.
For more information see Writing a Research Paper.
Recommendations
Although many business and engineering reports commonly have a separate Recommendations/Suggestions section, your Final Report does not need one. Just include your recommendations in your Conclusions. To learn more about writing your recommendations, see Writing a Report: Recommendations.
Example of Conclusions from a 2008-2009 FYP final report
In our project, we designed and implemented a low-cost and user-friendly telemedicine system with an Ebox 4300 device. The target users of the system are people living in remote communities in developing countries who cannot afford the time and the money to visit a doctor in the city.
There is still much room for future development that would enhance the system and increase its business value. The following items are some suggestions:
- Video and audio support for playback of health education content
Currently, this functionality only supports slideshows with plain images. This limits the audience to those who are literate and can understand the text on the screen. Support for video and audio content would expand the audience base and make the content more attractive.
- Programmatic printing of prescriptions
Patients' user experience can be greatly enhanced if the Ebox telemedicine software can automatically print prescriptions for them. This way, patients or their assistants do not have to copy them down manually.
- Synchronous streaming of video and audio
Video and audio are streamed separately in the current system, giving rise to potential video/audio synchronization problems. Some commercial applications use the Real-time Transmission Protocol (RTP) to resolve these problems. However, video streaming with RTP is not supported in Windows CE, so other solutions are needed to tackle this issue.
We have learned much through the project. We were challenged by the complexity of the technologies needed to build the system. None of us had experience with embedded development, video / audio capturing and streaming before the project. We needed to learn different concepts and techniques quickly and apply them in the system. The project also provided a chance for us to accumulate experience in .NET development and multi-threaded applications. This project experience has greatly enriched our knowledge and sharpened our technical skills.
In addition, we had to conduct substantial research on the United Nations’ Millennium Development Goals when we were brainstorming for a suitable topic for the Microsoft Image Cup 2009. We learnt more about the problems that developing countries are facing as their populations continue to grow. Our social awareness has increased, and we have become more concerned for global issues.
We sincerely hope that we can advance to the final round of the competition and share our ideas with teams from all around the world.