Preliminary Report Structure
The aim of the preliminary report is to define your intended project. The
report will constitute an agreement between you and your supervisor on the
nature and deliverables of the project. The report will also allow the
Division to approve the project as being suitable and feasible.
You must submit one copy of the preliminary report. This should be about 500
words (i.e. about 2 pages), so it should be brief and to the point. The
preliminary report must conform to the following structure:
Give your project title, student name, student registration number and
Describe the problem that you intend to tackle. Explain the scope and
objectives of the project. Describe what end-users should gain from the
work. Place the project in the context of work by others.
Explain how you intend to tackle the project. Describe any special software
or hardware that you will need. Discuss what you will need to do in order to
achieve the objectives. Highlight any special needs, e.g. languages or
packages with which you may need help or which need to be acquired. Identify
any professional issues that need particular attention (e.g. ethical, legal
or social aspects).
Give an outline plan for the remainder of the project. This should identify
the major pieces of work and when you plan to complete them. Define the
deliverables of the project. In particular, describe what you will
demonstrate as prototype for the interim report, and as completed system for
the final report.
Preliminary Report Assessment
The preliminary report must be countersigned by your supervisor before
submission. By countersigning the report, your supervisor agrees to
supervise the project as defined. The preliminary report is not formally
marked. However it will be reviewed by the Project Coordinator and Head of
Division. If the project is felt to be too trivial, too ambitious or
unachievable, you may be required to make significant changes to your plan.
The preliminary report will be returned to you after review.
Up one level to CSC9Z* (Honours Project)
Last Update: 15th February 2012