Project One Design

Project One Design

Project One is the Module Five Analyze + Design checkpoint. The final game code is not the graded deliverable yet.

Required Project One Submissions

1. design/game_storyboard.md
2. design/game_map.drawio
3. design/move.pseudo
4. design/get_item.pseudo

Storyboard and Map

The design must establish your own game world, including:

• Theme and storyline
• At least eight rooms
• At least six items for the minimum eight-room design
• One item in every room except the start room and villain room
• Start room with no item
• Villain room with no item
• Winnable placement of rooms/items/villain

The map later becomes the main source for the Project Two room/item dictionary.

Move and Get-Item Pseudocode

The course provides flowcharts for these processes. Use them to reason about:

• Input
• Validation
• Valid and invalid paths
• Output
• Decision branching
• Repetition

Write pseudocode, not Python.

Project One Rubric

Criterion	Weight
Storyboard: Theme and Map	20%
Pseudocode: Logical Steps and Functionality	30%
Pseudocode: Input / Output	20%
Pseudocode: Program Flow	25%
Clear Communication	5%

Consistency Matters

The four files should describe one game. Check room, item, and villain names before submitting.

A useful final design test is to trace a complete winning route through the map while asking whether the movement and get-item pseudocode could support each step.

What Happens to the Design Later?

• Module Six: move.pseudo helps you think about a reduced movement implementation, but the milestone uses its own sample dictionary.
• Module Seven: all four Project One artifacts return as implementation inputs for the final game.

Do not overwrite your design with the milestone sample world.