19-Soft-B2 User Interface · May 2014
Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)
National Exams, May 2014 — 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 — Medic123's ambulatory smart infusion pump and its Windows drug-library upload software, designed by MedicSoft using a User-Centered Design (UCD) approach for hospital pharmacists. 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 triangulation means. Triangulation is the practice of studying the same question (a requirement, a usability problem, a user need) using two or more independent data-gathering methods or data sources, and cross-checking whether they converge on the same finding. The term is borrowed from navigation/surveying, where a position is fixed more reliably from two or more bearings than from one. In usability work, this might mean confirming a suspected pain point in drug-library editing through interviews with pharmacists, direct observation of them performing the task, and analysis of logged error/correction events from the software itself — rather than relying on any single one of those sources alone.
Part B — conditions for triangulation to work. As a group, the chosen methods must (1) have genuinely independent, non-overlapping weaknesses — each method's blind spots and biases should be different from the others' (e.g. interviews are prone to what people say they do rather than what they actually do; observation is prone to the observer effect changing behaviour; log data is prone to capturing what happened but not why) — so that a finding surviving across methods is unlikely to be an artefact of any one method's particular weakness. (2) They must examine the same underlying question or population closely enough that a convergent or divergent result is actually meaningful — triangulating with methods aimed at different questions or different user groups produces results that cannot legitimately be compared. (3) The methods must be applied rigorously enough individually that each one's own result is trustworthy on its own terms — triangulation cross-checks genuine, well-executed findings against each other; it cannot rescue a poorly designed individual study by combining it with others. When these conditions hold, agreement across methods substantially increases confidence in a finding, and disagreement is itself informative — it flags exactly where a single-method study would have produced a false, unchecked conclusion.
