Semester 5: OS and Networking: 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 5: OS and Networking, 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 processes, concurrency, filesystems, sockets, protocols, and operational systems reasoning.
- 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: every failed required gate is repaired and independently retested before completion.
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 processes, concurrency, filesystems, sockets, protocols, and operational systems reasoning 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 processes, concurrency, filesystems, sockets, protocols, and operational systems reasoning 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: any required gate is below passing; complete the repair and independent retest before Semester 6.
- 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.
Scheduling-contract evidence
Require every PS1–PS6 gate at level 2 or above. Reuse the simulator packet: event-order predictions, independent metrics, queue-policy fault evidence and a bounded quantum/cost comparison. A simulator result does not establish host scheduler behavior. Failed gates remain incomplete regardless of aggregate score. See the reconciled workload and progression contract.
Translation-contract evidence
Require every VM1–VM6 gate at level 2 or above. Reuse address traces, permission/fault cases, ASID separation, remap/invalidation tests and counter reconciliation. A TLB hit does not guarantee authorized access, and a miss does not imply storage I/O. Failed gates remain incomplete regardless of aggregate score.
Queue-concurrency evidence
Require every CQ1–CQ6 gate at level 2 or above. Reuse protected-state reasoning, controlled wait/close traces, fault/repair evidence and the independent shutdown case. Sequential model histories and sampled thread tests do not prove every interleaving or fairness. Failed gates remain incomplete regardless of aggregate score.
Crash-recovery evidence
Require every FS1–FS6 gate at level 2 or above. Reuse the crash matrix, persisted-prefix cases, early-success counterexample and repeatable replay evidence. Model results do not certify real device durability. Failed gates remain incomplete regardless of aggregate score.
Stream-framing evidence
Require every NW1–NW6 gate at level 2 or above. Reuse fragmentation/EOF traces, early size rejection, terminal-error policy, simulated deadlines and the bounded socket-adapter design. Decoder tests do not establish real network timing or exactly-once business effects. Failed gates remain incomplete regardless of aggregate score.
Semester completion contract
Use the 468–676-hour workload and progression contract and the five separately scored security-strand categories S1–S5. All 34 module gates (including PC1–PC4) and all five strand categories must reach level 2; aggregate marks cannot replace missing evidence. Reuse artifacts and record time once. Independent review and workload pilots remain pending.
Native parallel-work evidence
Require PC1–PC4 at level 2 alongside existing gates. Reuse the native histogram packet during semester review; do not add parallel execution to the service without a workload justification. Clinic time is included in the revised 468–676-hour semester estimate.