MN692 Capstone Project Report Page 4 of
MN692 Capstone Project
Group Project Title
Client Contact Name:
School of IT and Engineering
Trimester x 201x
Signature of Students:
Sign your signature here
Date of Submission of Report: Put a date here clearly
Table of Contents Acknowledgement 2 Abstract 4 Glossary and Abbreviations 4 1. Introduction 5 2. Project Detailed Design 5 2.1 Summary of Literature Review 5 2.2 Objectives of the Project 5 2.3 Detailed Design 5 3 Project Implementation and Evaluation 5 3.1 Implementations 5 3.2 Testing 5 3.3 Results of the Project 6 3.4 Discussions/Analysis 6 4 Conclusions 6 References 6 5 Appendices 6 Appendix I: Client details form with client signature 6 Appendix II: Client and supervisor log book 6 Appendix III: Source Codes/ any other information 6
The abstract should not be more than 250 words. Describe your project, focusing on research questions and research methodology for next stage of the project.
The introduction should describe what the project is about and what the reader should know about your project before reading the rest of the report. The introduction section should also tell the reader what to expect in the report. It should say what each section of the report will contain. For example you may say something like:
In section 1 preliminary review of the topic is undertaken. Section 2 contains the literature review and state of the art as it is today. Second 3 is the design while section 4 provides simulation and discussions. Section 5 is summary. Finally references are given in Section 6. These statements help a reader to zero in to sections of your report that might be of interest to him.
Write all your literature review summary in this section and have in-text references as well. If you have undertaken any prior literature review in MN691 on the same topic as in MN692, you may use the review here as well.
Since the aim of your literature review is to gain understanding of what other authors have done on this topic and for you to also gain and obtain new ideas that you could use in your project, you need to summarise the new ideas from your literature review.
This section should contain highlights from the literature review section, particularly points and ideas that you wish to use for your project
State the objectives of the project as agreed with your lecturer and team (if a team is involved)? You may add insights gained from section 2.1 here.
Weekly schedule, Gantt chart and design methodology in detail.
If your project requires simulations, describe how the simulations were done, which software was used, what the inputs to the simulations are and the results you got from the simulations. This section may contain tables, graphs etc.
Describe your implementation.
Every system that is implemented needs to be tested. It does not matter whether is a software project or hardware, or a whole system combining both hardware and software. In all cases test the system for performance and record your findings on how the system you just implemented has performed. Honesty is required at this stage. It is ethically required that you are honest if the system fails or performs optimally. It is not to be seen as a flaw or failure if your system does not perform as expected. Thomas Edison ran over 1000 failed experiments on his first light bulb before he got it right.
In this section show your major results.
Discuss your results, explaining them to those who will read your report. Be aware that you are the expert on this project and it is your responsibility to explain your results in details.
Draw your conclusions here.
Compile your reference list as used in the review and research sections. This section should not contain any reference to any article that you have not used. Use the IEEE Communications referencing format. Check the Library on this format. For examples
 B. Klaus and P. Horn, Robot Vision. Cambridge, MA: MIT Press, 1986.
 L. Stein, “Random patterns,” in Computers and You, J. S. Brake, Ed. New York: Wiley, 1994, pp. 55-70.
 R. E. Kalman, “New results in linear filtering and prediction theory,” J. Basic Eng., ser. D, vol. 83, pp. 95-108, Mar. 1961.
 L. Liu and H. Miao, “A specification based approach to testing polymorphic attributes,” in Formal Methods and Software Engineering: Proceedings of the 6th International Conference on Formal Engineering Methods, ICFEM 2004, Seattle, WA, USA, November 8-12, 2004
If you have appendices, then include them here, for example
Title of your project