Fractions | Small Group
Students use coding logic to model fractions by identifying parts of a whole, comparing fractional values, and creating simple code-like instructions to represent fraction operations and visual models.
| Term | Definition |
|---|---|
| fraction | A number that names equal parts of a whole. |
| numerator | The top number in a fraction; it shows how many parts are being counted. |
| denominator | The bottom number in a fraction; it shows how many equal parts make the whole. |
| equivalent | Different fractions that name the same amount. |
| sequence | An ordered set of steps or instructions. |
| debug | To find and fix mistakes in code or logic. |
Display 3 to 4 fractions and ask the group to sort them from least to greatest, explaining each choice with numerator and denominator language.
Discuss in pairs, then share one reasoning statement aloud.
Model how a fraction can be written as a sequence of instructions, such as 'divide the shape into 4 equal parts, shade 3 parts.' Connect this to coding: clear order, precision, and no extra steps.
Listen, annotate, and repeat the sequence using math vocabulary.
Give each group a fraction card. Ask them to write a 3- to 4-step algorithm to represent that fraction on a grid or strip, then test it with another group.
Create the algorithm, check each step for clarity, and swap with another group for testing.
Present an incorrect fraction sequence, such as shading 2 out of 5 parts to represent 3/5. Ask groups to find the error and correct the steps.
Identify the mistake, explain why it is wrong, and rewrite the corrected code.
Invite groups to share one algorithm and one debugged correction. Highlight strong use of precise language and logical order.
Present briefly and reflect on how coding helps make fraction thinking clear.
End with a quick exit share: each group states one thing that makes fraction code accurate and one mistake to avoid. Reinforce that coding and fractions both depend on precision, order, and checking work carefully.