CO32037 Resit Coursework
If you have any questions about this resit coursework, please, contact the
During the summer period, it may be difficult
to reach the module leader. Therefore you should at least read through
this document as early as possibly and ask questions well before the
You should expect to spend at least two weeks working on the coursework.
Therefore you should start well in advance of the deadline.
For the resit coursework you are asked to write a report about the tool
described in the original coursework.
To write this report, you will have to
implement a substantial amount of the tool. Note that in contrast to the original
coursework which asked for documentation for users, this report is not aimed
at users but instead should be written in the style of a research report.
The report should consist of at least 10 pages not counting source code
examples, which you should put in an appendix.
Your report should contain the following:
If you are resiting the coursework because you failed the original coursework,
you also need to include a detailed critical analysis of what went wrong with
your original coursework submission. For the parts that were missing or not
working properly in your original coursework submission,
you need to provide detailed descriptions and explanations of how you
overcame the problems. Your report should demonstrate that you acquired
sufficient knowledge by now to implement such a tool.
- a specification of the tool including UML (or similar) diagrams about
usage, context and components of the tool;
- a description of the different HTML pages containing screenshots and
explanations of the functionality;
- sketches of the major algorithms used by the tool including flowcharts
and source code examples;
- a critical analysis of the challenges that are posed by
the implementation of such a tool; (what is difficult to implement and
how did you overcome it?)
- a critical analysis of the CGI (or PHP) security of your tool and
of Perl/CGI (or PHP)
tools in general; (how sure are you that your tool is sufficiently secure?)
- a brief, but critical analysis of the usability of your tool;
- suggestions for future extensions for such a tool; (what would be required
to develop a commercial version of the tool?)
The last page of your report must contain a complete list of any
resources you used, such as books or code examples from the web.
You need not mention any materials from the lecture notes and exercises
found on the module webpage. If you are resiting the coursework because
you failed the original coursework, you must include a brief explanation
of which parts of the tool were in the original coursework and which
ones are new or significantly modified.
Failing to include all your sources could lead to plagiarism. Other
causes of plagiarism occur if you share your work with other students.
It is your responsibility to ensure that your files are read-protected
from others. You should not leave any printouts of your report on Campus,
not even in the rubbish bins. You should make regular backup copies of
your work, for example, by storing the files on a floppy via your I-drive.
During trimester I and II, the deadline is 11:00 am on Friday in week 13.
In some cases, you may have received a letter from the University informing
you about a deadline for resit coursework. In that case, you can also submit
your resit coursework at that deadline.
Document to be handed in
Your report should be printed and bound
or stapled. To avoid wasting large amounts of paper, you can print on
both sides of the paper or two pages per page - as long as it is
legible. Any source code examples in the appendix
can be printed using a tiny font (as long as it is legible).