Self-Assessment Hub
The system’s one rule: attempt everything on the page before opening any answer. Every answer key here is hidden in a collapsible section (or a separate page, where the course’s unit quizzes live) precisely so a stray glance can’t destroy the self-test. Reading the key is the lesson — but only after your own attempt.
What’s in the system
| Collection | Count | Purpose | When to take it |
|---|---|---|---|
| Weekly quizzes | 16 × 10 questions | verify the week’s two sessions stuck | end of each study week |
| Topic revision tests | 8 × 12 questions | consolidate a topic that spans units | after finishing each topic cluster |
| Cumulative tests | 4 × 15 questions | prove earlier material still holds | Weeks 5, 10, 15, 16 |
| Practice finals | 2 × 25 questions | rehearse the complete course | Week 16 — exam conditions |
Total: 34 assessment instruments · 366 questions · every one with difficulty label, answer, and explanation.
The three question families
- Recognition (multiple choice, true/false) — fast, but the wrong options are real confusions students actually have, not filler.
- Prediction & tracing (output prediction, algorithm tracing, dry runs) — the executable-mental-model questions; the heart of the system.
- Diagnosis & construction (debugging, code reading, short programming) — you find the bug, name what a snippet does, or write 5–15 lines from a spec.
How to take any instrument
- Closed book first — no compiler, no notes, one sitting, 15–40 minutes depending on the instrument.
- Write answers down — paper or a file; “I knew that” doesn’t count.
- Open the key once, item by item, and for each miss write one sentence: what I confused it with. That sentence is the study plan.
- Score with the bands (below) and record the result in the checklist.
- Retake rule: a retake counts only after you’ve re-studied the flagged sections and slept on it. Same-day retakes measure memory, not learning.
Scoring bands (course-wide)
| Score | Verdict | Action |
|---|---|---|
| ≥ 90% | Ready | Move on; note any lucky guesses for the retake bank. |
| 70–89% | Almost | Re-study the sections your misses point to; retake after a day. |
| < 70% | Not yet | Redo the unit’s exercises and revision sheet; retake when fresh. |
Progress rule (unchanged from Assessment): a unit is complete when its lab works and its quiz is ≥ 90%.
The full progress checklist
Weekly quizzes — W01–W04 · W05–W08 · W09–W12 · W13–W16
- W01 ☐ (≥90) · W02 ☐ · W03 ☐ · W04 ☐ — weeklies-1
- W05 ☐ · W06 ☐ · W07 ☐ · W08 ☐ — weeklies-2
- W09 ☐ · W10 ☐ · W11 ☐ · W12 ☐ — weeklies-3
- W13 ☐ · W14 ☐ · W15 ☐ · W16 ☐ — weeklies-4
Topic revision tests — T1–T4 · T5–T8
- T1 Variables & Expressions ☐ · T2 Control Flow ☐ · T3 Functions ☐ · T4 Collections ☐ — topic-tests-1
- T5 Strings & Text ☐ · T6 Files & Persistence ☐ · T7 Memory & Pointers ☐ · T8 OOP & Design ☐ — topic-tests-2
Cumulative tests — CU1–CU2 · CU3–CU4
- CU1 (through loops) ☐ · CU2 (through collections) ☐ — cumulative-1
- CU3 (through memory) ☐ · CU4 (full course) ☐ — cumulative-2
Practice finals — Final A · Final B
- Final A ☐ (exam conditions, 90 min) · Final B ☐ (after A’s post-mortem)
Honesty line: this page trusts you with the keys because the system only works if you don’t peek. The person the checklist is for is you.
— Engr. Dr. Muhammad Nadeem Majeed, Professor, Department of Data Science (PUCIT), University of the Punjab, Lahore · About the instructor