CCEA A-Level Software Systems Development AS 2 Event Driven Programming: a complete overview of GUIs, files, data structures and robust applications

What this unit demands

AS 2 Event Driven Programming takes the object oriented foundation of AS 1 and uses it to build an interactive, graphical application. It introduces the event driven model (the program reacts to the user rather than following a fixed script), the controls that make up an interface, the files that let data persist, the data structures and algorithms that organise and search that data, and the testing, debugging and exception handling that make the result robust. The examiners test conceptual understanding (the paradigm, HCI, algorithms) alongside the ability to read, trace and write program fragments.

This guide walks through the five dot points of the unit, then sets out the exam patterns CCEA repeats. Each topic has a matching dot-point page with practice questions; this overview ties them together.

The event driven paradigm

An event is an occurrence such as a click, key press or timer tick; an event handler is code wired to respond to a particular event; and the event loop continuously waits for events and dispatches each to its handler. This differs from procedural programming in who controls the flow: procedural code follows a fixed sequence the program drives, whereas event driven code reacts to the user, who chooses what to do and when. This model suits graphical user interfaces.

Forms, controls and HCI

A form is a window hosting controls (buttons, text boxes, labels, list and combo boxes, check boxes, radio buttons). Each control has properties (data and appearance), events (occurrences it responds to) and methods (actions it performs), and events are wired to handlers. Good human-computer interaction (HCI) design follows usability principles: consistency, clear feedback, intuitive layout and navigation, meaningful labels, error prevention, accessibility and simplicity.

Files and data structures

Files give persistence: data survives between runs. The operations are open, read, write, append and close, with read mode controlled by an end-of-file test, write mode overwriting, and append mode preserving existing contents. Application data is held in arrays, lists and records (a record groups related fields of mixed types; an array of records stores many). The standard algorithms are linear search (any list), binary search (sorted lists only, halving the range) and a simple sort such as bubble sort (compare adjacent pairs, pass until no swaps).

Testing, debugging and robustness

Testing runs the program against planned normal, boundary and erroneous data in a test plan, using unit, integration and system testing. Debugging tools in an IDE - breakpoints, stepping, watches, the call stack - locate a fault. Exception handling with try ... catch detects run-time errors so the program stays robust and does not crash, complementing (not replacing) input validation.

How this unit is examined

A typical CCEA profile for AS 2:

• Concepts. Defining the event driven model and contrasting it with procedural programming.
• Interface design. Choosing controls, naming properties and events, and applying HCI principles.
• File handling and algorithms. Writing or tracing file read/write/append code and the standard search and sort algorithms.
• Robustness. Describing debugging tools and exception handling.

Check your knowledge

A mix of recall and tracing questions covering the unit. Attempt them under timed conditions, then check against the solutions.

1. Define the terms event and event handler. (2 marks)
2. State the key difference between event driven and procedural programming. (1 mark)
3. Name a control suitable for a single choice from several options and one for an independent on/off option. (2 marks)
4. State what happens to a file's existing contents when it is opened for writing, and when opened for appending. (2 marks)
5. State one requirement of a binary search that a linear search does not have. (1 mark)
6. State the condition that tells a bubble sort the list is fully sorted. (1 mark)
7. Name one IDE debugging tool. (1 mark)
8. State what the try block and the catch block are each responsible for. (2 marks)