Jiasheng Cao:

He is responsible for the design of the project framework, the use of design patterns (including MVVM, Factory Pattern, Decorator Pattern, etc.) and the design of the user interface. He participates in the design of the gameplay. He is responsible for the concrete implementation of the vast majority of the project's code (Including welcome view, character creation view, game view, aftergame view, corresponding model and view model, etc.) and provides technical assistance to other members. He is involved in assigning project tasks and team roles to ensure that deadlines are met. In addition, he is responsible for presenting the project's progress at demo sessions. In addition to the above, he is also responsible for some of the testing of the code.

 

Chunzhen Hu:

Her role is to keep the team on the right track. She helps sort and organize the team's task files and helps assign tasks to team members.She contributed to the team's early design tasks. She implemented the game screens, monster creation, and score updates in this game.

 

Sarah Ann:

Her role in this team involved a lot of different things. She handled team coordination, assigning clear roles to everyone and making sure deadlines were met. She also helped with demo meetings and provided assistance wherever needed. She organized documents and focused on big picture things (like the design and diagrams) to the smaller picture stuff (enemy, level backdrop, and scoring implementation).

 

Felipe Valencia:

Felipe played an active role in both the development and testing phases of the project. He was heavily involved in the rigorous testing process that ensured the project's stability and functionality and in detecting and documenting the design patterns implemented in the code. Additionally, Felipe contributed to the team's organizational efforts by actively participating in the assignment of project tasks and the definition of team roles. This collaborative approach helped to streamline the workflow and ensure that each team member was effectively utilizing their unique skills and expertise.

 

Colin Hakes:

Colin’s role in the game development process was very flexible, filling tasks needed per sprint. This involved testing implementation, explaining design patterns or specific architecture principles, and miscellaneous factors to implement such as the basis of the scoring system or certain enemies. He also assisted in the demo meetings of the group, where progress was demonstrated to instructors. In the testing process, he was both involved in generating specific tests, but also in checking and possibly tweaking teammates tests where necessary.