Labels Milestones New Issue

Report

Label

Show archived labels Use alt + click/enter to exclude labels

All labels No label

Assignee

Assigned to nobody Assigned to anybody

snap

Your submission should include a small report with the following sections:

1. User Guide (2%)

This section should provide information for someone wishing to play your game. This section should include:

• How to play the demo.
• A control guide e.g. key / mouse / controller. A diagram would be effective.
• Known issues / bugs in this release.
• Your filled in implementation check list (see the end of this document).

Note that the mark for this section also considers general report presentation and layout (please see the school report writing guidelines) as well as correctly following the submission requirements.

2. Maintenance Guide (8%)

This section should include information for another programmer working with your code systems:

• A description of the architecture of your game engine
• • Include UML diagrams.
• • Indicate design decisions made.

3. Conclusions (4%)

This section is where you can reflect on the work carried out. You should include critical reflection on your final implementation, lessons learned and future enhancements you would like to make to the demo.

Total: 14%