Junior Honours Team Project
Team reports should be submitted by the deadlines specified on MMS. The same team report should be submitted by each team member.
There is no explicit word limit for a JH project report, but conciseness is desirable in your writing. It will usually not be necessary to go over 10,000 for your JH project. The project library contains JH projects with word counts as low as 6,000 and as high as 16,000, all of which achieved excellent grades.
Team reports should contain the following:
| Section | Content |
|---|---|
| Title Page | Containing the title of the project, the names of the team members, “University of St Andrews” and the date of submission. |
| Abstract | Outlining in about 100 words the work of the project overall and the team specifically. |
| Declaration | “We declare that the material submitted for assessment is our own work except where credit is explicitly given to others by citation or acknowledgement. This work was performed during the current academic year except where otherwise stated. The main text of this project report is NN,NNN words long, including project specification and plan. In submitting this project report to the University of St Andrews, we give permission for it to be made available for use in accordance with the regulations of the University Library. We also give permission for the report to be made available on the Web, for this work to be used in research within the University of St Andrews, and for any software to be released on an open source basis. We retain the copyright in this work, and ownership of any resulting intellectual property.”* |
| Contents page | |
| Introduction | Describing the problem the team set out to solve and the extent of its success in solving it. The section should outline key aspects of the project for the reader to look for in the rest of the report. |
| Project details | Summarising the achievements of the project, and discussing those aspects of the project that are of particular interest: the main ideas of the design, unusual design features, special algorithms and data structures, odd implementation decisions, novel user interface features, etc. |
| Evaluation and critical appraisal | Evaluating the work with respect to the original objectives. The section should also critically evaluate the work with respect to related work done by others. It should compare and contrast the project with similar work in the public domain, for example as written about in published papers, or as distributed in software available to the team. |
| Conclusions | Summarising the project, emphasising key achievements and significant drawbacks, and discussing possible future directions for the work. |
| Appendices | Project objectives, specification, plan, and interim report as submitted during the year, followed by a list of changes that should be made in the light of experience, e.g. additional references, new software modules, changed specifications. |
| Testing summary | Describing the steps taken to debug, test, verify or otherwise confirm the correctness of the various modules and their combination. |
*Any request for permission to omit parts of the declaration should be directed to the project coordinator.