How are forms and GUI controls used to build a usable interface, and what HCI principles guide good design?
Forms and common GUI controls, their properties, events and methods, wiring controls to handlers, and the human-computer interaction principles of good interface design.
A CCEA A-Level Software Systems Development answer on forms and GUI controls: common controls and their properties, events and methods, wiring controls to handlers, and the human-computer interaction principles behind good interface design.
Reviewed by: AI editorial process; not yet individually human-reviewed
Have a quick question? Jump to the Q&A page
Jump to a section
What this dot point is asking
CCEA expects you to design and build an interface from forms and GUI controls, describing each control's properties (its data and appearance), events (what it can respond to) and methods (what it can do), and to wire controls to their handlers. You must also explain the principles of human-computer interaction (HCI) that make an interface usable. Questions ask you to choose controls for a task, name properties and events, and justify design choices.
The answer
Forms and controls
Common controls and a typical use:
- Button (command button): triggers an action; key event
Click. - Text box: single-line text entry/editing; key property
Text, eventTextChanged. - Label: displays fixed text or output (usually output-only).
- List box / combo box: offers a list of options to select from.
- Check box: an independent on/off option; radio (option) buttons offer a mutually exclusive choice in a group.
Properties, events and methods
A control is configured by its properties at design time (in a property window) or changed at run time in code (lblOut.Text = "Done"). It responds through its events, each linked to a handler. It is acted on through its methods (txtName.Clear()). Together these three make a control a small object with state (properties), behaviour the user triggers (events) and operations the program can call (methods), echoing the object oriented model from AS 1.
Human-computer interaction principles
Worked example: designing a simple login form
Examples in context
Example 1. An order form. A combo box lists products (so the user cannot mistype a name), a numeric text box takes the quantity, radio buttons choose delivery or collection (a single choice), a check box opts into a newsletter (independent), and a button submits. Feedback appears in a status label. The control choices prevent errors and reflect the nature of each input.
Example 2. A settings screen. Check boxes toggle independent options (dark mode, notifications), a slider sets volume, and grouped, consistently labelled sections make the screen easy to scan. Disabling options that do not apply (error prevention) and confirming saves (feedback) follow the HCI principles that make the screen usable.
Try this
Q1. Name a suitable control for entering a single line of text and state the property that holds its contents. [2 marks]
- Cue. A text box; its
Textproperty holds the contents.
Q2. Distinguish between a property and an event of a control. [2 marks]
- Cue. A property is data or appearance of the control (such as
TextorEnabled); an event is an occurrence the control can respond to (such asClick).
Q3. State one HCI principle and explain why it improves usability. [2 marks]
- Cue. For example consistency: controls and layout behave the same throughout, so a user who learns one screen can predict the others, reducing errors and learning time.
Exam-style practice questions
Practice questions written in the style of CCEA exam questions on this dot point, with worked answer explainers. The year tag is the paper they imitate, not the source.
CCEA 20186 marksDescribe three common GUI controls a developer might place on a form, stating a typical use, a key property and an event for each.Show worked answer →
Three common controls are a button, a text box and a label (a list box, combo box or check box would also be acceptable).
A button (command button) is used to trigger an action such as submitting a form. A key property is its Text (the caption shown), and a key event is Click, which runs when the user presses it.
A text box is used to let the user enter or edit a line of text, such as a name. A key property is its Text (the contents typed), and a useful event is TextChanged, which runs each time the contents change.
A label is used to display fixed or output text, such as a prompt or a result. A key property is its Text (the displayed string); labels are usually output-only and have no commonly handled event, though they support Click.
Markers reward three valid controls, a sensible use, a correct property and an appropriate event for each (with the property and use clearly matched to the control).
CCEA 20215 marksExplain three principles of good human-computer interface design and why each matters.Show worked answer →
Good interface design follows usability principles. Three examples:
Consistency means controls, colours, fonts and layouts behave the same way throughout the application, so once a user learns one screen they can predict the others. This reduces errors and the time needed to learn the system.
Clear feedback means the interface tells the user what is happening, for example highlighting a clicked button, showing a progress bar, or displaying a confirmation or error message. Without feedback the user does not know whether an action succeeded.
Intuitive, logical layout (with clear navigation) means related controls are grouped, the reading order is natural, and the most common actions are easy to find. This lets users complete tasks quickly with less confusion. Other valid principles include using clear and meaningful labels, preventing errors (for example disabling invalid options), accessibility (readable fonts and colour contrast), and keeping the interface simple and uncluttered.
Markers reward three distinct, genuine HCI principles, each with a correct explanation of why it improves usability.
Related dot points
- The event driven paradigm - events, event handlers, the event loop, event-driven versus procedural programming, and the roles of the operating system and the program.
A CCEA A-Level Software Systems Development answer on the event driven paradigm: what events and event handlers are, how the event loop dispatches them, and how event-driven programming differs from procedural programming.
- Storing application data in arrays, lists and records, and the standard algorithms - linear search, binary search and a simple sort such as bubble sort.
A CCEA A-Level Software Systems Development answer on storing application data in arrays, lists and records, and the standard algorithms: linear search, binary search and a simple sort such as bubble sort, with their requirements and trade-offs.
- Reading from and writing to text and sequential files - opening, reading, writing, appending and closing files, processing records, and handling file errors.
A CCEA A-Level Software Systems Development answer on file handling: opening, reading, writing, appending and closing text and sequential files so data persists between runs, processing records line by line, and handling file errors.
- Testing strategies for applications, debugging tools (breakpoints, stepping, watches), exception handling with try and catch, and producing robust software.
A CCEA A-Level Software Systems Development answer on testing and debugging event driven applications: test strategies, debugging tools such as breakpoints, stepping and watches, and exception handling with try and catch for robust software.
Sources & how we know this
- CCEA GCE Software Systems Development specification — CCEA (2016)