Week 4 10/20-10/27

We began architecting our code (specifically, we have made progress on our domain and class diagrams, and must still do our sequence diagram), added some additional user stories, added some art assets.

Prior week's goal stack:

Add art assets, especially for the Game Treatment. We need to make sure the kids themselves are on board at this stage of the concept/implementation. We also need these moving forward.

Complete the Sprite Kit Programming Guide, and any other tutorials/guides that may catch your interest.

This week's goal stack: NOTE we completed everything from before break. Time to get down and dirty with the code.

Complete domain, class, and sequence UML diagrams.

Add stories/use cases as we complete the above documents detailing any additional features, uses, or clarifications/compromises made as we design our architecture.

Describe the important models/algorithms/data strcutures used in our architecture. (i.e. how we represent the level, states, and fuel bar.)

Critique our design, attempting to remove any inconsistencies prior to handing the design over for review.

Articulate in a written document a rationale for our architecture choices.

Prepare for the architecture design review.