Case Study Practice for SQA Advanced Higher Computing | SQA 高级计算机案例分析实战演练

📚 Case Study Practice for SQA Advanced Higher Computing | SQA 高级计算机案例分析实战演练

Mastering the case study approach is essential for success in the SQA Advanced Higher Computing question paper. This article walks you through a realistic scenario — the automated management of a public library — demonstrating how to apply your knowledge of software development, database design, networking, and legal considerations in a structured manner. By practising these techniques, you will sharpen your analytical skills and learn to produce concise, well-justified answers under exam conditions.

掌握案例分析方法是 SQA 高级计算机考试成功的关键。本文通过一个真实场景——公共图书馆自动化管理系统，带你逐步演练如何将软件开发、数据库设计、网络技术和法律考量等知识以结构化的方式应用到答题中。通过练习这些技巧，你将提升分析能力，并学会在考试条件下给出简洁、有据的答案。

1. Understanding the Scenario | 理解案例场景

Every case study begins with a narrative description of an existing system or a proposal for a new one. Read the scenario carefully, highlighting key nouns (entities, users, hardware) and verbs (actions, processes). In our library case, a city council wants to replace a paper-based system with a digital platform that allows members to search the catalogue online, reserve books, and renew loans. Staff need to manage inventory, handle overdue notices, and generate statistical reports. External book suppliers must be able to view stock level requests electronically. Identify all stakeholders — members, librarians, system administrators, suppliers — and note the core goal: improving user experience while reducing manual workload.

每个案例都以对现有系统或新系统提议的叙述性描述开始。仔细阅读场景，圈出关键名词（实体、用户、硬件）和动词（动作、流程）。在我们的图书馆案例中，市议会希望用一个数字平台取代纸质系统，该平台允许会员在线搜索目录、预约书籍和续借。工作人员需要管理库存、处理逾期通知并生成统计报告。外部图书供应商必须能电子化查看库存需求。识别所有利益相关者——会员、图书管理员、系统管理员、供应商——并记下核心目标：改善用户体验，同时减少人工工作量。

2. Identifying Functional Requirements | 识别功能需求

Functional requirements describe what the system must do. List them in user-story format, for example: ‘As a member, I want to search books by title or author so that I can quickly find items of interest.’ For the library system, key functions include: member registration and login, catalogue search with filters, book reservation with queue management, loan renewal with validation against existing holds, staff dashboard for check-in/check-out, overdue fine calculation, inventory entry, and report generation. Don’t forget non-member interactions — the suppliers’ order request interface — and administrative functions like data backup scheduling. Prioritise these requirements using MoSCoW (Must have, Should have, Could have, Won’t have) to demonstrate structured thinking in your answers.

功能需求描述系统必须做什么。用用户故事格式列出，例如：“作为会员，我想按书名或作者搜索图书，以便快速找到感兴趣的物品。”对于图书馆系统，关键功能包括：会员注册与登录、带筛选器的目录搜索、带队列管理的图书预约、根据是否存在预约验证的续借、工作人员签入/签出仪表盘、逾期罚款计算、库存录入和报告生成。不要忘记非会员交互——供应商的订单请求界面——以及管理功能，如数据备份调度。使用 MoSCoW 方法（必须有、应该有、可以有、不会有）对这些需求进行优先级排序，以在答案中展现结构化思维。

3. Data Modelling and Database Design | 数据建模与数据库设计

Translate the scenario into an entity-relationship diagram (ERD) with at least four entities: Member, Book, Loan, Reservation, Staff, Supplier, Fine. Define attributes and primary keys. For example, Member (memberID, name, email, joinDate, status); Book (ISBN, title, author, publisher, year, genre, copiesTotal, copiesAvailable). Relationships: Member borrows Loan (1 to many); Book appears in Loan (1 to many); Member places Reservation (1 to many) linked to Book. Use Crow’s Foot notation to show cardinality. Then normalise to Third Normal Form (3NF): split repeating groups into separate tables (e.g., Author table to avoid redundancy) and ensure all non-key attributes depend on the whole primary key. A well-normalised design reduces update anomalies and maintains data integrity. In your exam answer, a simple table representation is acceptable, showing sample attribute lists and foreign key references.

将场景转化为实体关系图（ERD），至少包含四个实体：会员、图书、借阅、预约、员工、供应商、罚款。定义属性和主键。例如，会员（memberID, 姓名, 电子邮箱, 注册日期, 状态）；图书（ISBN, 书名, 作者, 出版社, 出版年份, 类别, 总副本数, 可用副本数）。关系：会员借阅借阅记录（一对多）；图书出现在借阅中（一对多）；会员预约关联图书（一对多）。使用鱼尾纹符号表示基数。然后规范化到第三范式（3NF）：将重复组拆分为单独的表（例如，作者表以避免冗余），并确保所有非键属性都依赖于完整主键。良好规范化的设计可减少更新异常并维护数据完整性。在考试答案中，用简单的表格表示法列出属性示例和外键引用即可。

4. User Interface Design Considerations | 用户界面设计要点

The interface must be accessible and task-efficient. For a web-based library system, propose a responsive design with three dashboards: Member Portal, Staff Console, and Admin Panel. Follow Nielsen’s heuristics: visibility of system status (e.g., showing remaining loan days), match between system and real world (book cover thumbnails), user control (filters that can be easily reset). Use wireframes to sketch layout: consistent navigation bar at top, search box prominent on the home page, colour contrast compliant with WCAG 2.1 AA. Consider input validation — date pickers for loan periods, dropdowns for genres — and clear error messages such as ‘Your reservation could not be completed because all copies are currently on loan’. Include accessibility features: alt text for images, keyboard navigation, and screen reader compatibility. Mention the trade-off between simplicity and functionality: avoid feature overload by grouping advanced options under ‘More filters’.

界面必须易于访问且高效。对于基于网络的图书馆系统，提出响应式设计，包含三个仪表盘：会员门户、员工控制台和管理面板。遵循尼尔森启发式原则：系统状态可见性（如显示剩余借阅天数）、系统与现实世界匹配（图书封面缩略图）、用户控制（可轻松重置的筛选器）。使用线框图勾勒布局：顶部一致的导航栏，主页醒目的搜索框，色彩对比度符合 WCAG 2.1 AA 标准。考虑输入验证——借阅期限使用日期选择器、类型下拉菜单——以及清晰的错误消息，如“因所有副本均在借阅中，您的预约未能完成”。纳入无障碍功能：图片替代文本、键盘导航和屏幕阅读器兼容性。提及简单性与功能性的权衡：通过将高级选项归入“更多筛选器”来避免功能过载。

5. Network Architecture Planning | 网络架构规划

The library system will be cloud-hosted with on-premises backup for reliability. Suggest a client-server model where web browsers act as thin clients, communicating via HTTPS with a cloud-based application server that processes business logic, while the database server resides in a separate subnet for security. Because multiple branches must access the central database simultaneously, a virtual private network (VPN) can be used to secure inter-branch traffic. Discuss bandwidth considerations: catalogue images should be compressed (WebP format) to reduce latency. For high availability, implement load balancing across two application server instances and configure auto-scaling during peak reservation periods (e.g., before holidays). For exam purposes, be prepared to draw a simple network topology diagram showing firewall placement, DMZ for public-facing web server, and internal database server. Mention protocols: HTTPS/SSL for encryption, SMTP for email notifications, and an API (RESTful) for supplier systems.

图书馆系统将采用云托管，并设有本地备份以确保可靠性。建议使用客户端-服务器模型，其中网络浏览器作为瘦客户端，通过 HTTPS 与处理业务逻辑的云应用服务器通信，而数据库服务器位于单独的子网中以保障安全。由于多个分馆需同时访问中央数据库，可使用虚拟专用网（VPN）保护馆际流量。讨论带宽因素：目录图片应压缩（WebP 格式）以减少延迟。为实现高可用性，在两个应用服务器实例间实施负载均衡，并在预约高峰期（如节假日前）配置自动伸缩。为应对考试，需准备绘制简单的网络拓扑图，显示防火墙位置、面向公众的 Web 服务器的 DMZ 以及内部数据库服务器。提及协议：用于加密的 HTTPS/SSL、用于邮件通知的 SMTP 以及面向供应商系统的 API（RESTful）。

6. Security and Data Protection | 安全与数据保护

Security must be embedded throughout the system lifecycle. Apply the CIA triad: Confidentiality (encrypt member passwords using salted SHA-256, enforce role-based access control so staff cannot see full member payment details), Integrity (database constraints, validation rules, and audit logs to track changes), and Availability (redundant servers, DDoS mitigation). The system must comply with the UK Data Protection Act 2018 and UK GDPR. As members’ personal data (names, emails, borrowing history) is collected, you must specify the lawful basis for processing (contractual necessity and consent for marketing), provide a privacy notice, and allow data portability. Explain that session cookies will be used only for authentication and that the system will automatically log out after 15 minutes of inactivity. A penetration test should be conducted before launch. For the exam, link each risk to a specific mitigation: SQL injection → parameterised queries, cross-site scripting → output encoding, insider threats → principle of least privilege.

安全性必须贯穿系统整个生命周期。应用 CIA 三元组：机密性（使用加盐 SHA-256 加密会员密码，实施基于角色的访问控制，使员工无法查看完整的会员支付信息）、完整性（数据库约束、验证规则和审计日志以跟踪更改）和可用性（冗余服务器、DDoS 缓解）。系统必须遵守《2018 年英国数据保护法》和英国 GDPR。由于收集会员个人数据（姓名、电子邮件、借阅历史），必须明确处理的合法依据（合同必要性和营销同意），提供隐私声明，并允许数据可移植性。解释会话 Cookie 将仅用于身份验证，且系统将在无操作 15 分钟后自动注销。上线前应进行渗透测试。对于考试，将每种风险与具体缓解措施联系起来：SQL 注入 → 参数化查询，跨站脚本 → 输出编码，内部威胁 → 最小权限原则。

7. Testing Strategy | 测试策略

Develop a comprehensive test plan covering unit, integration, system, and acceptance testing. During unit testing, check individual modules: the fine calculation function should correctly charge 20p per day, capped at the replacement cost of the book. Integration testing verifies that the reservation module correctly updates the Book table’s copiesAvailable when a reservation is removed. System testing evaluates end-to-end scenarios: a member searches for a book on a mobile device, reserves it, receives an email notification, and later renews it via the same interface. Use boundary value analysis for loan periods — test 0 days, maximum allowed 28 days, and 29 days. Acceptance testing involves real librarians and members performing typical tasks in a staging environment. Emphasise that a traceability matrix should map each functional requirement to test cases. For the written exam, you can present a table with columns: Test ID, Requirement, Input, Expected Output, Actual Result, Status. Also mention regression testing after any code update.

制定全面的测试计划，涵盖单元测试、集成测试、系统测试和验收测试。在单元测试中，检查各个模块：罚款计算功能应正确收取每天 20 便士，上限为图书重置成本。集成测试验证当预约被取消时，预约模块是否正确更新图书表中的可用副本数。系统测试评估端到端场景：会员在移动设备上搜索图书、预约、收到电子邮件通知，然后通过同一界面续借。对借阅期限使用边界值分析——测试 0 天、最大允许 28 天和 29 天。验收测试让真实的图书管理员和会员在预发布环境中执行典型任务。强调应使用可追溯性矩阵将每个功能需求映射到测试用例。对于笔试，可以展示一个包含以下列的表格：测试 ID、需求、输入、预期输出、实际结果、状态。还要提及任何代码更新后的回归测试。

8. Evaluation and Maintenance | 评估与维护

After deployment, the system must be evaluated against the original objectives. Define measurable criteria: reduction in average check-out time from 3 minutes to 30 seconds, 95% member satisfaction rating in a survey, zero critical security vulnerabilities in the first month. Discuss iterative maintenance types: corrective (fixing bugs found post-launch), adaptive (upgrading to support new browser versions), perfective (adding a recommendation engine based on borrowing patterns), and preventive (refactoring code to improve maintainability). In the SQA exam, you may be asked to justify why perfective maintenance should be scheduled only after user feedback analysis. Explain that change management procedures, including impact assessment and rollback plans, are essential to avoid disrupting live services. Show that you understand total cost of ownership: cloud hosting fees, ongoing staff training, and periodic security audits.

部署后，必须对照初始目标对系统进行评估。定义可衡量的标准：平均借阅处理时间从 3 分钟减少到 30 秒，调查中会员满意度达 95%，首月零严重安全漏洞。讨论迭代维护类型：纠正性维护（修复上线后发现的错误）、适应性维护（升级以支持新浏览器版本）、完善性维护（基于借阅模式添加推荐引擎）和预防性维护（重构代码以提高可维护性）。在 SQA 考试中，可能会要求你论证为什么完善性维护应在用户反馈分析之后才安排。解释变更管理程序，包括影响评估和回滚计划，对于避免中断实时服务至关重要。展示你对总拥有成本的理解：云托管费用、持续的员工培训和定期安全审计。

9. Legal and Ethical Implications | 法律与伦理影响

Beyond data protection, consider the Computer Misuse Act 1990 — unauthorised access to the library database by a member would be an offence. The Equality Act 2010 requires the digital platform to be accessible to users with disabilities, justifying the earlier interface design decisions. Ethically, the system should not use borrowing histories to infer sensitive information (e.g., medical conditions) without consent. When implementing a book recommendation algorithm, transparency is crucial: users should be able to see why a title was suggested and opt out. Intellectual property must be respected: book summary snippets displayed in search results should be obtained from the publisher’s API under licence. Discuss the ethical dilemma of digital inclusion — some elderly members may lack internet access; propose a solution: telephone renewal service and library kiosks. In your answer, always link legal clauses to system features to demonstrate applied understanding.

除数据保护外，还要考虑《1990 年计算机滥用法》——会员未经授权访问图书馆数据库属于违法行为。《2010 年平等法》要求数字平台可供残疾用户使用，这为之前的界面设计决策提供了依据。在伦理方面，系统不应在未经同意的情况下利用借阅历史推断敏感信息（如健康状况）。实施图书推荐算法时，透明度至关重要：用户应能看到推荐某书的原因并可选择退出。知识产权必须得到尊重：搜索结果中显示的图书摘要片段应通过出版商 API 获得许可。讨论数字包容性的伦理困境——一些老年会员可能缺乏互联网连接；提出解决方案：电话续借服务和图书馆自助终端。在答案中，始终将法律条款与系统功能联系起来，以展示应用性理解。

10. Exam Tips for Case Study Questions | 案例研究题的考试技巧

When approaching the SQA Advanced Higher computing paper, allocate 10 minutes to read the scenario and annotate it. Structure your responses using the sub-headings above even if the question is multipart. Use technical terminology accurately — say ‘normalised to 3NF’ rather than ‘organise the data properly’. Where possible, provide specific examples from the scenario instead of generic statements. For example, rather than ‘security is important’, write ‘member passwords must be hashed with salt to prevent credential reuse attacks’. Draw diagrams neatly with a ruler if describing a network or ERD. Manage your time: if a question carries 6 marks, aim for 3–4 distinct points. Practice with past papers, timing yourself to simulate exam conditions. Finally, in evaluation questions, always give both positive and negative aspects, then a justified conclusion. This balanced approach consistently earns top marks.

在应对 SQA 高级计算机试卷时，预留 10 分钟阅读并标注案例。即使问题有多部分，也用上述小标题结构组织回答。准确使用技术术语——说“规范化为 3NF”而非“合理组织数据”。尽可能提供来自案例的具体示例，而非笼统表述。例如，与其写“安全很重要”，不如写“会员密码必须加盐哈希以防凭据重用攻击”。描述网络或 ERD 时用尺子整齐绘图。管理好时间：如果一题 6 分，目标列出 3–4 个不同要点。用往年真题练习，计时模拟考试环境。最后，在评估题中，务必同时给出积极和消极方面，然后得出有理有据的结论。这种平衡方法能持续获得高分。

Published by TutorHao | Computing Revision Series | aleveler.com

更多咨询请联系16621398022（同微信）

Case Study Practice for SQA Advanced Higher Computing | SQA 高级计算机案例分析实战演练