Gradle Build CodeQL Branch Coverage (Tested classes) Coverage (Tested classes) Pull Requests Website aleccoates.github.io/Dragon-Boat-Z

Contents

About Us

Ever wanted to race Dragon boats down the River Ouse? Of course, the answer is yes and we have just the game for you. DragonBoat Z!

Our Team (Quackthulu) consists of:

Game Description

Dragon Boat Z is a single-player Boat Racing game based on the annual Dragon Boat Race held in York along the River Ouse.

In Dragon Boat Z, the player competes against 6 AI opponents, racing their dragon boats across 3 legs to achieve the fastest time to cross the finish line.

Upon starting the game, the player selects 1 of 7 boats as their boat that they would like to race with. Every boat has 4 statistics with each boat having a different distribution of these statistics.

Boat Statistics

Obstacles and Penalties

During the races, there are a series of obstacles that will be floating down the Ouse. The player must avoid these obstacles in order to not damage their boat. If the boat's durability is reduced to 0 at any point within the game, the game ends and the player loses. So, watch out for those geese!! Whilst navigating the obstacles, the player must make sure to stay in their lane to avoid incurring a time penalty.

Winning the Game

If the player manages to achieve one of the 3 fastest times across the 3 legs, they will qualify for the final race where they will compete against the other 2 fastest boats. Upon completing the final race, the player will be awarded a medal, bronze, silver, or gold respective to their finishing position.

Assessment 1 Content

Deliverables

Executables

Javadocs

Weekly Snapshots

Project Gantt Chart

Sprint Dropdowns

Sprint 1 - 08/10/2020

Having completed the task of setting up Jira and other resources needed for the project, the focus was on preparatory work for the upcoming week. This involved adding to the existing set of Customer Questions constructed and develop an understanding of how GitHub Pages works.



Sprint 1 Jira Board
Sprint 2 - 15/10/2020

Having completed the Customer meeting during the last Sprint, other tasks and deliverables could now be started. The priorities are the Architecture Abstract diagram that will be reviewed at the second meeting of this Sprint, as this will allow us to make decisions such as what game library would be used. Deliverables such as Method Selection and Planning, Requirements and Risk Assessment will be built up using the now known information from the Customer Meeting alongside the starting of Sprite Design.



Sprint 2 Jira Board
Sprint 3 - 22/10/2020

Having completed the Abstract Architecture Diagram, a focus was put onto the Concrete Architecture Diagram development so it would be ready for when initial classes are constructed, based off the Gantt Chart. This also meant a decision was made on the library used for this project: LibGDX. Thus, each team member was assigned the task of completing the tutorial found in the documentation, of LibGDX, and further research. Continued deliverable work was assigned a low priority as this was considered an iterative process throughout the course of the project.



Sprint 3 Jira Board
Sprint 4 - 29/10/2020

In Sprint 3, the Concrete Architecture was created and allowed for critical tasks to begin: the initial classes. This was a high priority as delays would impact the production of the prototype on time. Further deliverable work was assigned medium/low priority. To maintain a clear separation between work, the initial one board was separated into two: Deliverables and Implementation. It was decided that second session of the Sprint would focus on the progression of these tasks and discuss if any would need to be reassigned.



Deliverables Board
Sprint 4 Delievrables Jira Board
Implementation Board
Sprint 4 Implementation Jira Board
Sprint 5 - 05/11/2020

The backlog of tasks T14 and T11, from the previous Sprint, were assigned the highest priority, as continued programming work depended on their completion. With the aim of reaching the milestone M4, at the end of this Sprint, the prototype development was a high focus. The specific tasks related to the prototype were stated within the assignee's task description. Method Selection and Planning were a focus within the Deliverables board to continue to append changes that had occurred during the project lifecycle.



Deliverables Board
Sprint 5 Jira Deliverables Board
Implementation Board
Sprint 5 Jira Implementation Board
Sprint 6 - 12/11/2020

Due to some minor issues with the construction of the legs of the game in the prototype, this task was focused on. Once completed, we envision that the final tasks to have a functioning game will be finished on time. There will be a high focus on the programming elements needed for the final product. During the second meeting of this sprint, if there is extra time to implement additional functionality of the game the task, Animations, will be attempted and potentially additional features. The Deliverables board focused on the finalising of the Implementation document, reflecting features that we have unsuccessfully managed to implement and any additional features we may include.



Deliverables Board
Sprint 6 Jira Deliverables Board
Implementation Board
Sprint 6 Jira Implementation Board
Sprint 7 - 19/11/2020

Having reached the completion of the game, a focus on the game testing and peer review of finalised deliverables was focused on. This was to ensure a successful completion of the entire project.



Sprint 7 Jira Board

Assessment 2 Content

Deliverables

Executables

Javadocs

Weekly Snapshots

Week 1 Week 2 Week 3

Project Gantt Chart

Testing

Test Designs
Test Results
Inherited Code
Fixed Inherited Code
Expanded Code
Coverage Details