Semester 4: Systems Programming: Rubric and Passing Standards
The World-Class Strand evidence is non-compensatory: every required category must pass even when the rest of the submission is strong.
This rubric applies to the semester-level checkpoint, exam, and project. Use it with the answer key and solution outlines to keep grading consistent and learner-visible.
Minimum Passing Standard
To pass Semester 4: Systems Programming, the learner must satisfy all of the following:
- Checkpoint: at least 80% of checkpoint prompts are answered correctly and independently, with no critical gaps in C, memory, representation, compilation, debugging, and OS-facing system behavior.
- Exam: overall score is at least 70%, and no major section that tests a core semester outcome is below 60%.
- Project: all required deliverables are present, the artifact can be inspected or reproduced by another person, and the learner can defend the main tradeoffs.
- Integrity: sources, collaboration, generated assistance, and borrowed code or examples are acknowledged.
- Remediation: any failed required gate remains incomplete until a written repair and fresh-case retest pass.
Failure in any one of these categories means the semester should not be marked complete yet, even if the other artifacts look strong.
Grading Rubric
| Dimension | Needs repair | Minimum pass | Strong pass | Excellent / portfolio-ready |
|---|---|---|---|---|
| Concept command | Uses terms loosely or confuses core ideas. | Defines and applies the required concepts with minor gaps. | Explains concepts through examples, counterexamples, and constraints. | Teaches the ideas clearly and connects them across semesters. |
| Reasoning quality | Jumps to answers; hides assumptions. | Shows enough steps to inspect correctness. | Makes assumptions, invariants, and tradeoffs explicit. | Compares alternatives and anticipates edge cases or objections. |
| Evidence | Claims are unsupported or impossible to reproduce. | Provides basic proofs, tests, diagrams, traces, or outputs. | Evidence targets the riskiest claims and is easy to verify. | Evidence is organized as a review packet a third party can audit. |
| Semester integration | Treats modules as unrelated topics. | Connects the main semester themes to the assessment. | Synthesizes multiple modules in one coherent explanation or artifact. | Shows how mastery of C, memory, representation, compilation, debugging, and OS-facing system behavior shapes engineering judgment beyond the course examples. |
| Communication | Hard to follow; missing context. | Understandable and complete enough to grade. | Clear structure, named decisions, and concise explanations. | Professional presentation with honest limitations and next steps. |
Strong Submission Traits
Strong submissions usually demonstrate these traits:
- concise explanations that reveal the mental model, not just the final answer
- concrete artifacts that can be run, checked, reviewed, or traced
- explicit handling of edge cases, constraints, and failure modes
- visible revision: mistakes were found, corrected, and documented
- appropriate connections between C, memory, representation, compilation, debugging, and OS-facing system behavior and prior semester foundations
Common Weak Submission Patterns
Watch for these patterns during self-review:
- vocabulary recognition without the ability to apply the idea to a new prompt
- impressive-looking diagrams, code, or prose with no verification evidence
- hidden dependencies on tutorials, solution videos, or AI-generated answers
- project scope that is too broad to inspect or too narrow to prove the required skill
- missing reflection about tradeoffs, limitations, or what would be done differently
Calibration Decision Guide
- Pass: all minimum standards are met and weak patterns are minor.
- Repair required — incomplete: a bounded repair and fresh-case retest must pass before moving to Semester 5.
- Repeat / revisit: a core concept, core deliverable, or integrity requirement is missing.
When uncertain, grade against evidence rather than effort. Time spent is useful context, but the semester is complete only when the learner can demonstrate the outcomes.
C input-contract evidence
Require all CI1–CI6 at level 2 or above. Reuse the line-reader lab packet in the existing project: capacity traces, consecutive-line behavior, injected errors, compiler/diagnostic output and a fresh-case defense. No aggregate score waives missing input-contract evidence. Preserve the distinction between bounded storage and bounded running time.
Memory ownership evidence
Require all MP1–MP6 at level 2 or above. Reuse the growable-buffer packet: checked sizing, ownership traces, allocation-failure recovery, cleanup and independent transfer. The 20–30-hour package replaces the former short lab; it is not a complete module workload. Required fuzzing/Rust/mitigation/platform work remains separate.
Performance evidence
Require PE1–PE6 at level 2 or above. Reuse the locality measurement packet: checked sums, raw timings, target assembly, model assumptions and a bounded inference. A speedup or fabricated anomaly is never required. The specialized-platform strand remains separate.
Partial-I/O evidence
Require IO1–IO6 at level 2 or above. Reuse the write-progress packet: exact accepted prefixes, bounded retry traces, descriptor ownership and diagnostic evidence. A complete local write does not imply durability or remote processing.
Lexical interpretation evidence
Require all LI1–LI6 at level 2 or above. Reuse the interpreter packet: frame diagrams, two independent closure instances, evaluation-order tests, caller-scope fault evidence and explicit host/resource limitations. The small evaluator does not replace the original mutation, streams, staging or concurrency requirements. A failed gate remains incomplete regardless of aggregate score.
Integrated progression contract
Use the 440–640-hour workload and advancement contract. All 30 module extension gates and all five safety/platform evidence categories must independently reach level 2, alongside existing checkpoint, exam, project and integrity thresholds. Missing evidence means repair required — incomplete. Reuse module artifacts and record time once; the three-hour written exam and two-hour fresh-case defense are included in integration time.