Final Year Project Guidelines 1

Final Year Project

Guidelines
Final Year Project Guidelines 2

A Typical Project
A typical project would consist of the research and
development of a specific application requiring you to
Consider various alternative software technologies.
Decide on the appropriate technology.
Complete a prototype/ coding examples
Outline a Specification of completed system
Do an implementation
Final Year Project Guidelines 3

Final Report
Introduction (based on Project Proposal)
Research
Technologies
Application Domain
Requirements
Architecture
Design
Implementation
Testing and Evaluation
Conclusions
References/Bibliography
Glossary (optional)
Appendix (programming code where appropriate)
Final Year Project Guidelines 4

Project Proposal
This should be a couple of pages.
It should state clearly the aims and objectives of the
project.
It will be used as the basis for the Introduction in your
project report.
Could include a Wireframe mockup of what the main user
interface might look like (if appropriate)

Final Year Project Guidelines 5

Interim Project Presentation
December (reading week)
Presentation only, no application demonstration
Could include
Introduction to project
Background Research
Application Domain
Technologies
Screen dumps of any prototypes
Final Requirements for competed system
Final Year Project Guidelines 6

Requirements Document
Due in December.
It should set out the requirements, both function and non-
functional, for the software (hardware) to be developed.
It will form chapter 3 of your report.
Final Year Project Guidelines 7

Architecture
Should explain the high level architecture of the software
system to be developed.
Diagrams are particularly useful.
Final Year Project Guidelines 8

Design
Include UML (or equivalent) diagrams.
Final Year Project Guidelines 9

Implementation
For a software project
Screen dumps of the application GUI.
Snippets of code and associated explanations. (The full
source code listing goes in the appendix.)
Final Year Project Guidelines 10

Evaluation & Conclusion
Should restate the original objectives of the project and
discuss how well each was achieved.
Evaluate how well the functional and non-functional
requirements have been addressed in the project.
Evaluate how Design/Technology decision (e.g. if you were
doing the project again would you still use same tools).
Evaluate appropriateness of the solution.
Final Year Project Guidelines 11

References/Bibliography
References :-
All references should be listed at the end of the report.
References should be cited within the text using an
appropriate and consistent notation, such as first authors
surname and year e.g. (Torvalds, 2008).
It is preferable to use book, journal or conference paper
references rather than Web references (This is not always
possible)
These can be obtained using the inter-library loan
facilities/library databases
Final Year Project Guidelines 12

Project Report Guidelines:-
Regulations
The report should be your own work.
Anything included word for word from another source
should be quoted and referenced.
Direct copying of other peoples work without references is
forbidden by copyright law.
It is also a violation of exam regulations and as such is a
disciplinary matter for the college.
Note that if you cut and paste text from the Web it is
relatively easy to spot in a report and with the help of a
search engine and/or other tools the source can normally be
identified in a matter of minutes.
Final Year Project Guidelines 13

Project Report Guidelines :-
Report
Use the spell checker and grammar checker included with
your Office software.
No company logos in the report.
Submit one hard-bound copy and one soft-bound (spiral-
bound) copy of your report.
B.Eng reports should be bound in black.