Computer Science Programming Design and Debugging: Assessment and Progress Guide

Assessment purpose and target

Assessment should determine how independently and consistently a learner can design, implement, test, document, and improve programs using appropriate structures. Use results for a defined instructional decision rather than as a permanent label. Computer science learning develops understanding of computing systems, networks, data, algorithms, programming, and impacts. Current standards also foreground security, AI, ethics, accessibility, human-centered design, and multiple specialty pathways.

Balanced evidence set

• Conversation: A brief explanation, conference, or response to a probing question.
• Observation: Notes about strategy, tool use, collaboration, persistence, safety, and independence during authentic work.
• Product: a working program with test cases and debugging log evaluated against transparent criteria.
• Transfer: A later task with changed details that requires the same underlying learning.

Four-level analytic rubric

1. Beginning: Identifies part of the task but needs substantial modeling to choose or explain an approach.
2. Developing: Completes familiar work with support; reasoning or transfer is partial.
3. Secure: Completes an appropriate new task accurately and independently, using evidence and explanation.
4. Extending: Compares alternatives, manages complexity or uncertainty, and transfers learning while justifying decisions.

Assessment task design

A learner reproduces a bug, forms a hypothesis, changes one factor, and records evidence from the test. Use this process as an expected method: start from requirements, plan data and control flow, implement small pieces, test systematically, and explain changes. Ensure the task actually samples the target and does not depend unnecessarily on unrelated reading load, cultural background, motor output, technology access, or speed.

Interpret errors carefully

Specifically check for randomly editing code until output changes without identifying the cause. Compare the response with process evidence before deciding what the learner knows. One score, online result, or polished group product cannot establish independent mastery.

Feedback and reporting

Report the target, evidence source, performance conditions, level of independence, observed strength, precise next step, and date for recheck. Avoid averaging unrelated skills into a score that hides the actionable pattern.

Reassessment rule

After instruction and meaningful practice, use a fresh but comparable task. Keep criteria stable, record support, and update the conclusion when newer evidence is stronger.

Computing, privacy, and ethics check

Use test data without unnecessary personal information and follow school technology rules. Learners should document inputs, outputs, assumptions, edge cases, failures, accessibility, and human impacts. AI-generated or copied code must be understood, tested, attributed when required, and never treated as automatically correct or safe.

Student reflection prompts

• What was the learning goal in your own words?
• Which decision or evidence most affected your work?
• Where did you revise your first approach, and why?
• How would you use Programming Design and Debugging in a different task?

Related Computer Science subject guides

Algorithms and Computational Thinking · Programming Design and Debugging · Data Collection Analysis and Visualization

Framework reference: 2026 CSTA PK–12 Computer Science Standards. This original Exams.fit guide is independent and does not reproduce the standards. It summarizes useful national learning directions; state, district, school, course, and teacher expectations may differ. Reviewed August 2, 2026.