MSc in Computer Science - Interim Project Guidelines

Please note:

The typical software development type of project is a software prototype of a system, where the project can be used to research and try out a variety of ideas, obtain user feedback and the results used, if appropriate, for a more rigorous specification for subsequent development.
In addition, there are research type projects, or combinations of research and software development, where it is more difficult to be prescriptive about the project's content.

What to submit

Your interim report will consist of a Review and an Action. Along with your supervisor you need to decide what is the constitution of your project.

For Software Development projects, the Review consists of an introduction to what your project is about, your aims and objectives, and a literature survey of what is out there that does the same. For example, if you are writing a software system to send a rocket to the moon, you clearly need to review the systems already developed or attempted for this type of work by US, Russian, and Chinese software developers.
The Action then consist of chapters outlining and discussing the software specification, design, and a detailed plan for completion of the project. The plan should be linked to the stages of software development, testing, and evaluation with a resolution in terms of weeks. Some risk assessment will also be desirable. In general the software specification and design is expected to be much more advanced and developed than the "research" project model.
For Research projects, the Review consists of an introduction to what your project is about, your aims and objectives, and a literature survey of related techniques and papers already published in and around the subject. In general, the literature survey is expected to be much more indepth and thorough than the one in the "software development" model.
The Action then consist of chapters outlining and discussing the algorithm and software design, and a detailed plan for completion of the project. The plan should be linked to the stages of algorithm and software development, experimentation, and results evaluation with a resolution in terms of weeks. Some risk assessment will also be desirable.

An interim report is around 25 pages. There is no definition as to how many pages should be dedicated to each part, but clearly it will be around 12 each, + or - a few pages!

If you fail this unit, you can not continue to do your project. If you fail because the markers think only your plan is insufficiently developed, you can go ahead with your project ONLY WHEN YOUR PLAN IS RESUBMITTED AND APPROVED. Your mark will then be capped at 50%. Note this only applies to the plan part of your Action only and is not negotiable for the other parts.

You must submit completed parts, e.g. you will not be marked for the Action only if no Review is submitted! TWO printed copies should be submitted by 5:00pm and an electronic copy submitted by midnight. This report counts for 95% of the marks for the unit.

Length and Format

The reports should be approximately 25 sides of A4, including diagrams and references. Use single-spaced, 11-pt times font with a text area of approx 9" by 6". Make use of diagrams where appropriate. Avoid over use of special or colour fonts. References should be given clearly using a standard citation system. Include a front page giving the title of the project, your name, the name of your supervisor, the names of your markers, and the date.

TWO printed copies of each report should be submitted in person in room 3.37(MV), and an electronic copy should also be submitted via the online submission system.

Useful Links

Version 1.0 January 2007