Case Study Practical Drill for Year 13 CIE Computer Science | Year 13 CIE 计算机：案例分析实战演练

📚 Case Study Practical Drill for Year 13 CIE Computer Science | Year 13 CIE 计算机：案例分析实战演练

Case study questions in the CIE A-Level Computer Science syllabus (9618) demand more than just reciting textbook facts — they require you to apply computational thinking to realistic, often open-ended scenarios. This article provides a structured approach to mastering such questions, complete with a worked example that mirrors the depth expected at Year 13. By breaking down the process into clear stages, you will learn how to extract requirements, design data structures, select appropriate algorithms and critically evaluate your own solution.

案例分析题在 CIE A-Level 计算机科学（9618）大纲中，不仅仅考查对课本知识的记忆，更要求你将计算思维应用于真实且往往开放性的情境。本文提供了一套结构化的解题方法，并配以完整的实战案例，力求达到 Year 13 所要求的深度。我们将过程拆解为清晰的阶段，让你学会如何抽取需求、设计数据结构、选择合适的算法，并对自己的方案进行批判性评估。

1. Understanding Case Studies in CIE A-Level Computer Science | 理解案例分析在 CIE 计算机科学中的地位

Case study questions typically appear in Paper 3 (Advanced Theory) and implicitly in Paper 4 (Practical), where you might be asked to design a system or analyse a given scenario. They test your ability to integrate knowledge from multiple topics — such as databases, networking, algorithms and system design — into a coherent solution. Examiners look for evidence of methodical analysis, justified decisions and an awareness of trade-offs.

案例分析题通常出现在 Paper 3（高级理论）中，而 Paper 4（实践）也隐含着类似的要求，需要你设计系统或分析给定情境。这类题考查的是你能否将数据库、网络、算法和系统设计等多个模块的知识融会贯通为一个连贯的解决方案。考官看重的是有条理的分析过程、有根据的决策以及对权衡取舍的清醒认识。

2. The Systematic Approach to Analysis | 系统化分析方法

Adopting a systematic approach ensures that no critical aspect is overlooked. We recommend the following five-stage framework: Scope Definition → Requirement Elicitation → Solution Design → Implementation Planning → Evaluation. This mirrors industry-standard methodologies like the Systems Development Life Cycle but is tailored to the time constraints of an examination.

采用系统化的方法可以避免遗漏关键环节。我们推荐以下五阶段框架：范围界定 → 需求获取 → 方案设计 → 实施规划 → 评估。这一流程借鉴了系统开发生命周期等行业标准方法，但同时针对考试时间限制进行了调整。

3. Deconstructing the Problem Statement | 拆解问题陈述

Begin by reading the scenario twice. Underline keywords that indicate functional requirements (what the system must do), non-functional requirements (performance, security, usability), constraints (budget, hardware, legacy systems) and stakeholders. Create a quick mind map linking entities, processes and data flows. This initial parsing prevents misinterpretation and helps you frame the scope of your answer.

首先将情境阅读两遍。划出指示功能性需求（系统必须做什么）、非功能性需求（性能、安全性、易用性）、约束条件（预算、硬件、遗留系统）以及利益相关者的关键词。快速画一个思维导图，将实体、处理流程和数据流连接起来。这种初期解析可以防止误解，并帮助你界定答案的范围。

---

4. Identifying Stakeholders and Requirements | 识别利益相关者与需求

List every stakeholder mentioned or implied: end-users, system administrators, business owners, regulatory bodies. For each, extract their specific needs using a table like the one below. This demonstrates a user-centred mindset, which is highly valued in exam responses.

列出所有提及或隐含的利益相关者：最终用户、系统管理员、企业主、监管机构。针对每一类，使用类似下面的表格提取其具体需求。这展示了一种以用户为中心的思维，在考试答案中备受重视。

Stakeholder	Functional Need	Non-functional Expectation
Librarian	Check in/out books rapidly	Response time < 2 seconds
Member	Search catalogue, renew online	24/7 availability, intuitive UI
IT Manager	Backup, audit trail	Data encrypted at rest, ACID compliance

Stakeholder analysis is not a box-ticking exercise; it directly informs the design of interfaces, access controls and the database schema.

利益相关者分析不是走过场；它会直接影响界面设计、访问控制和数据库模式。

---

5. Designing a Robust Solution: Architecture & Data Structures | 设计稳健方案：架构与数据结构

Decide on an architectural style — client-server, peer-to-peer, or a mobile app with a cloud backend. Justify your choice with reference to the scenario. For a typical library management case, a centralised client-server model with a thin client (web browser) offers ease of maintenance and consistent data. Next, define the core data structures. Will you use arrays, linked lists, stacks, or queues? Most real-world systems rely on abstract data types mapped to database tables, but you must also reason about in-memory structures for caching or session data.

确定一种架构风格——客户端-服务器、对等网络，或是带云后端的移动应用。结合情境为你的选择提供理由。对于典型的图书馆管理案例，采用瘦客户端（网页浏览器）的集中式客户端-服务器模型便于维护，且数据一致性好。接下来，定义核心数据结构。你会使用数组、链表、栈还是队列？大部分真实系统依赖映射到数据库表的抽象数据类型，但你还需要考虑用于缓存或会话数据的内存结构。

For instance, a priority queue might be used to manage requests for rare books, while a binary search tree could index books by ISBN for logarithmic lookup. Explicitly state where each structure fits and why it outperforms naive alternatives.

例如，优先队列可用于管理珍本图书的借阅请求，而二叉搜索树可以按 ISBN 索引图书以实现对数级查找。要明确指出每种结构用于何处，以及它为何比朴素的替代方案更优。

---

6. Algorithm Selection and Pseudocode Development | 算法选择与伪代码开发

Identify the key algorithms: searching, sorting, pathfinding or scheduling. In a library system, a binary search on sorted records by ISBN is more efficient than linear search, giving O(log n) time complexity. Write out the algorithm in clear pseudocode, using standard CIE conventions (INPUT, OUTPUT, WHILE…DO, IF…THEN…ELSE).

识别关键算法：搜索、排序、路径寻找或调度。在图书馆系统中，按 ISBN 排序记录后进行二分查找比线性查找更高效，时间复杂度为 O(log n)。用清晰的伪代码写出算法，遵循 CIE 标准约定（INPUT、OUTPUT、WHILE…DO、IF…THEN…ELSE）。

PROCEDURE BinarySearch(BookArray, targetISBN)
low ← 0
high ← LEN(BookArray)-1
WHILE low <= high DO
mid ← INT((low+high)/2)
IF BookArray[mid].ISBN = targetISBN THEN
RETURN mid
ELSE IF BookArray[mid].ISBN < targetISBN THEN
low ← mid + 1
ELSE
high ← mid – 1
ENDIF
ENDWHILE
RETURN -1
ENDPROCEDURE

Always analyse the worst-case time complexity and mention any assumptions, such as pre-sorted data. This shows analytical depth.

务必分析最坏情况下的时间复杂度，并提及任何假设，例如数据已预排序。这能体现分析深度。

---

7. Database Design and Normalisation | 数据库设计与规范化

Construct an Entity-Relationship diagram (in text) and derive a relational schema. Ensure the design reaches Third Normal Form (3NF) to eliminate redundancy. For a library, key entities include Book, Member, Loan, Reservation. Use standard notation for primary keys (PK) and foreign keys (FK).

构建实体关系图（以文字形式）并推导关系型模式。确保设计达到第三范式（3NF）以消除冗余。对于图书馆，核心实体包括 Book、Member、Loan、Reservation。用标准符号标注主键（PK）和外键（FK）。

Book (ISBN, Title, Author, PublicationYear, CategoryID*)
Member (MemberID, Name, Email, JoinDate)
Loan (LoanID, ISBN*, MemberID*, DateOut, DateDue, DateReturned)
Reservation (ResID, ISBN*, MemberID*, ReserveDate, Status)

Explain how this schema supports common queries without joins across an excessive number of tables, and how indexes on FK columns improve performance.

解释该模式如何支持常见查询而无需跨过多表进行连接，以及外键列上的索引如何提升性能。

---

8. User Interface and Input/Output Considerations | 用户界面与输入输出考量

Sketch a wireframe for the main screens using a textual description. For a web-based library system, the member dashboard might include: a search bar, a list of current loans with due dates, and a button to renew. Highlight input validation techniques — format checks on email, range checks on publication year, and check-digit validation on ISBNs. Output should consider accessibility, such as screen-reader compatibility and high-contrast modes.

用文字描述勾勒主要界面的线框图。对于基于网页的图书馆系统，会员仪表板可能包括：一个搜索栏、带到期日的当前借阅清单，以及续借按钮。强调输入验证技术——对电子邮件格式的检查、对出版年份的范围检查，以及对 ISBN 的校验位验证。输出应考虑可访问性，如屏幕阅读器兼容性和高对比度模式。

Discuss the choice between a command-line interface (CLI) and a graphical user interface (GUI). For most end-users, a GUI is preferred, but a CLI may still be appropriate for batch operations performed by librarians.

讨论命令行界面（CLI）与图形用户界面（GUI）之间的选择。对大多数最终用户而言，GUI 更合适，但图书馆员执行的批处理操作可能仍适合使用 CLI。

---

9. Testing Strategies and Evaluation | 测试策略与评估

A complete case study response includes a testing plan. Describe unit tests for individual modules (e.g., binary search function), integration tests for database transactions (e.g., loan creation updates multiple tables correctly), and user acceptance tests. Explain the use of normal, boundary and erroneous test data. For instance, testing a loan period: normal (14 days), boundary (0 days, 365 days) and erroneous (negative days, non-numeric input).

一份完整的案例分析答案应包括测试计划。描述针对单个模块的单元测试（例如二分查找函数）、针对数据库事务的集成测试（例如创建借阅记录能否正确更新多张表），以及用户验收测试。说明如何使用正常、边界和错误测试数据。例如，测试借阅期限：正常值（14天）、边界值（0天、365天）和错误值（负数天数、非数值输入）。

Evaluation should not simply say ‘the solution works’. Critically assess limitations: what happens if the internet connection fails? Can the system handle a sudden surge of 500 concurrent users? Would the binary search still be optimal if the catalogue is updated every minute? Such reflective comments elevate your answer to the highest grade band.

评估不应简单地说“此方案有效”。要批判性地审视其局限性：若互联网连接中断会发生什么？系统能承受 500 个并发用户的突发流量吗？如果图书目录每分钟更新一次，二分查找依然是最优选择吗？这类反思性评论能将你的答案提升至最高评分档次。

---

10. Common Pitfalls and How to Avoid Them | 常见陷阱与规避方法

Many candidates lose marks by describing rather than analysing. Avoid simply restating the scenario; always add value by proposing specific algorithms, data structures, or schema designs. Neglecting non-functional requirements is another frequent mistake — explicitly address security, scalability and maintainability. Finally, manage your time: allocate roughly equal time to requirements, design, and evaluation, leaving 5 minutes for proofreading.

许多考生因描述而非分析而丢分。避免仅仅复述情境；始终要通过提出具体的算法、数据结构或模式设计来增加价值。忽视非功能性需求是另一常见错误——务必明确讨论安全性、可扩展性和可维护性。最后，要管理好时间：将大约相同的时间分配给需求、设计和评估，并留出 5 分钟用于检查。

---

11. Practice Example: A Community Library Digital Transformation | 实战演练：社区图书馆数字化转型

Scenario: A local community library currently uses paper records. They want a digital system that allows members to search for books online, place holds, and receive email notifications when a book is available. The librarian needs to manage inventory, track overdue loans and print reports. The system must work on the library’s two public kiosks and on members’ personal devices.

情境： 某社区图书馆目前使用纸质记录。他们需要一个数字化系统，允许会员在线搜索图书、预约并在图书可借时收到电子邮件通知。图书管理员需要管理库存、追踪逾期借阅并打印报告。系统必须能在图书馆的两台公共信息亭以及会员的个人设备上运行。

Application of the framework:

框架应用：

• Stakeholders: Members, Librarians, IT Support.
• 需求： Members need secure login, catalogue search with filters (author, genre, availability), place holds. Librarians need an admin dashboard with CRUD operations on books, view member status, generate overdue reports as PDF. Non-functional: must respond within 3 seconds under normal load, encrypt passwords, comply with data protection laws.
• Architecture: Three-tier web architecture (presentation, application logic, database) hosted on a local server, accessible via HTTPS. Kiosks run a locked-down browser.
• Data Structures: A dictionary (hash table) for caching member sessions; a queue for hold requests to ensure fair access; a SQL database with tables for Books, Members, Holds, Loans, Notifications.
• Algorithms: Linear search with indexed database for catalogue search (since filters and partial matches preclude simple binary search), email notification via a background polling process that checks Holds table every 5 minutes.
• Testing: Unit test each stored procedure; simulate 20 concurrent search requests and measure response time; test edge cases like a member placing a hold on the last available copy.

This concise walkthrough demonstrates how to apply every stage of the framework to a realistic brief, balancing theoretical justification with practical awareness.

这一简洁的演练展示了如何将此框架的每个阶段应用于一个真实简报，做到理论依据与实践意识之间的平衡。

---

12. Conclusion: Linking Theory to Practice | 结语：理论联系实际

Mastering the CIE case study requires sustained practice in thinking like a systems architect. Regularly attempt past papers and vary the domains — from healthcare booking systems to e-commerce inventory — to build versatility. Remember that the best answers are those where every technical choice is clearly justified and the solution is critiqued honestly. Use the framework presented here as a mental checklist, and you will approach any case study with confidence.

要精通 CIE 案例分析题，需要持续练习像系统架构师一样思考。定期尝试往年真题，并变换领域——从医疗预约系统到电商库存——以培养应变能力。请记住，最佳答案中的每一项技术选择都有清晰的理由，且方案被诚实审辩。将本文中的框架作为思维检查清单，你将能充满信心地应对任何案例分析题。

Published by TutorHao | Computer Science Revision Series | aleveler.com

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