Skip to content
Wyatt's Notes — DSE

DSE ICT -- Diagnostic Guide

DSE ICT — Diagnostic Guide

Coverage Map

Core Systems

Diagnostic FileTopics CoveredSource File
diag-./2-computer-systems/1_computer-systemsCPU architecture, memory hierarchy, I/O devices, Von Neumann model, fetch-decode-execute cycle./2-computer-systems/1_computer-systems
diag-data-representation.mdBinary/hex conversion, two”s complement, character encoding, image/audio representation, compressiondata-representation.md
diag-internet-data-communications.mdOSI model, TCP/IP, network topologies, protocols, bandwidth, error detection./4-networking-and-internet/1_internet-and-data-communications

Applications and Security

Diagnostic FileTopics CoveredSource File
diag-programming-databases.mdAlgorithm design, pseudocode, SQL queries, database normalisation, testing methods./3-programming-and-databases/2_programming-and-databases
diag-network-security-social-implications.mdMalware, encryption, data protection, legal/ethical issues, privacy, cyber lawnetwork-security-and-social-implications.md
diag-office-automation.mdSpreadsheet formulas, data analysis, document formatting, mail merge, collaborative tools./5-office-automation/1_office-automation
diag-web-multimedia.mdHTML/CSS, web design principles, multimedia formats, web security, responsive designweb-development-and-multimedia.md

Grading Rubric

PASS Criteria

  • Correctly solve at least 2 out of 3 Unit Tests with full working
  • Correctly solve at least 2 out of 3 Integration Tests demonstrating cross-topic understanding
  • Correct use of technical terminology (OSI layers, normalisation forms, encryption types)
  • Accurate calculations for binary conversion, file sizes, and network performance

PARTIAL Criteria

  • Correctly solve 1—2 Unit Tests and 1 Integration Test
  • Shows understanding of concepts but makes errors in calculations or pseudocode
  • Partially correct SQL queries or pseudocode with minor syntax errors
  • Can describe concepts qualitatively but struggles with technical application

FAIL Indicators

  • Cannot convert between binary, decimal, and hexadecimal correctly
  • Cannot identify OSI layers for common protocols
  • Cannot write basic SQL queries (SELECT, JOIN, WHERE)
  • Confuses symmetric and asymmetric encryption
  • Cannot distinguish between different normalisation forms

Prerequisite Chains

Computer Systems (hardware, CPU, memory)
  ├── Data Representation (number systems, encoding)
  │     └── Internet and Data Communications (protocols, transmission)
  └── Programming and Databases (algorithms, SQL)


Data Representation (binary, encoding)
  ├── Internet and Data Communications (error detection, bandwidth)
  └── Web Development and Multimedia (file formats, compression)


Internet and Data Communications (networking)
  └── Network Security and Social Implications (security, encryption)


Programming and Databases (logic, data management)
  └── Office Automation (spreadsheet formulas, data analysis)

Recommended order of diagnostic completion:

  1. diag-computer-systems — hardware foundations
  2. diag-data-representation — essential number system skills
  3. diag-internet-data-communications — networking fundamentals
  4. diag-programming-databases — algorithmic thinking and SQL
  5. diag-network-security-social-implications — builds on networking knowledge
  6. diag-office-automation — practical application of data skills
  7. diag-web-multimedia — integrates data representation, networking, and security

Timing Recommendations

DiagnosticRecommended TimeNotes
diag-computer-systems30 minutesMix of conceptual and calculation questions
diag-data-representation35 minutesBinary conversions and file size calculations
diag-internet-data-communications35 minutesOSI model recall and network calculations
diag-programming-databases40 minutesPseudocode writing and SQL queries
diag-network-security-social-implications30 minutesConceptual questions with some calculation
diag-office-automation25 minutesSpreadsheet formulas and practical scenarios
diag-web-multimedia35 minutesHTML/CSS, file format analysis, security

Total recommended time: approximately 3.5 hours (spread across 2—3 sessions).

How to Use These Diagnostics

  1. Complete each diagnostic without notes or reference materials.
  2. For programming questions, write out pseudocode or SQL on paper first before checking solutions.
  3. For calculations (binary conversion, file sizes, bandwidth), show all working.
  4. Check solutions immediately, focusing on both the approach and the final answer.
  5. If you score FAIL, review the corresponding source file before retrying.
  6. Integration Tests frequently combine concepts from multiple topics — these are especially valuable for DSE exam preparation.
  7. Practice writing SQL queries and pseudocode by hand, as the DSE exam requires written responses.

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.