Evaluating a solution against constraints
Check if a solution stayed within its time, budget, device and skill limits, say if each was met or not met, and explain what trade-offs were made and how they affected its features.
Understanding Evaluating a solution against constraints in Years 7–8 Creating Digital Solutions
What it does: Removing a feature to save time is a trade-off made because of the time constraint. The device limit changed what the solution can do, so this shows the effect of a constraint on features. The constraint said school laptops. If the game does not work on them, the device constraint was not met. The skill constraint is about working within the skills you have. Using block coding fits that limit. Honest evaluation includes constraints that were not met. Explain what happened and what it affected.
Common mistakes: The solution spent 150, so a limit of 100 would mean the budget was not met. The result says met, so the limit should be 200. The time constraint is met when the time used is less than or equal to the limit. The test should use <=, not >=.
Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.
This module's key terms are also in a printable crossword (Modules 50–125) and word search (Modules 3–125).
Take this worksheet further — free with Cloodit
Each concept is reinforced from every angle — learned, then applied, then tested.
Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.
Over 100 of them, across seven natural biomes.
Turns their work into revision material ready for Flash Cards and Exam study.
Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.
Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.
Quick Questions
Match the Pairs
Key Term
evaluate against constraintsFill in the Blanks
Spot the Error
Student with a class code? Join your class →