A-Level Computer Science — Diagnostic Guide

Coverage Map

Topics Covered Through Integration Tests

Grading Rubric

PASS Criteria

• Correctly solve at least 2 out of 3 Unit Tests with complete working
• Correctly solve at least 2 out of 3 Integration Tests showing cross-topic reasoning
• Correct use of Big O notation, binary representations, and SQL syntax
• Code/pseudocode is logically correct and follows structured programming principles

PARTIAL Criteria

• Correctly solve 1—2 Unit Tests and 1 Integration Test
• Shows understanding of concepts but has errors in implementation or calculation
• Partially correct code with logical gaps or syntax issues
• Correct high-level approach but incorrect details (e.g., wrong subnet mask, off-by-one in binary search)

FAIL Indicators

• Cannot perform basic binary/hex conversions or two’s complement
• Confuses data structure operations (e.g., stack vs queue behaviour)
• Cannot analyse algorithm complexity (assigning wrong Big O class)
• Unable to write basic SQL queries or identify normal form violations
• Fundamental misunderstanding of FSM/Turing machine concepts

Prerequisite Chains

Fundamentals (number systems, binary, Boolean algebra)
  └── Data Structures (arrays, linked lists, trees, hash tables)
        ├── Algorithms (sorting, searching, graph algorithms, complexity)
        │     └── Theory of Computation (FSM, regular languages, decidability)
        └── Programming (OOP, SQL, data representation)
              └── Software Engineering (SDLC, testing)

Networks (TCP/IP, addressing, security)
  └── Web Technologies (HTTP, protocols)

Recommended order of diagnostic completion:

1. diag-fundamentals — foundational number systems and logic
2. diag-data-structures — requires binary understanding
3. diag-algorithms — requires data structure knowledge
4. diag-programming — requires algorithm and data structure understanding
5. diag-networks — largely independent
6. diag-theory-of-computation — builds on algorithms and programming

Timing Recommendations

Total recommended time: approximately 3.9 hours (spread across multiple sessions).

Full battery timing: Complete all 6 diagnostics over 3—4 sessions of 60—70 minutes each.

How to Use These Diagnostics

1. Complete each diagnostic without referring to notes or reference materials.
2. For programming questions, write pseudocode or actual code on paper first.
3. Check solutions immediately after each question to identify gaps.
4. If you score FAIL, review the corresponding source file before retrying.
5. Integration Tests are the strongest predictor of exam readiness — they test your ability to combine concepts from different topics, which is essential for A-Level exam questions that often span multiple areas of the specification.
6. Pay special attention to: binary arithmetic accuracy, Big O notation, SQL syntax, and FSM design — these are frequently tested and easy to lose marks on through small errors.

Summary

The key principles covered in this topic are linked in the sub-pages above. Focus on understanding the definitions, applying the formulas or frameworks, and evaluating strengths and limitations of each approach.

Worked Examples

Worked examples demonstrating the application of key concepts are covered in the detailed sub-pages linked above.

Common Pitfalls

• Confusing terminology or concepts that appear similar but have distinct meanings.
• Overlooking key assumptions or boundary conditions that limit applicability.