Team 16:

Finite State Machines

Bryan Trujillo: btrujillo@hmc.edu

Eoin Nugent: enugent@hmc.edu

Ethan Kenny: ekenny@hmc.edu

John Shaugnessy: jshaughnessy14@students.claremontmckenna.edu


Meetings:

Meeting 1: Thursday 9/26

First meeting in class, chose roles, threw around project ideas.


Meeting 2: Monday 9/30

Discussed project ideas, looked through CSunplugged, etc.


Meeting 3: Thursday 10/3 (Client meeting)

Our client approved of our idea, we received information on intended audience.


Meeting 4: Friday 10/4 (Lab)

Created High Concept, Competitive Analysis, and Customer Elicitation Documents


Meeting 5: Thursday 10/10 (Pseudo-lab)

Created Game Treatment, Stories/Use Cases, and Tech Assessment Documents


Meeting 6: Thursday 10/17

Completed the Game Proposal, discussed what we will work on after fall break.


Meeting 7: Friday 10/24

Completed our domain diagram and class diagram, added some stories/use cases. Will meet Tuesday to finish architecture design.


Meeting 8: Tuesday 10/29

Completed our Architecture Design and Architecture Design Review packages.


Meeting 9: Thursday 11/7, Friday 11/8

Completed our Task Analysis document, prepared for UI Test tomorrow, Friday 11/8. Completed the Design Test Notes and Final UI Design documents.


Meeting 10: Sunday 11/10

Completed a basic prototype of the game, with most of the functionality for a single level. Delegated the next week's goal stack among the team members.


Meeting 11: Friday 11/22

Completed the alpha, prepared our presentation, and planned our new goal stack.


Meeting 12: Tuesday 12/3

Completed the Test Plan, made some progress on the game.


Meeting 13: Sunday 12/8

Created the final prioritized goal stack--these are goals to be completed for the final beta that we will demo on Thursday.


Weekly Project Assessment/Plan:

Week 0: 9/26-9/29

Introduction to group/team dynamics, some concept creation.


Week 1: 9/30-10/6

Finalize game dynamics/concept for elicitation, proceed to setting goals.


Week 2: 10/7-10/13

Added to game concept (especially the non-functional parts; viz., art assets, adventure vs puzzle, map-based vs levels, etc.)


Week 3: 10/14-10/20

Prepared concept presentation, assessed goals/risks, prepared for start of implementation.


Week 4: 10/20-10/27

Began architecting and designing code.


Week 5: 10/28-11/3

Completed the alpha Architecture Design and Architecture Design Review Packages.


Week 6: 11/4-11/11

Completed the Initial UI Design (see the Task Analysis for a picture of the setup), the Task Analysis, Design Test Notes, and Final UI Documents.


Week 7:11/11-11/18

Added features to our prototype, including updated paths/ship movement, improved fuel cells/fuel bar, added flame exhaust to ship, etc.


Week 8: 11/18-11/25

Completed the alpha, prepared our presentation.


Week 9: 11/25-12/2

Completed the Test Plan


Week 10: 12/2-THE END

Created the final week's goal plan. Completed the beta (see github) and Beta Presentation for the end of the semester.


Deliverables:

Phase 1

Phase 2

Will be updated with new phases...


Individual work logs

NOTE: These will be added when I hear back from the team.

Bryan Trujillo

Eoin Nugent

Ethan Kenny

John Shaughnessy


Customer Updates

This will be updated weekly with our progress on the game!


Problem Reports

We have yet to face any significant technical or personal problems. If we do come across any, we will update this section.