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.
Internationalization (i18n) is the process of designing and building the software so it can be adapted to different languages and regions without redesign or re-engineering — it is a technical/architectural preparation done once, up front. Localization (l10n) is the subsequent process of actually adapting the internationalized software for a specific language/region (translated text, local conventions), typically repeated for each target locale.
To incorporate internationalization into the design: (1) externalize all user-facing text into resource files rather than hard-coding strings, so translation does not require touching the interface's logic or layout; (2) design flexible layouts that tolerate text expansion/contraction (French and German labels commonly run 30–50% longer than English) without truncating or overlapping controls — especially important on the drug-name/dose fields where truncation could itself become a safety issue; (3) use Unicode throughout so drug names and pharmacist-entered text in any supported language display correctly; (4) avoid encoding meaning in culture-specific icons, colours or gestures alone (e.g. a red/green pair for "unsafe/safe" should be paired with an icon or label, since colour meanings and colour-vision accessibility both vary); and (5) design number, date, time and unit formats to be locale-driven rather than fixed — critically, dosing units and decimal separators (comma vs. period) must be handled correctly, since a locale-format mismatch on a dose value is directly safety-relevant, not merely cosmetic.
Localization, layered on top, would then involve: professional translation of the externalized strings for each hospital's operating region/language (not machine translation alone, given the safety-critical vocabulary); local clinical/regulatory review of terminology (drug naming conventions can differ by jurisdiction); and adapting date/number/measurement-unit display to the local convention (e.g. metric units and Canadian date conventions for a Canadian hospital deployment) while keeping the underlying stored data format locale-independent so libraries remain portable across sites.
