[an error occurred while processing this directive]

The Major Project

Specification | Examples | Help | Getting Started | Due Date | Marking Scale | Diary | Plagiarism | Copyright | Submitting | Revision History

Specification

The precise description of what you are to do

Examples

Each team is responsible for generating their own tests and test data. It is quite acceptable for students to share tests and test data - provided that you do not reveal your solution or assessible code.

Share data via the FAQ.

Help

Frequently Asked Questions (FAQ) - Ask your question here. Read this regularly. Please also answer questions or offer what help you can to unanswered questions. Please treat this FAQ as an open public forum for 1711 students.

All students have access premission to ask and to offer answers in this FAQ.

Getting Started

Step 1: Create a directory project to store all your assignment work. Download all files to your new directory.

Step 2: Read all files carefully. As stated in task 1 - a past student recommends:

"Read the spec at least three times before starting. It is far too easy to start writing a program and realize that you've spent two hours programming the wrong thing!"

Step 3: Prepare carefully for your week 8 tutorial.

Step 4: Read the FAQ. And re-read it regularly during the assignment period. If at any stage you have any problems or questions, read the FAQ first! If no-one has asked the question yet, add your question to the FAQ.

Step 5:Think about a backup strategy for your work to allow you to recover files after a catastrophie (eg your computer might get stolen during the assignment).

Due Date

The task is due 23:59 Sunday 25 May 2003.

Normal late penalties apply for submissions on Monday. No submissions will be accepted afer 23:59 Monday.

Marking scale

20 Marks for your Location/Strategy module, and 5 marks for your (revised) Network module.

Subjective marks 25%, and performance 75%. There are some bonus marks available, up to 3 for the comp and up to 3 for good isUnsafe() functions. Up to a maximum of 5 marks per person.

The Location/Strategy module must be your own coding. You only submit one of these modules. This mark will be an individual mark.

Both members of your team are to submit the same Network module. This mark will be a group mark and both members will receive the same mark.

Each member is to maintain their own diary. These will be marked individually, not one per team.

You may add the 3 new network functions to whichever task2 Network module you wish - either use one of the group member's submission, one from a third party, or write a new one from scratch!

For the Location Module: The performance mark will be calculated by autotesting your functions against a suite of simple tests. These will check that various combinations and sequences of your functions produce a correct final output.

For the Strategy Module: the performance mark will be awarded in the same way as for the Location module - save that the ai() function will be awarded marks for:

The subjective mark is determined by your tutor and will measure:

  1. Meaningful names
  2. Good commenting
  3. Appropriate breakdown of functions into subfunctions
  4. Layout of code
  5. Clarity
  6. Non trivial diary
  7. Complience with interface
  8. Clarity and Completeness of your Strategy/Location type
  9. How easy it is to understand your program

"Clarity and completeness" means how easy the implementation of your Abstract type is to understand, and whether or not it is sufficient to include all the information needed to be able to efficiently implement the interface functions.

If you have any questions about how the subjective marks are awarded you can ask your tutor in your tutorial.

Each team member receives the same bonus marks.

Assignment Diary

You are to keep a diary for this assignment. Each day write down what you did, problems you had, ideas, and breakthroughs etc. The diary should be at least 4 pages long by the end of the assignment. Record your diary in text format (NOT word format) in a file called Diary.txt.

Plagiarism

Penalties for copying or letting others copy part of your assignment are severe. See the subject information page for more details. This warning was repeated in the Wednesday Week 3 lecture. If you are unsure what constitutes copying ASK the lecturer, the administrator, or your tutor.

Students can help each other with ideas and debugging. However the code you submit must be wholly your own.

Copyright

Copyright of any material you submit will belong to the university. Submitting means you accept this condition. The reason we require this is so we can use your work as an example to students in future sessions. If you wish to discuss this policy please talk to the lecturer about it before submitting.

This clause will be slightly ammended once i work out how to alter the wording for task2.

Submitting

How to Submit:

Click here for submission procedures.

Revision History

[an error occurred while processing this directive]