Anson Wong
Menu

Web Application Development for HKDSE ICT: what this elective actually covers

What this topic covers

Web Application Development is arguably the least understood of the three current electives before students actually start studying it, because “web development” as a general skill (which plenty of students have picked up informally, from tutorials or personal projects) and Web Application Development as an examined HKDSE elective are related but not identical. The exam cares about specific, examinable concepts—not about whether you can personally build and deploy a website.

Main areas

Client-side vs. server-side. What runs in the browser versus what runs on a server, and why that distinction determines what a web application can and can’t do—this framing recurs throughout the elective.

Structure, presentation, and behaviour. The conceptual separation between a page’s content/structure, its visual presentation, and its interactive behaviour—examined at the level of understanding why this separation is good design, not at the level of memorising syntax.

Web application design principles. Usability, accessibility, and basic user-interface considerations for a web application, examined through scenario-based questions about a described application’s design choices.

Data handling in web applications. How a web application typically collects, sends, and stores user data—connecting back to the Databases elective for students taking both, and to security concepts from the compulsory part.

How the ideas fit together

This elective sits at the intersection of Computer Systems Fundamentals (what’s actually running the application), Internet and its Applications (how the client and server communicate), and—for students who also take Databases—how a web application’s data is actually structured and stored. It rewards students who can reason about a system as a whole, not just one layer of it.

Common difficulties

Students who’ve done informal web development sometimes over-answer with implementation detail (specific syntax, specific tools) when the question is actually asking for a conceptual explanation, and under-answer the conceptual reasoning because they assume it’s “obvious.” The exam wants the underlying principle stated clearly, illustrated with the scenario given— not a demonstration of coding fluency.

What you should be able to do

  • Explain the client-side/server-side distinction using a concrete example from a described web application.
  • Identify structure, presentation, and behaviour as separate concerns in a described page, and explain why keeping them separate is good practice.
  • Evaluate a described web application’s design against basic usability and accessibility principles.
  • Explain, at a conceptual level, how a described web application would collect and handle user data.

Get in touch

HKDSE ICT Tutoring