Button Scoring Systems

Overview

Today students continue designing their micro:bit game by building a scoring system using button controls and clear game mechanics. They connect real-world scoring ideas to fraction/ratio reasoning and use ordered pairs and sign reasoning to describe where scores and feedback “belong” in the game interface.

Learning intentions

Students will be able to:

• Implement a two-button scoring mechanic so each press changes the score predictably.
• Explain and justify how their game rules translate into program behavior.
• Use visual models and equations to interpret and compute outcomes from fractional sharing contexts that resemble “equal turns” or “balanced scoring.”
• Describe game feedback using ordered pairs in all quadrants (including negative values like “penalty points”).

Success criteria

• I can describe my game’s win/lose conditions and scoring rules in plain language.
• I can implement Button A and Button B so points update correctly every time a player presses.
• I can represent my scoring logic with an equation and explain why it works.
• I can plot a score/feedback ordered pair and explain how it changes when a sign changes (positive vs negative).

Curriculum links

• The Number System — Interpret and compute quotients of fractions, and solve word problems involving division of fractions by fractions.
• The Number System — Understand positive and negative numbers used together to describe opposite directions or values; explain 0 in context.
• The Number System — Understand signs of numbers in ordered pairs as indicating locations in quadrants; recognize reflections across axes.

Lesson structure (45 minutes)

1. 0–5 min · Hook (Game rules remix). Teacher shows two mini examples: “Press A = +2 points, press B = -1 penalty.” Students predict the score after 5 presses in a quick think-pair-share.

2. 5–12 min · Micro:bit design mini-teach (mechanics + UX). Teacher models a scoring loop concept: input (button press) → update (score) → output (display/feedback). Students sketch a 3-step flow in notebooks and label which step is “user experience” (what the player sees/feels).

3. 12–20 min · Math connection: fraction sharing as “balanced turns.” Teacher poses a 6th-grade story: “3 players share 1/2 lb of chocolate equally—how much does each get?” Students use a simple visual fraction model (draw a bar split into equal parts), then write the division equation that matches the model. Bridge to game: “Balanced turns” is like distributing points fairly across players or rounds.

4. 20–30 min · Ordered pairs for feedback (positive/negative points). Teacher draws a coordinate grid and explains: (score, feedback) as an ordered pair. Example: (4, 1) is positive score and positive feedback; (4, -1) is positive score but negative feedback (like “bonus not earned”). Students choose one of their own rule outcomes and create an ordered pair using a negative value for penalty.

5. 30–40 min · Build time: scoring buttons in their game. Teacher circulates with a checklist: students must wire/assign Button A and Button B actions and ensure the score updates correctly and displays after each press (or at least after each event). Students implement and test their scoring mechanic.

6. 40–45 min · Exit reflection: explain it like a designer. Students answer two prompts on a half-sheet:

• “If a player presses Button A twice and Button B once, what is the score change?”
• “Describe one ordered pair (score, feedback) for your game and explain what the sign means.”

Resources

• micro:bit kits with batteries or power source
• laptops/tablets with micro:bit coding environment installed
• teacher-created scoring rule examples (printed or on board)
• coordinate grid handout (single page)
• notebook or scoring sheet template (rules → equation → ordered pairs)
• timers for structured build/test minutes
• optional: small sticky-note labels for “UX feedback” (display text, sound, LED)

Assessment

• During hook and mini-teach: listen for correct predictions of score changes after button presses.
• During build: use a quick observation checklist (both buttons mapped, score updates, display/feedback happens).
• Exit ticket: verify students can (1) compute net score change and (2) explain the meaning of positive/negative signs in an ordered pair.

Differentiation

• Support: provide sentence starters and a scoring template: “Button A increases score by __. Button B decreases score by __.” Include a completed example of a fraction sharing model to reduce math load while keeping the connection.
• Support for writing ordered pairs: offer a word bank: “positive,” “negative,” “penalty,” “reward,” and “0 means no change/no penalty.”
• Advanced learners: require a “fairness” extension by adding a rule that ties scoring to fractional sharing (e.g., “Each round awards points equal to a fraction of the total turn value,” and students must justify the division with a visual model and equation).
• EAL/SEN: allow students to submit the ordered pair explanation using a diagram plus one-word labels (e.g., “+ reward,” “- penalty”) before full sentences.