Theory Notes/🗄️ Topic 4: Data & Information Management, Solution Development/11.4.12

11.4.12Grade 11

Good Design in User Interfaces (Programming Context)

Applying the UI principles from 10.4.12 specifically to the messages and behaviour of a coded program. Note: not examinable in the practical exam, but is examinable in theory.

Descriptive error messages — the message should indicate a solution, not just state that something went wrong, e.g. 'Please enter a number between 1 and 100' rather than just 'Invalid input'.
Appropriate prompts and error messages based on caught exceptions or the specific situation.
Appropriate use of metaphors/images — e.g. a printer icon on a print button, so the function is intuitively recognisable.
Consistent behaviour that makes use of long-term memory — e.g. always using F1 for Help, or ESC to cancel; there are de facto standards users already expect.
Uncluttered screens with effective, purposeful use of colour.
Effective use of components for data validation, e.g. drop-down boxes (limits choices to valid options) and calendar pickers (prevents invalid date formats).

💡 Exam Tip

Even though 11.4.12 is not examinable in the practical, it's fully examinable in the theory paper — expect a scenario asking you to critique or improve a described interface using these exact principles.