The MBC information booklet - RMIT University

Chapter 11: Minor Thesis/Project
54
1. A title page as shown below (do not use the RMIT logo):
2. A declaration page as shown below:
A Java based tool for manipulating course
approval documents
by
Virginia Leanne Ruttaputnam, B.Sc.
A Minor project submitted in partial fulfilment
of the requirements for the degree of Master
of Applied Science in Information Technology
School of Computer Science and Information
Technology
RMIT University
Figure 3: Title Page for Minor Project
Declaration
I certify that all work on this project was carried out between X
and Y and has not been submitted for any academic award at any
other college, institue or university. The work presented was
carried out under the supervision of Dr ... who proposed ... and
who .... This is my original work and no part of it has been copied
from any other source except where due acknowledgement is
made.
No part of this thesis has been written for me by any other person
except where such collaboration has been authorised by my
supervisor (as described on page X). This thesis may be
reproduced, communicated, compared and archived for the
purpose of detecting plaiarism.
I give permission for a copy of my marked work to be retained by
the School for review and comparison, including review by
external examiners.
Plagiarism is the presentation of the work, idea or creation of
another person as though it is your own. It is a form of cheating
and is a very serious academic offence that may lead to expulsion
from the University. Plagiarised material can be drawn from, and
presented in, written, graphioc and visual form, including
electronic data, and oral presentations. Plagiarism occurs when the
original of the material used is not appropriately sited.
Virginia Leanne Ruttaputnam
June 17, 2006
Figure 4: Declaration Page for Minor Project
3. A table of contents.
4. A table of figures (where relevant).
5. An acknowledgment page (where desired).
6. An introductory chapter which motivates the need/use of the program.
7. An optional literature chapter (where relevant) which compares this approach to
existing approaches.
8. A specification chapter. The program requirements are specified using formal
notation.
9. A design chapter. The program design is specified using formal notation.
10. A testing chapter (sic) which describes the testing regime employed.
11. A conclusion.
12. An appendix consisting of a user manual.
13. Other appendices may include, where relevant, code fragments, further definitions
etc.