2025-group-5

2025 COMSM0166 group 5

Your Game

Link to your game PLAY HERE The Canvas: https://editor.p5js.org/chyx-17/full/gs4csAz5Y change color：press 'R','G', 'B'. change shape: press '1','2','3'.

Your game lives in the /docs folder, and is published using Github pages to the link above.

Include a demo video of your game here (you don't have to wait until the end, you can insert a work in progress video)

Kanban Link

https://wuxiaoalfie.atlassian.net/jira/software/projects/MFLP/boards/1

Your Group

• Group member 1, Jingwei Lin, [email protected], ZhiyiJaved
• Group member 2, Xiao Wu, [email protected], Alfie-wuxiao
• Group member 3, Shaojie Yang, [email protected], YYYYWhy
• Group member 4, Yaoyao Shen, [email protected], YasmineShen
• Group member 5, Xinyi Zhou, [email protected], Neltharion-Z
• Group member 6, Yaxin Chen, [email protected], chyx-17

Project Report

Introduction

• 5% ~250 words
• Describe your game, what is based on, what makes it novel?

Requirements

1. List of Stakeholders • Players: Expect a smooth gameplay experience and engaging challenges. • Development Team: Wants a clean and maintainable code structure for easy expansion. • Product Manager: Hopes the game is easy to understand and suitable for players of all ages. • Testers: Ensure the game is free from major bugs and runs stably.

---

2. Epics and User Stories Epic 1: Core Gameplay • User Story 1.1 (As a player, I want to control the dragon’s movement so that I can survive longer in the game). • User Story 1.2 (As a player, I want the dragon to gain length when it eats food to increase the game’s challenge). • User Story 1.3 (As a player, I want the game to end if the dragon crashes into walls or itself, adding difficulty to the game). Epic 2: Game Interface and Experience Optimization • User Story 2.1 (As a player, I want a score counter so that I can track my game performance). • User Story 2.2 (As a player, I want start, pause, and restart buttons for easier control). • User Story 2.3 (As a player, I want to choose different difficulty levels to experience different challenges).

---

3. Reflection During the development of the Dragon Game, our team learned about epics and user stories and applied them to our requirements analysis. Here are our key takeaways:
4. Breaking Down Epics and User Stories o Epics helped us understand the game’s core functionalities, while user stories allowed us to define specific details. o Initially, we only had the idea of "making a dragon game," but by breaking it down, we realized we needed to consider aspects like core gameplay, interface optimization, and additional features.
5. Acceptance Criteria o While defining each user story, we also considered its acceptance criteria. For example, when the dragon eats food, it should gain health or receive buffs; otherwise, the feature would be incomplete. o This helped us realize that well-defined acceptance criteria provide clear development goals and reduce ambiguity.
6. Contextual Analysis of the Game o Through analysis, we found that the game’s primary audience consists of casual players. Therefore, we needed intuitive controls and a user-friendly UI design. o Additionally, we considered features like an infinite mode to enhance competitiveness and engagement.

Design

• 15% ~750 words

• System architecture

• Class diagram

• behavioural diagram

Implementation

• 15% ~750 words

• Describe implementation of your game, in particular highlighting the three areas of challenge in developing your game.

Evaluation

• 15% ~750 words

• One qualitative evaluation (your choice)

• One quantitative evaluation (of your choice)

• Description of how code was tested.

Process

• 15% ~750 words

• Teamwork. How did you work together, what tools did you use. Did you have team roles? Reflection on how you worked together.

Conclusion

• 10% ~500 words

• Reflect on project as a whole. Lessons learned. Reflect on challenges. Future work.

Contribution Statement

• Provide a table of everyone's contribution, which may be used to weight individual grades. We expect that the contribution will be split evenly across team-members in most cases. Let us know as soon as possible if there are any issues with teamwork as soon as they are apparent.

Additional Marks

You can delete this section in your own repo, it's just here for information. in addition to the marks above, we will be marking you on the following two points:

• Quality of report writing, presentation, use of figures and visual material (5%)

  • Please write in a clear concise manner suitable for an interested layperson. Write as if this repo was publicly available.

• Documentation of code (5%)

  • Is your repo clearly organised?
  • Is code well commented throughout?