Code Mapping Assignment

Why this lab looks different this week

Week 13 only meets once, for lecture, with no lab period. So instead of mapping the codebase for the final project together with your team in lab, you'll each do it solo this week and bring your notes to the Week 14 Team Sync, where your team will compare notes before anyone touches the code.

Goal

Before you fix, extend, or improve someone else's code, you have to understand what it currently does — including the parts that don't work right. This lab is about reading and tracing, not writing or fixing.

Setup

Each team member is assigned one file from the Rescue Mission starter codebase:

(Five files, so on a 3-person team, two people will map two files each — your instructor will assign these.)

Task

For your assigned file(s), write a plain-English "code map." Do not fix anything yet — this lab is understanding only.

  1. Read the whole file once through before running anything.
  2. Predict what you think each function or block does, in your own words.
  3. Run the game and deliberately exercise the parts of the game your file controls. Try normal inputs first, then unusual ones.
  4. Use an AI agent to help decode anything unfamiliar — unusual syntax, a pattern you haven't seen, a built-in function you don't recognize. Ask it to explain, not to fix. Note in your map what you asked and what it told you.
  5. Write your code map, covering:
    • What this file is responsible for, in one or two sentences.
    • A plain-English walkthrough of each function: what goes in, what comes out, what it does in between.
    • Anything unclear — code you can trace line-by-line but still don't understand the purpose of.
    • Anything that looks broken — behavior that doesn't match what you'd expect as a player, based on what you observed while playing.
    • Questions for your team — anything you want a second opinion on at Team Sync.

What to submit

A short document (half a page to a page is plenty) with the sections above. Markdown, a doc, or even organized notes are all fine — clarity matters more than formatting.

Bring this to Week 14

At the Team Sync, your team will compare all three (or however many) code maps side by side, sketch a shared picture of how the whole game currently works, and agree on what's broken before deciding who works on what.

How this will be evaluated

This lab is graded on evidence of genuine tracing and honest uncertainty, not on whether you found every bug. "I traced this function line by line and I'm still not sure why it's here" is a better answer than a confident guess that turns out to be wrong. Noting where you used an AI agent and what it told you is part of the grade — this is practice for using AI as a thinking partner, not an answer key.