The project is 10 credits, i.e. each team member is expected to spend 1/6 of their woking time on the project. For an average student aiming for an average mark, this equates to 6.5 hours per week.

It is vital that all members of the team keep in regular contact with each other. The complete team is required to meet the demonstrator regularly once a week to discuss progress. Absences without good cause may be penalised.

In addition, it is essential that the members of the team meet more frequently than once a week on a working basis. If you do not regularly meet in the computer room, you should arrange alternative meetings (e.g. after a lecture that everyone attends). The team cannot work properly if the members of the team are not in regular and frequent contact with each other.

The team leader (or any member of the team) should inform the lecturer in charge of the Software Workshop of any team member who is persistently failing to attend meetings or otherwise keep in contact with the rest of the team.

Each student should keep a personal diary of the time he spends on various aspects of this project. The categories to be distinguished are:

1. background reading
2. specification and design
3. coding and testing
4. writing the report
5. team meetings and walkthroughs (including seeing your demonstrator).

Your diary must be submitted with the final report.

Use a small notebook for your diary and always make entries immediately - by tomorrow you will probably have forgotten! You may be required to produce your diary for inspection at any time during the course of the project.

This should be kept on paper or on the computer. Every entry should be dated and signed if possible. The main purpose of the diary is to record the overall progress of the work. All work allocations should be noted in the diary and work completed should be ‘signed off’ by the author of the work. Subsequent discovery of bugs should also be noted and corrected work signed off also.