Appendix - Knowledge Check
What We Learned
- Recall concepts without notes, then explain the mechanism and trade-off behind each answer.
- Use module quizzes and Q&A banks to find weak areas and revisit the relevant chapter.
- Score all fourteen readiness domains from demonstrable evidence, rather than familiarity.
- Build independently to reach level 2; design, debug and justify choices to reach level 3.
- Keep project code, measurements and reports; rescore after tracks and capstones.
Key Acronyms, Concepts & Jargon
| Term | Short meaning |
|---|---|
| Active recall | Retrieve an answer from memory before checking the notes. |
| Q&A | Questions and Answers: prompts and explanations for review practice. |
| Readiness score | 0: cannot explain; 1: follow a tutorial; 2: build independently; 3: design and debug. |
| Core-domain threshold | The course target of no core readiness score below 2. |
| Trade-off | A choice that improves one property while costing another. |
| Evidence / baseline | Demonstrable work or measurements / reference used for comparison. |
| Regression | Loss of a previously working behavior or capability. |
| End-to-end project | A complete system with code, metrics, architecture and an explained outcome. |
| Capstone | An integrated project demonstrating skills across multiple course sections. |
| ADR / SLO / ROI | Architecture Decision Record / Service Level Objective / Return On Investment. |
| Eval | A repeatable procedure for measuring system behavior or task success. |