23-Ind-B4 Design of Information Systems · December 2013
Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)
National Exams — December 2013 — 98-Ind-B4, Design of Information Systems. 3 hours; closed book, no calculator permitted. The exam comprises four parts: Part A (select 20 of 40 terms and explain each in a sentence or two, 2 marks each = 40 marks), Parts B and C (select 2 of 5 questions in each part, 11 marks each = 22 marks per part), and Part D (select 1 of 2 questions, 16 marks). Complete answers to every term and every question in all four parts follow below, not only the minimum selection a candidate would submit on exam day.
Reference texts: Laudon & Laudon, Management Information Systems: Managing the Digital Firm, 15th ed.; Schwalbe, Information Technology Project Management, 9th ed.
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.
From an individual's perspective, this is the personal question of what an organization is allowed to know about you, and what say you have over it: whether your browsing history, location, purchase pattern, or personal data (Question 1's terms 5 and 14 — behaviour monitoring, cookies) is collected, how it is used, and whether you can see, correct, or opt out of that collection. Where an organization's privacy policy (term 34) is weak or poorly enforced, an individual can be tracked, profiled, or have decisions made about them without their meaningful knowledge or consent.
From an individual's perspective this cuts both ways: as a consumer, it is the question of respecting the intellectual property of software, media, and digital content the individual uses (unlicensed copying, patent/copyright infringement); as a creator, it is the question of who owns content the individual generates or contributes on a platform (photos, posts, data), and whether the platform's terms of service adequately protect that individual's rights to their own work.
When an information system causes an individual harm — a wrong medical record, an erroneous credit decision, a security breach exposing personal data — this dimension asks who can personally be held responsible, and what recourse the affected individual actually has. For an individual user, the practical question is rarely abstract: can they identify who is accountable, and is there a real mechanism (regulatory complaint, legal action, corporate redress process) available to them, or does the complexity of the system let responsibility diffuse until no one is answerable.
Poor system quality — software bugs, inadequate testing, unvalidated data — translates directly into personal harm when the system in question manages an individual's finances, health record, or legal status: an erroneous entry can follow a person for years and be difficult to have corrected. From an individual's perspective, system quality is not an abstract engineering metric but the practical reliability of systems the person has no choice but to depend on and generally cannot audit themselves.
At a personal level, information systems have blurred the boundary between work and home life (always-connected devices extending the workday), created information overload that can degrade decision quality and wellbeing, driven deskilling or reskilling anxiety as automation changes what human labour a job actually requires, and created a digital divide in which unequal access to technology and connectivity translates into unequal access to opportunity, information, and services.
