📚 Year 12 CIE Computer Science Case Study Practice | Year 12 CIE 计算机：案例分析实战演练
Case study questions in CIE AS Computer Science (9618) are designed to test your ability to apply theoretical knowledge to real-world scenarios. They require you to analyse a given situation, identify requirements, propose solutions, and justify your design choices. This article will guide you through a structured approach, using a practical example to build your confidence and exam technique.
CIE AS 计算机科学（9618）中的案例分析题旨在检验你将理论知识应用于实际场景的能力。它们要求你分析给定情境、识别需求、提出解决方案并论证设计选择。本文将通过结构化方法和一个实操示例带你练习，帮助你建立信心、掌握答题技巧。
1. Understanding the Case Study Approach | 理解案例分析题型
Case study questions usually present a narrative describing a problem an organisation or individual is facing. You will be asked to design a software or hardware solution, evaluate alternatives, or discuss social and ethical implications. The exam rewards depth of understanding rather than recall of isolated facts.
案例分析题通常提供一段叙述，描述某个组织或个人面临的问题。你需要设计一个软件或硬件解决方案、评估替代方案，或讨论社会与伦理影响。考试奖励的是理解的深度，而非孤立知识点的记忆。
Marks are allocated for structured decomposition, clear reasoning, and the correct application of computational thinking. Always read the scenario twice: first to grasp the big picture, second to underline key constraints, data items, and user needs.
分数会分配给结构化分解、清晰的推理以及计算思维的正确运用。务必把情景读两遍：第一遍把握大局，第二遍勾画出关键约束、数据项和用户需求。
2. Key Knowledge Areas | 核心知识领域
Before tackling a case study, ensure you are comfortable with these topics covered in Year 12: abstraction and decomposition, algorithm design (pseudocode), data representation, databases and file handling, network fundamentals, system life cycle, and the ethical/social aspects of computing.
在攻克案例分析之前，确保你对 Year 12 所涵盖的主题得心应手：抽象与分解、算法设计（伪代码）、数据表示、数据库与文件处理、网络基础、系统生命周期以及计算的社会伦理因素。
Additionally, you need to be able to compare programming paradigms, evaluate backup and security strategies, and understand the roles of different development methodologies. Real-world constraints such as budget, time, and hardware limitations often appear in the narrative.
此外，你需要能够比较编程范式、评估备份与安全策略，并理解不同开发方法的角色。预算、时间和硬件限制等现实约束经常会出现在情景描述中。
3. Step-by-Step Analysis Framework | 分步分析框架
A reliable method for approaching any case study is the UPAC framework: Understand the problem, Plan a solution, Analyse details, and Communicate the answer. Start by identifying inputs, processes, outputs, and storage requirements.
应对任何案例分析题的可靠方法是 UPAC 框架：理解问题（Understand）、规划解决方案（Plan）、分析细节（Analyse）、表达答案（Communicate）。首先识别输入、处理、输出和存储需求。
Draw a simple system boundary diagram in your mind or on scratch paper. List all stakeholders and their needs. Then break the system into manageable modules. This top-down approach prevents you from writing disorganised answers.
在脑海中或草稿纸上画一个简单的系统边界图。列出所有利益相关者及其需求。然后将系统分解为可管理的模块。这种自顶向下的方法能防止答题杂乱无章。
4. Case Study Example: Library Management System | 案例分析示例：图书馆管理系统
Let us apply the skills to a typical CIE-style case: A small school library currently uses paper-based records. The librarian wants a computerised system to track books, members, and loans. The system must run on a single PC and be easy for non-technical staff to use.
让我们把技能应用到一个典型的 CIE 风格案例中：一所小型学校图书馆目前使用纸质记录。管理员希望有一套计算机系统来追踪图书、成员和借阅情况。系统需运行在单台 PC 上，且便于非技术人员使用。
Expected outputs: a daily report of overdue books, a search function by title or author, and the ability to register new members. Only the librarian should have access to member data. No internet connectivity is available in the library room.
预期输出：每日逾期图书报告、按书名或作者搜索的功能，以及注册新成员的能力。只有管理员可以访问成员数据。图书馆室内没有网络连接。
5. Decomposition and Abstraction | 分解与抽象
Abstracting the essential details: the system requires three main files – Books, Members, Loans. Each book has attributes: ISBN, title, author, status. Each member has ID, name, contact. Each loan links a member ID and book ISBN with a due date.
对关键细节进行抽象：系统需要三个主要文件——图书、成员、借阅。图书属性：ISBN、书名、作者、状态。成员属性：ID、姓名、联系方式。借阅将成员 ID 和图书 ISBN 关联，并包含应还日期。
Decompose functionality into modules: Member Registration, Book Cataloguing, Loan Processing, Search, and Overdue Report Generation. This separation allows independent development and testing.
将功能分解为模块：成员注册、图书编目、借阅处理、搜索和逾期报告生成。这种分离允许独立开发和测试。
6. Algorithms and Pseudocode Design | 算法与伪代码设计
Design the Search module algorithm. Input: search term and type (title/author). Process: read through the Books file sequentially, comparing the term with the relevant field. Output: display matching records.
设计搜索模块算法。输入：搜索词和类型（书名/作者）。处理：顺序读取图书文件，将搜索词与相关字段比较。输出：显示匹配记录。
PROCEDURE SearchBooks(term, searchType)
OPENFILE Books FOR READ
WHILE NOT EOF(“Books”) DO
READFILE “Books”, currentBook
IF searchType = “title” AND currentBook.title = term THEN
OUTPUT currentBook
ELSE IF searchType = “author” AND currentBook.author = term THEN
OUTPUT currentBook
ENDIF
ENDWHILE
CLOSEFILE “Books”
ENDPROCEDURE
Above pseudocode uses a linear search because the dataset is small. For larger systems, explain why an index or hash table would improve performance – this demonstrates evaluation skills examiners look for.
上述伪代码采用线性搜索，因为数据集很小。对于更大的系统，要解释为什么索引或哈希表可以改善性能——这正是考官希望看到的评估能力。
7. Data Structures and File Handling | 数据结构与文件处理
Choose appropriate structures: each record in the Books file can be a fixed-length record with fields: ISBN(13 chars), Title(50), Author(30), Status(10). Fixed-length simplifies direct access, but wastes space. Variable-length records with a delimiter could save storage.
选择合适的数据结构：图书文件每条记录可以是定长记录，字段：ISBN（13字符）、书名（50）、作者（30）、状态（10）。定长虽简化了直接存取，但浪费空间。带分隔符的变长记录可以节省存储。
For the Loans file, a linked approach using member ID and book ISBN as foreign keys works naturally. Data integrity rules: no loan without valid member and available book. Declare these rules in pseudocode or a brief description.
借阅文件使用成员 ID 和图书 ISBN 作为外键的链接方法很自然。数据完整性规则：没有有效成员和可借图书就不能产生借阅。在伪代码或简短描述中声明这些规则。
8. Evaluation and Testing | 评估与测试
Testing must be systematic. Plan a test table covering normal, boundary, and erroneous data. Example: test loaning a book that is already on loan (error), loaning with an invalid member ID, and loaning when all copies are available (normal).
测试必须系统化。制定测试表，覆盖正常、边界和错误数据。例如：测试借出一本已借出的书（错误）、用无效成员 ID 借阅、以及所有复本均可用时的借阅（正常）。
- Normal: Member M01 borrows ISBN 001; expected: loan recorded, status updated to “On loan”.
- 正常：成员 M01 借阅 ISBN 001；预期：记录借阅，状态更新为“在借”。
- Boundary: Try to borrow when due date equals today’s date configuration; expected: system warns.
- 边界：尝试在应还日期等于当天配置时借阅；预期：系统警告。
- Erroneous: Input empty search term; expected: prompt user to re-enter.
- 错误：输入空搜索词；预期：提示用户重新输入。
Also discuss acceptance testing with the librarian to ensure the interface meets non-functional requirements like usability.
还要讨论与管理员一起进行验收测试，确保界面符合可用性等非功能性需求。
9. Common Pitfalls to Avoid | 常见陷阱需避免
Avoid diving straight into coding without analysis. Many students lose marks by skipping requirement identification or ignoring the ‘why’ behind their choices. Also, do not describe screens in excessive detail unless the question specifically asks for interface design.
避免不经过分析就直接编码。许多学生因跳过需求识别或忽略选择背后的“为什么”而失分。同时，除非题目特别要求界面设计，否则不要过度描述屏幕界面。
Straying from the given scenario is another mistake. If the case mentions ‘no internet’, you cannot propose a cloud-based solution. Always base your answer on explicitly stated constraints, not assumptions.
脱离给定情景是另一个错误。如果案例提到“没有网络”，你就不能提出基于云的方案。始终基于明确陈述的约束来回答，而非个人假设。
10. Practice with a Sample Question | 示例问题实践
Here is a mini-exercise based on our library case: “Describe two data validation checks you would implement in the member registration module and explain why each is necessary.”
这里有一个基于图书馆案例的小练习：“请描述你将在成员注册模块中实施的两种数据验证检查，并解释每种检查的必要性。”
Answer: 1) Length check on member name – ensures the name field is not empty and does not exceed 30 characters, preventing storage errors. 2) Format check on contact number – only digits and a leading ‘+’ are allowed, maintaining data consistency for future SMS reminders if ever needed.
答案：1）对成员姓名进行长度检查——确保姓名字段非空且不超过 30 个字符，防止存储错误。2）对联系方式进行格式检查——仅允许数字和前置“+”，以保持数据一致性，便于将来可能的短信提醒。
Notice how the explanation connects to the context. The examiner can award full marks because each check is tied to a specific need in the scenario.
请注意解释是如何与情境关联的。考官可以给满分，因为每项检查都与情境中的特定需求挂钩。
11. Marking Criteria Insights | 评分标准解读
CIE mark schemes for case studies typically split marks across: problem identification (5-10%), solution design (15-25%), justification/evaluation (20-30%), and technical accuracy. Most candidates lose marks on weak justification.
CIE 案例分析的评分标准通常将分数划分为：问题识别（5-10%）、方案设计（15-25%）、论证/评价（20-30%）和技术准确性。多数考生因论证薄弱而失分。
| Criterion | What earns marks |
|---|---|
| Analysis | Listing constraints, stakeholders, data entities |
| Design | Algorithms, file structures, validation rules |
| Justification | Explaining why a choice fits the scenario, comparing alternatives |
| Communication | Clarity, use of technical terms, pseudocode conventions |
Use the phrase ‘because…’ frequently. For example, ‘I chose a sequential file because the library has fewer than 500 books and random access is not required, simplifying implementation.’
经常使用“因为……”这个句式。例如，“我选择了顺序文件，因为图书馆藏书少于 500 本，不需要随机存取，从而简化了实现。”
12. Final Tips for Exam Success | 备考成功秘诀
Allocate time wisely: spend about 10 minutes reading and planning, then write concisely. If a question asks for three advantages, list exactly three; extra points risk contradicting yourself without gaining extra credit.
合理分配时间：大约花 10 分钟阅读和规划，然后简洁作答。如果题目要求列出三个优点，就只写三个；多余的要点可能会自相矛盾，却不会额外加分。
Practice with past papers under timed conditions. After writing, compare your answer with the mark scheme and note any technical terms you missed. Build a glossary of command words such as ‘state’, ‘describe’, ‘analyse’, and ‘evaluate’.
在限时条件下练习历年真题。写完后再对照评分标准，记下缺失的技术术语。建立一个包含“说明”、“描述”、“分析”、“评价”等指令词的词汇表。
Finally, remember that the case study is a chance to show real-world thinking. Even if you forget a specific algorithm, a well-reasoned approach using decomposition and abstraction can still earn the majority of marks.
最后，记住案例分析是展示现实世界思考的机会。即使你忘记某个特定算法，运用分解与抽象给出的合理方法仍能拿到大部分分数。
Published by TutorHao | Computer Science Revision Series | aleveler.com
更多咨询请联系16621398022（同微信）
屏轩国际教育cambridge primary/secondary checkpoint, cat4, ukiset,ukcat,igcse,alevel,PAT,STEP,MAT, ibdp,ap,ssat,sat,sat2课程辅导，国外大学本科硕士研究生博士课程论文辅导