All subjects · Information Technology · WIT14 3 hour practical exam on database solutions

User experience: how design affects the user

Edexcel IAL Information Technology · WIT14 3 hour practical exam on database solutions

Specification 17.3 links user characteristics to design choices and design choices to the experience users get. You must build solutions that give a suitable experience and evaluate them.

Practise this in the app: instant marking and a fix for every mistake. Free, no email needed to start.

Practise this lesson

Characteristics that shape the design

The spec lists five aspects of design that depend on who the users are:

How design affects the experience

Aspect of experienceGood designPoor design
Ease of useClear labels, logical tab order, one task per screenUnlabelled boxes, random order
EfficiencyDefaults, drop-downs, auto-generated IDs, buttons for frequent jobsRetyping the same data, many clicks
HelpInstructions on the form, help text in the status bar or tooltipsNo guidance; users guess
CompatibilityWorks in the version the users have; exports to formats they can openFeatures that fail on the users' system
StabilityErrors are trapped and explained; users cannot break the designCrashes or cryptic system messages
Accuracy of dataValidation, input masks, lookups, confirmation before savingFree typing everywhere

Building and evaluating for experience

When you build a form or menu in the exam, the mark scheme rewards features that improve the experience, for example a meaningful title, instructions, clear labels, required fields marked with an asterisk, fields that cannot be edited being disabled, a clearly labelled save button with a confirmation message. Pearson's examiner reports note that default wizard forms earn few marks.

To evaluate the experience, judge each aspect (ease of use, efficiency, help, compatibility, stability, accuracy) with evidence from your solution, then suggest a specific improvement for any weakness.

Worked example

Evaluate this design: a booking form opens with all 14 fields of three tables on one screen, field captions are the raw field names, and an Access system error appears if Days is 0.

  1. Complexity: too many fields at once for occasional users; split into a customer section and a hire section, or show only fields needed for a booking.
  2. Language: raw names such as CustomerID confuse users; use captions such as 'Customer'.
  3. Stability and help: the system error is unhelpful; add a validation rule with text such as 'Days must be 1 or more'.

Answer: Each criticism names the aspect of experience, the evidence and a specific fix.

Key idea: Interface type, appearance, complexity, language and compatibility should suit the users; good design gives ease of use, efficiency, help, compatibility, stability and accurate data. Evaluate each aspect with evidence and specific improvements.

Check yourself

  1. A user enters a negative quantity and sees a cryptic system error, then the form closes. Which aspect of user experience is poorest?
    • Compatibility, because the software version is wrong
    • Appearance, because the colours clash
    • Efficiency, because there are too many clicks
    • Stability, because errors are not trapped and explained
    Show answer

    Stability, because errors are not trapped and explained. Untrapped errors and crashes are a stability problem; a validation rule with a clear message fixes it.

  2. Which feature mainly improves efficiency?
    • The title is in a larger font
    • The date field defaults to today
    • The form has a company logo
    • Field labels are left aligned
    Show answer

    The date field defaults to today. Defaults remove a typing step every time a record is entered.

  3. A report is exported in a format the client's office software cannot open. Which aspect has been ignored?
    • Complexity
    • Language
    • Stability
    • Compatibility
    Show answer

    Compatibility. Outputs must be usable on the recipients' systems.

  4. Which form label is best for users at a hotel reception?
    • Guest's arrival date
    • dtArr
    • fld_ArrDt
    • ARRIVAL_DATE_FK
    Show answer

    Guest's arrival date. Plain language that matches the users' own words is easiest to understand.

  5. Which is an example of help built into a form?
    • A validation rule with no error message
    • A hidden field holding the record ID
    • Status bar text explaining what to enter when a field is selected
    • A primary key on the table
    Show answer

    Status bar text explaining what to enter when a field is selected. Help text guides users as they work.

  6. A data entry form lets users type any value for 'Membership type', which must be Gold, Silver or Bronze. Explain the effect on user experience and suggest an improvement.
    Show answer

    Users can make spelling mistakes, so data is inaccurate and searches miss records; a drop-down list of the three types would prevent this and be quicker.. Free typing harms data accuracy (and searching); a list, option group or list validation rule fixes it.

Practise with instant feedback

Sources

Last updated 8 November 2026. Spotted a mistake? Tell us.