CE301 Individual Capstone Project Challenge

The title page must include the project title.You must also include your name, registration number, your supervisor’s name, your second assessor's name, and degree course on the title page.

If material has been obtained from sources outside the University, for example from liaison with industry, the student may wish to make an acknowledgement.  Acknowledgement to the supervisor and any assistance from postgraduate or other undergraduates should be given.

The report should begin with an abstract or summary of what the report, not exceeding 200 words. This may be the abstract you submitted for the Open Day. It should contain sufficient information for the reader to understand what the project is about, what work has been carried out and what the final outcome of the work was.  The summary page should not be numbered, but all other pages are numbered consecutively.

The report should be subdivided into relevant sections.Each should be given a meaningful heading or subheading, and they should follow a numbering scheme as given below.

This list defines the main symbols used in the report, especially acronyms and unusual meanings.The SI unit system is standard and should not be listed here.

It must begin with setting the context of the project through a literature review demonstrating reading and comprehension of the context of your project. What problem has been solved? Why is this problem important? You must discuss the context of your product and its role in society. You must discuss any issues relating to sustainability, legal, ethical, and Intellectual property that have relevance to your project work.

After setting the context you must state the project aims and objectives. While the detailed technical documentation can go into GitLab, you can provide a summary in the final report with appropriate links. The FAQ section has examples of Technical documentation.  You should follow a technical documentation style that is appropriate to the product being developed. It is important to stress the technical achievements you have made, making it clear what you have adopted, modified, or created entirely from new.

Related topics should be kept close together, and the relationships should be clearly indicated. Explanations should be given in terms of what has already been revealed rather than in terms of what is to follow.  References should be given as close to the referred material as possible.  You should précis important material and avoid long quotations, a reference to the original work being given instead.

The main text should include no more mathematics than is absolutely essential.  Extended mathematical treatment, if necessary, may be added as an appendix at the end of the report.  A detailed explanation of, for example, a standard circuit configuration or design technique or a lengthy digression, if it must be included, should also be put in an appendix.  Parenthetical remarks and footnotes that also distract the reader’s attention from the main theme should be brief and few.

In this section you should discuss your project planning. How successful were you at maintaining momentum, adapting to change, identifying and dealing with risks. You should reflect on your overall achievements, performance, and what you have learnt. Did your methodology prove suitable?

You should conclude your report by drawing together the work you have undertaken and presenting your overall results. Make clear what has been produced against what was intended. Make comment on what future work could be undertaken to improve or further your work.

These should be numbered and listed in a special section entitled 'References', or if exhaustive, 'Bibliography', and indicated in the text by [1] for example.