AS CAIE Computer Science: Case Study Practical Walkthrough | AS CAIE 计算机：案例分析实战演练

📚 AS CAIE Computer Science: Case Study Practical Walkthrough | AS CAIE 计算机：案例分析实战演练

Case study questions in AS CAIE Computer Science (9618) challenge you to apply computational thinking to a realistic scenario. This article walks you through a structured approach to deconstructing requirements, designing algorithms, selecting data structures, and testing your solution. By working step-by-step on a movie ticket booking example, you will gain confidence in tackling any case study under exam conditions.

AS CAIE 计算机科学（9618）中的案例分析题要求你将计算思维应用到真实场景中。本文带你逐步拆解需求、设计算法、选择数据结构并测试解决方案。通过一个电影票预订实例的完整演练，你将建立起在考试条件下应对任何案例分析的信心。

1. Understanding the Case Study Task | 理解案例分析任务

A case study typically presents a problem statement describing a system or process, such as managing bookings, processing sales, or simulating a scientific model. Your task is to identify what the program must do, what data it manipulates, and what output it produces.

案例分析通常会给出一个描述系统或过程的问题陈述，例如管理预订、处理销售或模拟科学模型。你的任务是明确程序必须做什么、操作哪些数据以及产生什么输出。

Start by reading the scenario carefully and highlighting key functional requirements. Note any constraints, such as limited resources or specific validation rules. Distinguish between what is explicitly asked and what is implied by the context.

首先仔细阅读场景，标出关键功能需求。注意任何限制条件，例如资源有限或特定的验证规则。区分明确要求的内容和上下文所暗示的内容。

2. Breaking Down Requirements and Abstraction | 需求分解与抽象

Once you have listed all functional requirements, decompose the problem into manageable modules. Abstraction helps you focus on essential features while ignoring irrelevant details. For a ticket booking system, essential features include selecting a movie, entering ticket quantity, calculating cost, and updating seat availability.

列出所有功能需求后，将问题分解为可管理的模块。抽象帮助你聚焦基本特性，忽略无关细节。对于票务预订系统，基本功能包括选择电影、输入票数、计算费用和更新座位余量。

You might decide to split the system into input collection, processing logic, and output display. Identify dependencies: for instance, cost calculation depends on ticket type and quantity. Record these relationships in a simple structure chart or numbered list to keep your design clear.

你可以决定将系统拆分为输入收集、处理逻辑和输出显示。识别依赖关系：例如，费用计算取决于票型和数量。将这些关系记录在简单的结构图或编号列表中，使设计保持清晰。

3. Identifying Inputs, Outputs, and Variables | 识别输入、输出与变量

Clearly define all inputs and outputs. Inputs may include user choices (movie name, seat type), numeric values (number of tickets), and possibly system status (remaining seats). Outputs are the total price, confirmation messages, or error prompts.

明确定义所有输入和输出。输入可能包括用户选择（电影名称、座位类型）、数值（票数），以及可能的系统状态（剩余座位）。输出则是总价、确认信息或错误提示。

Map each data item to a variable with a meaningful name and appropriate data type. For example, movieChoice : STRING, ticketType : CHAR, quantity : INTEGER, totalPrice : REAL. Maintain a variable table to help you during pseudocode writing.

将每个数据项映射到具有有意义名称和合适数据类型的变量。例如，movieChoice : STRING、ticketType : CHAR、quantity : INTEGER、totalPrice : REAL。维护一个变量表有助于编写伪代码。

4. Designing the Algorithm with Pseudocode | 用伪代码设计算法

Pseudocode allows you to express the logic without worrying about syntax. Use consistent constructs: INPUT, OUTPUT, IF ... THEN ... ELSE ... ENDIF, WHILE ... DO ... ENDWHILE, and FOR ... TO ... NEXT. Assignment uses the left arrow ←.

伪代码使你可以表达逻辑而不必担心语法。使用一致的结构：INPUT、OUTPUT、IF ... THEN ... ELSE ... ENDIF、WHILE ... DO ... ENDWHILE 以及 FOR ... TO ... NEXT。赋值使用左箭头 ←。

For the booking system, begin with an initialisation block: set availableSeats ← 100, constant prices. Then loop until the user quits or seats are exhausted. Inside the loop, read inputs, validate, compute price, update seat count, and output result.

对于预订系统，从初始化块开始：设置 availableSeats ← 100，常量价格。然后循环，直到用户退出或座位售罄。在循环内，读取输入、验证、计算价格、更新座位计数并输出结果。

Always consider decision points: what if quantity exceeds available seats? What if invalid ticket type is entered? Use conditional statements to handle these and provide user-friendly feedback.

始终考虑决策点：如果数量超过剩余座位怎么办？如果输入了无效的票型怎么办？使用条件语句处理这些情况并提供用户友好的反馈。

5. Visualising Logic with Flowcharts | 使用流程图可视化逻辑

Flowcharts translate pseudocode into a visual diagram that examiners often expect you to draw or interpret. Use standard symbols: ovals for start/end, parallelograms for input/output, rectangles for processes, diamonds for decisions, and arrows for flow.

流程图将伪代码转化为考官常常期望你绘制或解读的可视化图表。使用标准符号：椭圆表示开始/结束，平行四边形表示输入/输出，矩形表示处理，菱形表示决策，箭头表示流向。

Sketch a high-level chart showing the main loop, and then expand each decision block. This method helps you verify that your algorithm covers all paths, including error exits. Even a rough hand-drawn sketch in an exam gains marks for structure and completeness.

绘制一个展示主循环的高层流程图，然后展开每个决策块。这种方法有助于验证算法覆盖了所有路径，包括错误出口。即使在考试中粗略手绘的草图也会因结构和完整性而得分。

6. Selecting Appropriate Data Structures | 选择合适的数据结构

AS case studies often involve lists of items – for instance, multiple movies with different seat capacities. You may need a 1D array to store movie names and a parallel array for available seats. Alternatively, a 2D array could store movie, seat type, and price.

AS 案例分析通常涉及项目列表——例如，多部电影具有不同的座位容量。你可能需要一个一维数组存储电影名称，并用一个并行数组存储可用座位。或者，二维数组可以存储电影、座位类型和价格。

If the system requires persistent storage, text file handling may be required. You can read initial data from a file and write updated availability at the end. Always consider the need to search, sort, or update records when choosing an array structure.

如果系统需要持久存储，可能涉及文本文件处理。你可以从文件读取初始数据，并在结束时写入更新后的可用座位。在选择数组结构时，始终考虑搜索、排序或更新记录的需求。

For the ticket booking example, a simple array seatsLeft[1:5] could hold remaining seats for five movies. This keeps the design manageable and demonstrates indexing and iteration clearly.

对于电影票预订示例，一个简单的数组 seatsLeft[1:5] 可以存储五部电影的剩余座位。这使得设计易于管理，并清晰地展示了索引和迭代。

7. Developing a Test Strategy | 制定测试策略

Testing proves your algorithm works correctly. Design test cases covering normal, boundary, and erroneous data. Normal data: a standard booking of 2 normal tickets. Boundary data: booking exactly all remaining seats, or 0 tickets. Erroneous data: negative quantity, invalid seat type, or non-numeric input.

测试证明算法运行正确。设计测试用例，覆盖正常、边界和错误数据。正常数据：预订 2 张普通票。边界数据：预订恰好所有剩余座位，或 0 张票。错误数据：负数数量、无效座位类型或非数值输入。

Document expected outcomes before running tests. For each input set, predict the output and final seat count. A test table helps organize this process:

在运行测试前记录预期结果。对于每组输入，预测输出和最终座位计数。测试表有助于组织这一过程：

Test Type	Input	Expected Output
Normal	Movie A, Normal, 2	Total: £20, Seats left: 98
Boundary	Movie A, VIP, 100 (all seats)	Total: £1500, Seats left: 0
Erroneous	Movie A, Student, 1	Error: Invalid seat type

Use trace tables for logic-heavy algorithms to track variable changes step by step. This debugging technique is highly valued in CAIE mark schemes.

对逻辑密集的算法使用跟踪表，逐步追踪变量变化。这种调试技术在 CAIE 评分标准中很受重视。

8. Walkthrough: Complete Example – Movie Ticket Booking | 实战演练：完整案例——电影票预订

Let us consolidate the concepts into a single cohesive solution. The scenario: A cinema has five movies, each with 100 seats. Two seat types ‘N’ (Normal, £10) and ‘V’ (VIP, £15). The program allows repeated bookings until the user chooses to exit or all seats for a selected movie are sold. It outputs the total cost after each valid booking.

让我们将这些概念整合到一个连贯的解决方案中。场景：电影院有五部电影，每部 100 个座位。两种座位类型 ‘N’（普通，£10）和 ‘V’（VIP，£15）。程序允许重复预订，直到用户选择退出或所选电影的座位全部售罄。每次有效预订后输出总费用。

Variable table:

seatsRemaining[1:5] : ARRAY OF INTEGER (initialised to 100)
movieIndex : INTEGER
seatType : CHAR
qty : INTEGER
price : REAL
totalCost : REAL

Pseudocode:

FOR i ← 1 TO 5
    seatsRemaining[i] ← 100
NEXT i

REPEAT
    OUTPUT "Enter movie number (1-5) or 0 to quit:"
    INPUT movieIndex
    IF movieIndex = 0 THEN
        OUTPUT "Goodbye"
    ELSE
        IF movieIndex < 1 OR movieIndex > 5 THEN
            OUTPUT "Invalid movie number"
        ELSE
            OUTPUT "Enter seat type (N/V):"
            INPUT seatType
            IF seatType ≠ 'N' AND seatType ≠ 'V' THEN
                OUTPUT "Invalid seat type"
            ELSE
                OUTPUT "Enter quantity:"
                INPUT qty
                IF qty ≤ 0 OR qty > seatsRemaining[movieIndex] THEN
                    OUTPUT "Invalid quantity or not enough seats"
                ELSE
                    IF seatType = 'N' THEN
                        price ← 10
                    ELSE
                        price ← 15
                    ENDIF
                    totalCost ← price * qty
                    seatsRemaining[movieIndex] ← seatsRemaining[movieIndex] - qty
                    OUTPUT "Booking confirmed. Total cost: £", totalCost
                    OUTPUT "Seats left for movie ", movieIndex, ": ", seatsRemaining[movieIndex]
                ENDIF
            ENDIF
        ENDIF
    ENDIF
UNTIL movieIndex = 0 OR AllSeatsSold()

Define a function AllSeatsSold() that returns TRUE if every element of seatsRemaining is 0. This modularity improves readability and reusability.

定义一个函数 AllSeatsSold()，如果 seatsRemaining 的每个元素均为 0 则返回 TRUE。这种模块化提高了可读性和可重用性。

The solution demonstrates input validation, arithmetic operations, array updates, and loop control. Examiners expect you to present such structured pseudocode, clearly indented, with comments if helpful.

该解决方案演示了输入验证、算术运算、数组更新和循环控制。考官期望你呈现这样的结构化伪代码，清晰缩进，并在有帮助时添加注释。

9. Common Pitfalls and Debugging Tips | 常见陷阱与调试技巧

Students often forget to re-initialise variables inside loops, leading to incorrect totals. Another common mistake is off-by-one errors when iterating through arrays – always check that your loop counters match the declared bounds (e.g., 1 to 5 inclusive).

学生经常忘记在循环内重新初始化变量，导致错误的总计。另一个常见错误是在遍历数组时发生“差一错误”——始终检查循环计数器是否与声明的边界匹配（例如，1 到 5 含边界）。

Also, neglecting to handle invalid data types can cause runtime errors. In pseudocode, specify type checks or use TRY...EXCEPT if your syllabus allows. Always test extreme values and unexpected inputs to ensure robustness.

此外，忽略无效数据类型处理可能导致运行时错误。在伪代码中，指定类型检查或如果教学大纲允许，使用 TRY...EXCEPT。始终测试极值和意外输入以确保健壮性。

When debugging, insert temporary OUTPUT statements to display variable values at critical points. This mirrors print-debugging in real programming and helps locate logic flaws quickly.

调试时，插入临时的 OUTPUT 语句在关键点显示变量值。这类似于真实编程中的打印调试，有助于快速定位逻辑缺陷。

10. Mark Scheme Insights and Answering Techniques | 评分标准解读与答题技巧

CAIE examiners award marks for correct algorithm design, appropriate use of constructs, and completeness of test plans. Ensure your pseudocode covers every requirement stated in the case study. Re-read the question to check for hidden tasks like saving data to a file or providing a summary report.

CAIE 考官对正确的算法设计、适当的结构使用和测试计划的完整性给予分数。确保你的伪代码覆盖案例分析中陈述的每个需求。重新阅读题目，检查是否有隐藏任务，例如将数据保存到文件或提供总结报告。

In written answers, explicitly mention data types, array dimensions, and loop termination conditions. Even if the question does not require a full flowchart, a quick sketch can clarify your logic and earn additional planning marks. Practice under timed conditions to balance detail with speed.

在书面答案中，明确提及数据类型、数组维度和循环终止条件。即使问题不要求完整的流程图，快速草图可以阐明逻辑并获得额外的规划分。在计时条件下练习，以平衡细节与速度。

11. Final Review and Exam Tips | 最终回顾与考试技巧

Before submitting, trace your algorithm with sample data to verify that all branches execute as intended. Check that variables are declared, constants are defined, and the output matches the specification. Use a consistent naming convention and keep pseudocode language-independent.

提交前，用示例数据跟踪你的算法，验证所有分支按预期执行。检查变量是否声明，常量是否定义，输出是否符合规范。使用一致的命名约定，并保持伪代码与语言无关。

Common topics in AS case studies include menu-driven programs, data validation, running totals, search operations, and file updates. Master these patterns so you can adapt them quickly to any scenario presented in the exam.

AS 案例分析中的常见主题包括菜单驱动程序、数据验证、累计总和、搜索操作和文件更新。掌握这些模式，以便在考试中快速适应任何场景。

Finally, remember that clarity is key. Use comments to explain non-obvious steps, and present your solution logically. With systematic practice, case study questions become an opportunity to showcase your computational thinking and score high marks.

最后，记住清晰是关键。使用注释解释不明显的步骤，并逻辑清晰地呈现你的解决方案。通过系统练习，案例分析题将成为你展示计算思维并获得高分的契机。

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

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

AS CAIE Computer Science: Case Study Practical Walkthrough | AS CAIE 计算机：案例分析实战演练