A demonstration of a prototype user interface design is due in the week beginning 15/3/99, and is worth 15% of the overall assessment for this course. These demonstrations will take place in the Computer Science NT Lab (E250), in normal tutorial times:

Wednesday 17/3 14:00 - 15:00

Thursday 18/3 10:00 - 12:00

Thursday 18/3 16:00 - 17:00 (KST2 have priority)

You should choose a time when all of your group can attend, and sign up on the sheet on the noticeboard. We can run up to three demonstrations at the same time.

You will need to make sure that your prototype will run successfully on the NT machines in E250 - doing this is your responsibility. You are advised to arrive early in order to set up your system - extra machines will be available to allow for this. You can bring your own machine if this is convenient.

The point of this exercise is to assess the quality of your proposed user interface. We will combine (at least) two roles: a) Willowbank staff who will be using this system, and b) lecturers assessing the extent to which a piece of work meets criteria laid out in the taught material on this subject.

This is just an assessment of the user interface, so we are not concerned with the validity of the output produced by the program; any output which illustrates how the UI will function is acceptable.

We will look at the overall organisation of your user interface, starting at the main screen(s)/window(s), and at how the user finds their way around it. In particular, we will want to see a demonstration of your user interface for some of the following tasks:

start up - Receptionist starts up the Booking system at the start of a days' work

make a booking - Member phones up to book a court for a particular sport/date/time/duration

pay and play - Member turns up with a guest to play an unpaid session, pays for it and plays.

accept subscription - Member pays their sub for the year

add a new member - enter details and accept pro-rata subscription

log on - as Administrator

remove court - make court unavailable for a period (repair, etc)

change price bands for sessions

overdue members - produce list of members whose subs are overdue (including hardcopy)

The distinction between "client" and "server" here just corresponds to two levels of access; we don't expect these to be separate programs.