19-Soft-B2 User Interface · May 2015
Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)
National Exams, May 2015 — 04-Soft-B2, User Interface (closed book, 3 hours). Part A: answer any FIVE of the NINE questions (10 marks each); Part B: answer ALL FIVE questions (10 marks each), all based on the same case study — Happy Medical Clinic, a Toronto medical clinic switching from paper-based practice to an electronic health record (EHR) system purchased from VisualEHR Inc., an off-the-shelf vendor willing to customize the product to the clinic's needs. Most questions call for essay-format answers; clarity and organisation count. This solution answers all fourteen questions as a full study resource.
Reference texts. Rogers, Sharp & Preece, Interaction Design: Beyond Human-Computer Interaction, 5th ed., Ch. 1–3 (interaction design, cognitive aspects, mental models), Ch. 9–10 (prototyping, personas), Ch. 11–12 (data gathering, requirements), Ch. 15–16 (evaluation, lab vs. field studies); Nielsen, Usability Engineering, Ch. 4–6 (usability heuristics, iterative design, usability testing); Shneiderman, Designing the User Interface, 6th ed., Ch. 2 (guidelines, principles), Ch. 12 (internationalization); Norman, The Design of Everyday Things, Ch. 1–4 (visibility, affordances, feedback, conceptual models).
Question text not reproduced: the examination questions are © Engineers and Geoscientists BC. Open the official past paper (linked at the top of this page) to read the question, then follow the worked solution below.
Part A — interface metaphor, with an example. An interface metaphor is a design device that presents a new, unfamiliar system in terms of a familiar real-world (or already-familiar digital) concept, so users transfer their existing knowledge of that concept to predict how the new interface behaves. Example: a patient's EHR chart presented as a "folder/tab" metaphor — a virtual folder for each patient, with labelled tabs for "Medications," "Lab Results," "Visit History" — letting clinic staff reuse their familiarity with organising a physical paper chart into labelled sections.
Part B — pros, cons, and the relationship to mental models and information processing. A metaphor works by deliberately priming the user to import an existing, familiar mental model (of the metaphor's real-world source, e.g. a physical patient folder) as the starting point for the mental model they build of the new digital system — it is a direct mechanism for shaping mental-model formation. It also shapes information processing at the point of encoding: because the metaphor's visual elements (folder, tabs) resemble a category the user's long-term memory already has a place for, recognizing and interpreting the interface's structure requires less new perceptual and cognitive processing than an entirely novel, unfamiliar layout would.
Pros: reduces learning time by leveraging prior knowledge (staff already understand "tabs" divide a chart into sections); makes system behaviour more predictable when the metaphor genuinely matches the underlying functionality (clicking a tab reveals that section, exactly as flipping to a labelled divider would in a paper chart); and gives designers and users a shared, immediately understood vocabulary. Cons: a metaphor that only partially matches the real behaviour actively misleads users once they push past the surface analogy — e.g. a "folder" suggests one exclusive location for a document, which may not reflect that the same lab result is actually shared and visible across multiple views in the underlying database; metaphors can constrain the design to the limits of the source domain (a physical-folder metaphor has no natural analogue for a full-text search across every patient's chart, a capability the digital system can and should offer); and metaphors that feel intuitive to the designer's own culture or generation may be unfamiliar or actively confusing to some users, undermining the very mental-model transfer the metaphor was meant to provide.
