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 — what heuristic evaluation is. Heuristic evaluation is a usability inspection method in which a small number of evaluators independently examine an interface and judge it against a published set of recognised usability principles ("heuristics," e.g. Nielsen's ten usability heuristics — visibility of system status, match between system and the real world, user control and freedom, consistency and standards, error prevention, recognition rather than recall, and so on), identifying and rating any violation they find — without needing to recruit or run sessions with real end users.
Part B — how to conduct one. (1) Recruit 3–5 evaluators — ideally with some usability/HCI expertise, since expert evaluators find substantially more and more severe problems than novices; (2) each evaluator independently walks through the existing EHR interface's key tasks (e.g. searching a patient chart, entering a diagnosis, scheduling an appointment) at least twice — once for overall flow, once focused on specific elements — noting every point where the interface violates a heuristic; (3) evaluators work independently to avoid one person's opinion biasing another's, then aggregate the individually found problems into one consolidated list, removing true duplicates; (4) each aggregated problem is rated for severity (e.g. cosmetic, minor, major, catastrophic) considering frequency, impact and persistence, so effort can be prioritised; (5) the consolidated, severity-ranked list is reported back to the design team, typically in a debriefing session that also lets evaluators discuss possible fixes.
Part C — benefits and limitations. Benefits: (1) it is fast and inexpensive compared to user testing — no participant recruitment, scheduling, or lab time is needed, so a heuristic evaluation of the current EHR interface could be completed in days rather than weeks; (2) it can be done very early, even on a rough prototype or paper sketch, and can catch a broad range of generic usability violations before any user testing budget is spent. Limitations: (1) it relies on evaluator judgement and expertise — without genuinely experienced evaluators, it both misses real problems and produces false positives, and even experts systematically miss issues that only emerge from real users' actual tasks and domain knowledge (a heuristic-only review of the EHR is unlikely to catch a problem specific to how clinical charting is actually done in practice); (2) because no real users are involved, it cannot validate whether the interface actually fits the real target users' mental models, vocabulary, and workflow — a design can pass heuristic review cleanly and still fail with real Happy Medical Clinic staff on a task the heuristics don't happen to cover.
