📚 Year 13 CIE Computer Science: Case Study Practical Exercises | Year 13 CIE 计算机：案例分析实战演练
Case studies form a core part of CIE A-Level Computer Science Paper 4 (or equivalent components), where you are asked to solve a realistic problem through program design, pseudocode, and logical reasoning. Practising with real-world scenarios not only boosts your confidence but also sharpens your analytical skills. This article offers a structured walkthrough of how to tackle case study questions effectively, ending with a complete practice exercise.
案例分析是 CIE A-Level 计算机科学 Paper 4（或同等考试）的重要组成部分，要求你通过程序设计、伪代码和逻辑推理解决一个现实问题。通过真实场景练习不仅能提升自信，还能增强分析能力。本文将系统讲解如何高效应对案例分析题，并提供一个完整的实战演练。
1. Understanding the Case Study Question | 理解案例分析问题
Before diving in, read the question at least twice. Identify exactly what the examiner wants: is it a complete program, a single function, a set of subroutines, or a design document? Look for keywords such as ‘write pseudocode’, ‘design a data structure’, or ‘produce a trace table’. Pay attention to marking weight – an 8‑mark coding question demands more depth than a 2‑mark definition. Check any restrictions mentioned, for example ‘use a 1D array’, ‘implement binary search’, or ‘assume the file is already loaded’. Highlight these constraints so you don’t overlook them later.
开始之前，至少把题目读两遍。准确判断考官要求什么：是一个完整的程序、一个函数、一组子程序，还是一份设计文档？寻找关键指令，如 ‘编写伪代码’、’设计数据结构’ 或 ‘生成跟踪表’。注意分值——一道 8 分的编程题比 2 分的定义题需要更深入。审视题目中给出的任何限制，例如 ‘使用一维数组’、’实现二分查找’ 或 ‘假设文件已加载’。高亮这些约束，以免后续忽略。
Underline the input/output specifications. Often, case studies describe a user story: “A teacher needs to enter student marks and view averages.” Translate this into technical requirements: inputs (student IDs, marks), processes (calculate average, validate range), outputs (formatted report). Write a brief paragraph in your own words to confirm your understanding before attempting a solution.
标出输入/输出规格。案例分析通常会描述一个用户场景：“教师需要录入学生成绩并查看平均分。”将此转化为技术需求：输入（学号、成绩）、处理（计算平均分、验证范围）、输出（格式化报告）。在动手解题前，用自己的话写一小段确认理解。
2. Deconstructing the Scenario | 拆解场景
Break the narrative into logical components: actors (who uses the system), inputs, outputs, processing steps, and storage. A simple list or a rough structure chart can help. In CIE exams, you may be asked to draw a hierarchy chart before coding. Even if not required, a quick sketch on paper clarifies module relationships. For instance, a library system might have top‑level modules ‘Manage Books’, ‘Manage Members’, ‘Handle Transactions’, each with sub‑modules like ‘Add Book’, ‘Search Book’, ‘Borrow Book’, etc.
将叙述分解为逻辑组件：参与者（谁使用系统）、输入、输出、处理步骤和存储。列出简单清单或绘制简要结构图均可。在 CIE 考试中，你可能被要求在编码前画出层次图。即使不要求，在草稿纸上快速勾勒也能理清模块关系。例如，图书馆系统可能有顶层模块 ‘管理图书’、’管理会员’、’处理事务’，每个又包含子模块如 ‘添加图书’、’搜索图书’、’借书’ 等。
Explicitly state any assumptions. If the case study says “books are identified by a numeric ID”, assume IDs are unique integers. If it is not specified, you can decide and declare: “We assume book IDs are positive integers between 1000 and 9999.” Making reasoned assumptions shows examiners you understand the boundaries of the problem.
明确声明假设。若案例说“图书由数字 ID 标识”，则可假定 ID 是唯一整数。若未说明，可以自行决定并声明：“我们假设图书 ID 为 1000 至 9999 之间的正整数。”合理的假设能向考官展示你了解问题的边界。
3. Identifying Data and Processes | 识别数据与流程
Create a data dictionary early on. For each data item, record its identifier, type (Integer, String, Boolean, Real) and a short description. This prevents inconsistent naming later. For the library system, you might define:
尽早创建数据字典。为每个数据项记录其标识符、类型（整数、字符串、布尔、实数）和简要描述，这能避免后续命名不一致。对于图书馆系统，你可以这样定义：
| Identifier (标识符) | Type (类型) | Description (描述) |
|---|---|---|
| bookID | Integer | Unique code for each book (每本书的唯一编码) |
| title | String | Book title (书名) |
| author | String | Author of the book (作者) |
| onLoan | Boolean | TRUE if book is currently borrowed (若当前借出则为 TRUE) |
| memberID | Integer | Unique identifier for a member (会员唯一标识) |
Next, map out the data flow. Which module produces which data? For instance, ‘BorrowBook’ needs bookID and memberID as input; it updates the book’s onLoan flag and perhaps creates a loan record. Drawing even a simple Level‑0 DFD (data flow diagram) can solidify your design.
接下来，勾勒数据流动。哪个模块产生哪个数据？例如，’借书’ 需要 bookID 和 memberID 作为输入；它更新图书的 onLoan 标志并可能创建借阅记录。即使画一个简单的零层数据流图也能巩固设计。
4. Designing Algorithms and Pseudocode | 设计算法与伪代码
CIE expects clear, well‑formatted pseudocode. Use indentation to show structure. Start key functions with FUNCTION name(parameters) RETURNS type and end with ENDFUNCTION. For procedures, use PROCEDURE name(parameters) and ENDPROCEDURE. Use IF … THEN … ELSE … ENDIF, WHILE … DO … ENDWHILE, FOR … TO … NEXT. Always initialise variables and include comments.
CIE 期望清晰且格式规范的伪代码。用缩进表示结构。关键函数以 FUNCTION 名称(参数) RETURNS 类型 开头，以 ENDFUNCTION 结尾；过程则用 PROCEDURE 和 ENDPROCEDURE。结构使用 IF … THEN … ELSE … ENDIF、WHILE … DO … ENDWHILE、FOR … TO … NEXT。始终初始化变量并加上注释。
For a borrowBook function, the English logic is: receive bookID and memberID; search for bookID in the book array; if found and book is not on loan, set onLoan to TRUE, store memberID, and return ‘Success’; else return an appropriate error message. The corresponding pseudocode:
对于 borrowBook 函数，英文逻辑是：接收 bookID 和 memberID；在图书数组中查找 bookID；若找到且图书未借出，则设置 onLoan 为 TRUE、存储 memberID，并返回 ‘Success’；否则返回相应的错误信息。对应伪代码：
FUNCTION borrowBook(bID: INTEGER, mID: INTEGER) RETURNS STRING
DECLARE index ← searchBook(bID)
IF index = -1 THEN
RETURN “Book not found”
ELSE
IF bookArray[index].onLoan = FALSE THEN
bookArray[index].onLoan ← TRUE
bookArray[index].currentMember ← mID
RETURN “Success”
ELSE
RETURN “Book already on loan”
ENDIF
ENDIF
ENDFUNCTION
Note the use of a helper function searchBook which returns the index or -1. Breaking a large task into smaller subroutines is good practice and simplifies testing.
注意这里使用了辅助函数 searchBook，返回索引或 -1。将大任务分解为小方法是一个良好实践，且能简化测试。
5. Selecting Appropriate Data Structures | 选择合适的数据结构
Choosing how to store data is critical. In CIE pseudocode, you often deal with arrays or records. A record groups related fields together, while an array holds multiple instances. A 2D array might represent a table, but records within a 1D array are usually more readable. Consider the need for searching and sorting:
如何存储数据至关重要。在 CIE 伪代码中，你常需要处理数组或记录。记录将相关字段组合在一起，数组则存储多个实例。二维数组可表示表格，但使用一维数组搭配记录通常可读性更强。考虑搜索和排序需求：
| Data Structure (数据结构) | Advantage (优势) | Typical Use in Case Study (案例中的典型用途) |
|---|---|---|
| 1D Array of Records (一维记录数组) | Easy to iterate; records keep fields together | Book list, member list (书目、会员列表) |
| 2D Array (二维数组) | Compact for purely numeric grids | Pixel maps, mark sheets (像素图、成绩表) |
| Queue / Stack (队列/栈) | Ordered processing (FIFO/LIFO) | Waiting list, undo history (等候名单、撤销历史) |
For the library system, a 1D array of BookRecord is ideal. Searching depends on whether the array is sorted. If books are kept in ascending order by ID, binary search (O(log₂n)) is efficient; if not, linear search (O(n)) is used. Always comment on algorithmic complexity where relevant.
对于图书馆系统，一维 BookRecord 数组很理想。搜索取决于数组是否已排序。若图书按 ID 升序排列，二分查找（O(log₂n)）高效；若未排序，则用线性查找（O(n)）。在合适的地方始终评论算法复杂度。
6. Handling Edge Cases and Errors | 处理边界情况与错误
Robust programs don’t just handle the ‘happy path’. Consider invalid inputs such as empty strings, negative IDs, or missing data. For a borrow function, what if the member ID does not exist? What if the book is already on loan? What if the array is full? Each of these must trigger a meaningful response. In pseudocode, add IF checks at the very start of a subroutine to validate arguments.
强健的程序不能只处理“理想路径”。要考虑无效输入，例如空字符串、负数 ID 或缺失数据。对于借书函数，如果会员 ID 不存在会怎样？如果书已借出呢？如果数组已满呢？每种情况都应返回有意义的信息。在伪代码中，可在子程序开头添加 IF 检查来验证参数。
Also think about boundary values. If the system limits books to 500, test with index 0 and index 499. Make sure loops do not cause off‑by‑one errors. A common CIE trap is an array indexing of 1…n in one part and 0…n‑1 in another. Be consistent and state your range clearly.
也要考虑边界值。如果系统限制最多 500 本书，要测试索引 0 和 499。确保循环不致差一错误。CIE 常见的陷阱是一处使用 1…n 索引，另一处使用 0…n‑1。必须保持一致并清楚说明索引范围。
7. Writing Efficient and Clear Code | 编写高效清晰的代码
Even in pseudocode, efficiency counts. Avoid nested loops where a single pass could work. Use Boolean flags to exit early when a condition is met. Name variables so their purpose is obvious — bookCount is better than x. Maintain a consistent naming convention; CIE often uses camelCase or PascalCase. Keep your code DRY (Don’t Repeat Yourself): if you find yourself copying a chunk of logic, turn it into a separate procedure.
即使在伪代码中，效率也重要。避免在单次遍历就能解决问题时使用嵌套循环。使用布尔标志，满足条件时提前退出。变量命名要体现意图——bookCount 比 x 更好。保持一致的命名约定；CIE 常使用 camelCase 或 PascalCase。遵循 DRY 原则（不要重复自己）：若发现重复的逻辑块，就将其提取为独立的过程。
For example, searching for a book by ID is needed in borrow, return, and search functions. Instead of copying the linear‑search code three times, write a reusable findBookByID(bID) function that all modules call.
例如，按 ID 查找图书在借书、还书和搜索功能中都会用到。与其在三处复制线性查找代码，不如编写一个可复用的 findBookByID(bID) 函数，让所有模块调用。
8. Testing Your Solution Thoroughly | 全面测试你的解决方案
Create a test plan with at least three categories: normal, boundary, and erroneous data. For the library system:
制定一份测试计划，至少包含三类：正常数据、边界数据和错误数据。以图书馆系统为例：
| Test Category (测试类别) | Input (输入) | Expected Output (预期输出) |
|---|---|---|
| Normal (正常) | borrowBook(102, 7) where book 102 is available | “Success”; onLoan becomes TRUE |
| Boundary (边界) | 更多咨询请联系16621398022（同微信）
CommentsMore posts |
屏轩国际教育cambridge primary/secondary checkpoint, cat4, ukiset,ukcat,igcse,alevel,PAT,STEP,MAT, ibdp,ap,ssat,sat,sat2课程辅导，国外大学本科硕士研究生博士课程论文辅导