Rubric: Practical Task A - Two-button controller

Wilteq Arduino Self-Study - Lesson 31 | Practical Assessment Criteria Grid

Learner: ________________________ Assessor: ________________________ Date: __________

Outcomes assessed by this grid

Interpret the brief into IPO, pin plan and success criteria before wiring
Implement debounced digital inputs on both buttons
Produce three distinct output states that match a truth table
Report state changes on Serial without flooding
Build safely with correct LED limiting and workmanship
Submit diagram, BOM, test evidence, fault reflection and explanation

Practical Assessment Criteria Grid

For each criterion, tick or circle one level only: Excellent, Proficient, Basic, or Poor. There is no separate score column.

Criteria	Excellent	Proficient	Basic	Poor
Brief interpretation & success criteria	Thorough criteria written before build, covering states, debounce, Serial and safety; used to judge the demo.	Clear criteria covering most brief requirements before or during the build.	General criteria only; some brief requirements missing.	Minimal or unclear criteria; demo cannot be judged against the brief.
Concept & design (IPO / block diagram)	Distinct useful purpose with complete IPO/block diagram and deliberate state design.	Useful controller concept with an adequate IPO and predictable design.	Basic idea with a thin or incomplete block diagram.	No clear application, or a direct lesson copy with no planning artefacts.
Truth table & pin planning	Complete truth table for three states and labelled pin table matching the sketch exactly.	Truth table and pin table present and mostly accurate.	Partial truth table or pin table with gaps or small mismatches.	Missing tables, or tables contradict the build.
Code structure & naming	Named pins/constants, clear state logic, useful comments; easy to follow.	Functional, structured code with adequate naming; comments present.	Works but sparse comments and unclear names.	Does not compile, chaotic, or dominated by unused boilerplate.
Debounce implementation	Reliable millis (or equivalent) debounce on both buttons; no chatter in demo or Serial.	Solid debounce on both buttons; rare edge noise only.	Debounce attempted; occasional double events remain.	No debounce; clear chatter on outputs or Serial.
Three-state behaviour vs truth table	All three states match the truth table in a live demo, including edge combinations.	All three states work and largely match the table.	Three states mostly work; one combination or PWM detail wrong.	Fewer than three states, or behaviour does not match the table.
Serial state reporting	Clear message on each state change only; baud documented; no flood while held.	Useful state-change messages with little noise.	Serial prints something useful but noisy or incomplete.	No Serial output, or continuous flood while held.
Physical hardware layout	Neat, colour-coded, inspectable layout; LED resistors correct; easy to audit.	Secure, safe layout; generally tidy and traceable.	Secure enough and safe, but cluttered and hard to trace.	Loose wiring, missing LED resistors, or short-circuit risk.
Circuit diagram / schematic	Accurate diagram matching the build: pins, INPUT_PULLUP to GND, LED resistors.	Clear diagram that matches the build with minor labelling gaps.	Diagram present but messy, missing pins, or weak symbols.	Missing diagram, or it does not match the hardware.
I/O integration (buttons + outputs)	Flawless real-time integration of both buttons with LED/PWM outputs.	Reliable button-to-output integration across required states.	Basic press-to-output works; one advanced path fails.	Inputs and outputs fail to work together.
BOM & component safety	Detailed BOM with resistor values and explicit safety notes.	BOM with key values; safety measures clear.	BOM without ratings; basic safety only.	No BOM; LED current limiting ignored.
Test evidence table	Complete table: conditions, expected, observed, pass/fail for idle, A, B and required combinations.	Solid test table covering the main cases with pass/fail.	Partial table missing columns or some required cases.	No test table, or only anecdotal claims.
Resolved challenges list	Deep debug journal (bounce, pinMode, Serial flood, state logic) with method and fix.	Clear faults documented with sensible troubleshooting steps.	Simple faults noted with minimal method.	Omitted, or claims fault-free with no debugging.
Unresolved challenges & explanation	Honest remaining limits plus clear explanation of debounce and state logic.	Some limits named; good explanation of how the controller works.	Thin reflection; explanation incomplete.	No reflection and cannot explain the design.

Criteria

Excellent

Proficient

Basic

Poor

Brief interpretation & success criteria

Thorough criteria written before build, covering states, debounce, Serial and safety; used to judge the demo.

Clear criteria covering most brief requirements before or during the build.

General criteria only; some brief requirements missing.

Minimal or unclear criteria; demo cannot be judged against the brief.

Concept & design (IPO / block diagram)

Distinct useful purpose with complete IPO/block diagram and deliberate state design.

Useful controller concept with an adequate IPO and predictable design.

Basic idea with a thin or incomplete block diagram.

No clear application, or a direct lesson copy with no planning artefacts.

Truth table & pin planning

Complete truth table for three states and labelled pin table matching the sketch exactly.

Truth table and pin table present and mostly accurate.

Partial truth table or pin table with gaps or small mismatches.

Missing tables, or tables contradict the build.

Code structure & naming

Named pins/constants, clear state logic, useful comments; easy to follow.

Functional, structured code with adequate naming; comments present.

Works but sparse comments and unclear names.

Does not compile, chaotic, or dominated by unused boilerplate.

Debounce implementation

Reliable millis (or equivalent) debounce on both buttons; no chatter in demo or Serial.

Solid debounce on both buttons; rare edge noise only.

Debounce attempted; occasional double events remain.

No debounce; clear chatter on outputs or Serial.

Three-state behaviour vs truth table

All three states match the truth table in a live demo, including edge combinations.

All three states work and largely match the table.

Three states mostly work; one combination or PWM detail wrong.

Fewer than three states, or behaviour does not match the table.

Serial state reporting

Clear message on each state change only; baud documented; no flood while held.

Useful state-change messages with little noise.

Serial prints something useful but noisy or incomplete.

No Serial output, or continuous flood while held.

Physical hardware layout

Neat, colour-coded, inspectable layout; LED resistors correct; easy to audit.

Secure, safe layout; generally tidy and traceable.

Secure enough and safe, but cluttered and hard to trace.

Loose wiring, missing LED resistors, or short-circuit risk.

Circuit diagram / schematic

Accurate diagram matching the build: pins, INPUT_PULLUP to GND, LED resistors.

Clear diagram that matches the build with minor labelling gaps.

Diagram present but messy, missing pins, or weak symbols.

Missing diagram, or it does not match the hardware.

I/O integration (buttons + outputs)

Flawless real-time integration of both buttons with LED/PWM outputs.

Reliable button-to-output integration across required states.

Basic press-to-output works; one advanced path fails.

Inputs and outputs fail to work together.

BOM & component safety

Detailed BOM with resistor values and explicit safety notes.

BOM with key values; safety measures clear.

BOM without ratings; basic safety only.

No BOM; LED current limiting ignored.

Test evidence table

Complete table: conditions, expected, observed, pass/fail for idle, A, B and required combinations.

Solid test table covering the main cases with pass/fail.

Partial table missing columns or some required cases.

No test table, or only anecdotal claims.

Resolved challenges list

Deep debug journal (bounce, pinMode, Serial flood, state logic) with method and fix.

Clear faults documented with sensible troubleshooting steps.

Simple faults noted with minimal method.

Omitted, or claims fault-free with no debugging.

Unresolved challenges & explanation

Honest remaining limits plus clear explanation of debounce and state logic.

Some limits named; good explanation of how the controller works.

Thin reflection; explanation incomplete.

No reflection and cannot explain the design.

Levels awarded: Excellent __ / 14 | Proficient __ | Basic __ | Poor __ Overall result: ________________

Evidence the learner must submit

Success criteria and IPO/block diagram
Truth table and pin table
Labelled wiring diagram or photo
Sketch / .ino
Serial excerpt of state changes
Completed test table
Resolved and unresolved challenges notes

Assessor guidance

Tick one level per row. Missing debounce cannot be Excellent for Debounce or Serial reporting. Unsafe LED wiring without a series resistor keeps Physical hardware and BOM at Basic or Poor.

Sign-off

Assessor signature

Learner signature

Result

Pass / Resubmit / Distinction (circle) Resubmit by: __________