Coursework Part 1

Official Frontpage of this assessment

Please, see the FAQ.

For the coursework you are asked to build an advanced server-side web application which has some graphics functionality. You can use PHP or Perl. (If you want to use another server-side scripting language, you must check with the module leader whether that is ok. In any case it needs to be a language that runs on a typical installation of Apache.)

There is a Part 2 of this coursework which consists of writing a report related to Part 1. You should read both coursework descriptions before you start working on Part 1.

Choice of topics for your application

You can choose one of the following topics for your application: In both cases, your tool should accept Unicode (utf-8) characters. Users should be given the choice of "viewing the graph" or "viewing the SVG source" (without asking them to select "view source" on their browser).

Adding more features

If you want to achieve a higher mark, you need to implement extra features using any of the topics discussed in this module (AJAX, viewing and processing of an XML file of your data, web services or other Web 2.0 features). These extra features should be related to and be well integrated with your graphics tool. Only up to 3 features will be considered for marking. Although you can discuss your ideas with the module leader, you will be given only very little help with additional features.

Diary Sheets

You should not leave your coursework to the last minute. In order to help you with your time management, you are asked to print two copies of the diary form. At two different practicals you should discuss your progress with the module leader using a diary form, which should be signed by the module leader at that time. You should hand the diary forms in at the project demonstration (see below).

Deadlines

Code hand-in: Monday in Week 11, November 16, 15:00: Demonstration: Practicals in Week 11 and 12:

Plagiarism and Safeguarding your work

Although you are allowed to use existing sources on the web, you are NOT allowed to post questions relating to the coursework on the internet or ask other people to help you in any way. During the demonstration you may be asked to explain parts of your code. All sources used must be declared in the references section of coursework part 2.

It is your responsibility to ensure that your files are read-protected from others. You should not leave any printouts of your code on Campus, not even in the rubbish bins. You should change the permissions of all your HTML files and PHP to "unreadable by others" while you are not working on the code.

Deadline Extensions

Module leaders are not allowed to give extensions. Losing your code because you didn't make backups or having problems with the Napier webserver (which is guaranteed to be slow during a time of high demand around the deadline) are not reasons for extensions.

If you have mitigating circumstances, you should discuss this with your Programme Leader who might give you an extension. But extensions of more than 2 weeks are not accepted by the module leader, even if your Programme Leader signs this. If you have severe mitigating circumstances then you must go through the official mitigating circumstances process and submit your coursework at the resit diet.

Marking Scheme

If you submit your coursework late (up to 5 working days after the deadline), the mark will be capped at 40%. After that your coursework will be marked as "fail".

You can reach a total of 50 points for the coursework. This is 50% of your final mark. The points will be distributed as follows:

Basic features (total 26):

Graphics10 points
Security5 points
Design and Usability5 points
Unicode2 points
Diary sheets4 points

Extra features (total 24):

Up to 8 points for each extra feature.