In Sprint 1, each assessment group started work on the Fiery Dragons game by completing (i) a set of user stories, (ii) a Domain Model, and (iii) a low fidelity UI prototype. In Sprint 2, each team member (individually) is to continue the work started in Sprint 1 and add complete the following tasks:

• ●  An initial object-oriented design of the Fiery Dragon game (the domain model created in Sprint 1 is to be used as the starting point, but can be modified where required)

• ●  A justification (i.e. rationale) for the initial design

• ●  An implementation (in the technologies listed in Sprint 1 – they can be changed were required) of

  key elements of the design (see below for specific details)

• ●  The creation of an executable deliverable of the implementation (together with installation

  instructions) so that the implementation can be run and tested on suitable target platforms

• ●  A short, max. 3 minutes video that demonstrates how the created implementation works

  Further details of each of these tasks is given below. Looking ahead, in Sprint 3 each team is to consolidate the work done by individual team members, take the best ideas and corresponding code bases, and create a complete, fully running implementation of the Fiery Dragon’s game (no extensions required - they will be added in Sprint 4).
  
  

  Sprint 2 Deliverables (20% of final unit mark – Individual Assessment)

  All tasks are mandatory.
  
  

1. Object-Oriented Design and Design Rationales

• ●  A complete Class Diagram for the Fiery Dragon game, including class names, attributes, methods, relationship between classes, and cardinalities. UML notation is fine, but you can use other notations as well if you wish to do so.

  Note: it is strongly recommended that you complete the design task first and think through your solution approach before implementing any code. Reverse engineering designs from source code is – most of the time – a waste of anybody’s time and defeats the purpose of doing a design in the first instance. It is OK if your design is not a perfect match with the source code you are creating as long as the difference is not too substantial. We reserve the right to penalise students where we detect an obvious reverse engineering from a code base.

• ●  A summary of how the key game functionalities of
  (i) set up the initial game board (including randomised positioning for dragon cards);
  (ii) flipping of dragon (“chit”) cards;
  (iii) movement of dragon tokens based on their current position as well as the last flipped dragon