Standards

This page is intended to make standards alignment easier to discuss without letting it take over the live experience. It is most useful in planning, reporting, or curriculum conversations.

Standards Alignment Areas

The table below gives educators a compact way to describe the alignment in planning documents, grant reports, or curriculum conversations. Use district or state-specific codes where required; the language here is intentionally broad so it can map cleanly to several middle school standards frameworks.

Alignment area What learners do in the experience Evidence educators can capture
Algorithms and Programming Use events, variables, conditions, and block sequences to make the game respond to player actions and changing conditions. A student explains which block or value changed the car, score, life, weather, or strategy result.
Data and Analysis Use score, efficiency, collisions, pit stops, and saved results as evidence for decisions. A student compares two runs or names which result should guide the next test.
Engineering Design Make setup choices under constraints, test the result, and revise based on tradeoffs. A student identifies what improved, what became harder, and what they would test next.
Digital Literacy and Collaboration Work with a partner, follow a guided technical workflow, and communicate observations clearly. A team uses Driver/Navigator roles or explains a shared decision during a pause point.
Career Exploration Connect gameplay decisions to software, data, strategy, design, systems, operations, or sustainability roles. A student names a role and explains why that role would care about a specific game moment.

Computer Science

The experience supports core computer science ideas by making them visible through gameplay and guided building.

  • cause-and-effect reasoning through code or block changes
  • event-driven behavior through buttons, overlaps, and changing conditions
  • debugging, iteration, and refinement through repeated test loops
  • variables, conditions, and feedback as tools for controlling system behavior

Engineering and Design

Driven by STEM is especially strong when framed as an engineering design experience.

  • learners make choices under constraints rather than chase one perfect answer
  • the activity highlights tradeoffs between performance, control, efficiency, and sustainability
  • students predict, test, compare, and revise
  • evidence from the game becomes part of how they justify a decision

Digital Literacy and Communication

The project also supports communication and collaborative reasoning.

  • learners explain what changed and why it mattered
  • pairs or teams can divide roles such as Driver and Navigator
  • students practice using evidence instead of opinion alone
  • reflection prompts support clear language about design, usability, and strategy

Career Exploration and Applied STEM

One of the strongest features of the experience is that it connects gameplay to real roles without breaking the flow.

  • software engineer
  • telemetry or data analyst
  • strategist
  • designer or UX thinker
  • operations and systems roles
  • sustainability-focused decision-making

Practical Fit for Planning

This experience works best when standards are used to frame:

  • design reasoning
  • collaboration
  • reflection
  • communication about evidence

It is less effective when standards are used to interrupt the build-test-improve rhythm with too much front-loaded explanation.

What to Capture as Evidence

For planning or reporting, useful evidence includes:

  • a student’s explanation of what they changed and why
  • a prediction before a test run
  • a comparison between two setups or results
  • a reflection on one tradeoff or one next step
  • a career connection grounded in a specific gameplay moment

Copyable Planning Summary

Driven by STEM supports middle school computer science, engineering design, digital literacy, and career exploration through a browser-based MakeCode Arcade skillmap. Learners build and test an F1-inspired simulator, adjust variables and rules, observe performance and efficiency tradeoffs, use gameplay data as evidence, and connect decisions to real STEM team roles. Assessment can be based on short explanations, prediction-test-reflect moments, replay comparisons, and student descriptions of what they would improve next.

Facilitation Note

Standards mapping belongs in planning notes. During the live session, the focus should stay on play, evidence, and discussion.