Latest game version entry point (click the link in the main README to play):
https://github.com/angelicaserein/UhelpU
Group 13 | COMSM0166 | 2025–2026
Demo: April 28 | Final Submission: May 1st, 12:00
⚠️ Important Reminders
| Member | Main Tasks | Internal Deadline | Notes |
|---|---|---|---|
| Member 1 | Fix level bugs + adjust difficulty progression + manual test records (write into Evaluation) | April 20 | Focus on levels, no redesign |
| Member 2 | Requirements section (~750 words) | April 15 | Use case diagram + user stories + ideation process |
| Member 3 | Design section (~750 words) | April 15 | Complete class diagram + behavioural diagram + system architecture description |
| Member 4 | Process section (~750 words) | April 15 | Team collaboration methods, tools, reflection (write honestly) |
| Member 5 | Conclusion section (~500 words) | April 15 | Summary + lessons learned + future plans |
| Member 6 | README update + demo video recording | April 21 | Screenshots/links/group photo/roles/video |
| Date | Goal | Responsible | ||
|---|---|---|---|---|
| April 8 (today) | Everyone read the WeChat messages | All members | ||
| April 15 | Requirements / Design / Process / Conclusion / demo video first draft complete | Members 2, 3, 4, 5, 6 | done | |
| April 16–20 | Peer review and revise report + continue fixing levels | All members | All written in English? Layout clear and clean? Content concise? Images instead of text? Word count requirements met for each section? | |
| April 21–27 | Final level polish + record demo video + final README update | All members | ||
| April 28 | ⚠️ Demo presentation (all day, all members must attend) | All members | ||
| April 29–30 | Final review, code cleanup, comment completion | All members | ||
| May 1st, 12:00 | ⚠️ Final submission deadline for report + code | All members |
| Item | Description |
|---|---|
| Task 1 | Fix existing bugs in the 4 new levels |
| Task 2 | Adjust level difficulty progression (simple to complex, smooth transitions) |
| Task 3 | Create manual test checklist: test points for each level (collision / recording playback / edge cases, etc.) |
| Task 4 | Record test results, write into the [Code Testing] section of the report's Evaluation chapter |
| Deadline | April 20 (levels) / April 20 (test records) |
| Item | Description | |
|---|---|---|
| Weight | 15% \ | ~750 words |
| Deadline | April 15 (first draft) | |
| Content 1 | Team's initial ideation process: how did you decide to make this game? | Not a priority for now |
| Content 2 | Use Case Diagram: illustrate player interaction with the game system | Not a priority for now |
| Content 3 | User Stories: e.g. "As a player, I want to see a recording of my past actions" | Read the week 4 requirements document, play through the current game version, remove unfinished requirements, add new ones |