Software Engineering › Key terms › Y12 SE Project › User interface (UI) design
User interface (UI) design
Diagram Y12 SE Project
Definition
Planning the screens and controls users interact with, so they are clear, consistent and accessible.
Example: Large buttons, clear labels, good contrast.
Found in: syllabus, sample exam and familiarisation guidelines, school notes, past SDD papers.
Where it is used in the test
Syllabus area: Y12 SE Project.
Question types it can appear in
- Drawing: Draw a UI (familiarisation Q9a)
- Short answer: Define, outline or explain it and tie it to the scenario.
- Multiple choice: Pick the option that matches the definition or example.
Where it has appeared in the paper
The Software Engineering Project (Part C). Part letters follow each paper’s own layout.
Related past questions
- Familiarisation Q9a (3 marks): Prototype and user interface design The Software Engineering Project (Part C) · 3 marks
These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.
Study links
- Flashcard: User interface (UI) design in The Software Engineering Project (Year 12) · study that set
- Memorise: Maintenance, version control, stubs and drivers, optimisation
- Notes: Part 3. Where this has been examined (see ../../question_bank.md) (The Software Engineering Project (Year 12))
- Notes: Part 3. Where this has been examined (see ../../question_bank.md) (Pseudocode, flowcharts and diagram rules)
How to use it in an answer
A model sentence
Diagram: “Planning the screens and controls users interact with, so they are clear, consistent and accessible.” Then apply it: Large buttons, clear labels, good contrast.
In a short answer, give the definition in your own words first, then tie it to the situation in the question. Do not copy the example above unless it fits the scenario.
Command words used with it
No linked question shows the command word for this term. Across the past drawing and short answer questions in this bank the words used most are: Explain, Outline, Describe, Compare, Classify, Analyse. Check the actual word in your question.
Technique for the question types
- Drawing: Use the online drawing tool: label every symbol and arrow, use the correct symbols from the specification, and add every required item.
- Short answer: One clear point per mark, use the stimulus and course terms, and answer the command word.
- Multiple choice: Read all four options, rule out wrong ones, pick one; no penalty for guessing so never leave blank.
What the marking guidelines and feedback say
Include labelled: title/heading, text boxes (username, password, confirm password, email), labels, password mask, submit/register button, cancel/clear, error message area, consistent colours/fonts, help text. (Checklist from UI design principles, not from the MG.)
Common mistakes
- Drawing questions (2025 HSC exam Q22): refine attributes into separate inherited classes; use appropriate class diagram symbols.
- Use the term exactly as the syllabus words it, then link it to the scenario in the question; the 2025 feedback repeatedly rewards using the stimulus.
- Answer the command word: outline gives main points only, explain gives a reason or cause, discuss gives both sides.
Related terms
Same group in the syllabus: Resource allocation · Presenting a solution · Version control · Strategies for difficulties · Prototype