^ Task: System Design

Definition

Each team will construct a system architecture document for the game code base. Use this document to plan your approach to the following considerations. Create class diagrams, flow charts, tables, lists, etc. as appropriate, and list technologies to be used.

Each team will also demonstrate the compilation and deployment process for their game.

Considerations

• authoring
  • distributed code authoring (source control & integration)
  • distributed asset creation (asset control & integration)
  • compilation process / access to latest version
  • special fonts
  • target player version
• game structure
  • attract loop
    • title
    • instructions
    • high scores
    • sample game play (optional)
  • main game
    • player join-in
    • initials entry for high scores
    • player characters
    • non-player characters
    • environmental elements
    • backgrounds
    • UI elements
• utilities
  • test plans and bug tracking
  • test harnesses
  • timing & profiling
  • graphics processing automation
  • sound processing automation

Requirements

Every member of the team must individually be able to check in updates and see the results in-game in order for development to be a largely parallel process. Fundamental changes will undoubtedly need to occur, so please consider what to do when they become necessary. Plan, implement, and document the process for a team member to insert any of the following and obtain the latest version of the game:

• graphic assets
  • update of existing art
  • introduction of new art
  • backgrounds
  • sprite graphics
  • UI elements
  • attract loop screens / edits
• audio assets
  • update of existing sound
  • introduction of new sound
  • background music
  • foley effects
  • UI sounds
  • attract loop screen music
• code assets
  • update of existing code
  • introduction of new code / class
  • timeline scripts
  • course class / library updates

Grading Criteria