1 Written Reports
The progress reports and final reports must be written in the format of an IEEE technical paper. Students must use the following MS Word document, IEEE Template, as a template for the report. The same fonts, style for heading, and margins must be used. Progress reports must contain the information in the subsections below and should have a maximum of 5 pages excluding appendices. The final report is similar to the progress report, however it should have a maximum of 10 pages, excluding appendices:
1.1 Cover Page (optional)
A cover page can be included for your written report. You can use this page to include graphics, list supervisors and proposers, see example cover page. Please note the rest of the document should be the standard IEEE technical paper format.
1.2 Project Title and Heading
The project title must be short as possible and capture the essence of the project.
The author of the paper is the student; the co-authors are the supervisors and project proposer. The heading of paper should follow the example below, where Lindon Falconer and Paul Aiken are the supervisors and Andrey Coy is the project proposer:
1.3 Abstract
This section is a summary of the research done. It should list the project objectives and criteria and briefly explain if the expected results were obtained.
1.4 Introduction
Should include description of problem, how other researchers approach this problem, how your solution is different and introduce your solution.
1.5 Methodology
This section should outline the design of your solution. Use the following diagrams/tables to explain the approach taken to implement your solution:
1. System Block Diagram (High level block diagram describing the entire solution, including representation of external systems that interface with your system)
2. High level circuit block diagram.
3. High level software design (flow chart)
4. Schematics diagram of electronics circuit
5. Parts List (including cost and supplier)
6. Project Gantt Chart
1.6 Results
This section outlines the results obtained from the implementation of your prototype.
1.7 Discussion
This section reflects on the work and reasons why things turned out the way they did. Were the expected results obtained? Why?
1.8 Conclusion
Summarize key points of the research. You can also make reference to future work that can be done to enhance the project.
1.9 References
Sources where you obtained information; for this paper references must be written according to the “Chicago Manual of Style”, see the following website for information: http://www.chicagomanualofstyle.org/tools_citationguide.html
Note how websites should be referenced.
1.10 Biography
A short description of your educational career (see example paper); if you choose, a photograph of yourself can be included.
1.11 Appendix
Program codes and additional diagrams or tables should be placed in this section.
2 Poster Session
The purpose of the poster session is multifold, it allows students to present their projects to the university community and have one-on-one discussion with interested persons; while gaining valuable experience that will be needed in research or making presentation for a company.
The content of the poster is a summary of the written report, so minimum effort will be required to create this document. The template at the following URL, template, should be used as a guide for preparing your poster (size of the poster is A1). Students can use a different design; however the content and the logos must remain the same. See the following links for examples of other posters; example posters 1, example poster 2, example poster 3. The examples are posters presented by final year undergraduate students at another university.
Students are required to pay for printing their poster.
Posters will be evaluated in the following areas:
-
Poster Quality
-
Background Information and Project Goals
-
Design approach testing and results
-
Oral Quality of Presenter