Case Study Practice for Year 10 AQA Computer Science | 案例分析实战演练

📚 Case Study Practice for Year 10 AQA Computer Science | 案例分析实战演练

Case study questions are a central part of the AQA GCSE Computer Science exam (Paper 2). They require you to apply your computational thinking and programming knowledge to a realistic scenario. In this article, we will walk through a structured approach for tackling case studies, using a cinema booking system as our main example. You will learn how to break down a problem, identify requirements, design algorithms, choose data structures, and write effective test plans.

案例分析题是 AQA GCSE 计算机科学考试（试卷2）的核心部分。它要求你将计算思维和编程知识应用到一个真实的场景中。本文将通过一个电影院订票系统作为主要示例，带你一步步掌握处理案例分析的结构化方法。你将学会如何分解问题、确定需求、设计算法、选择数据结构以及编写有效的测试计划。

1. Why Case Studies Matter | 为什么案例分析如此重要

Case studies test your ability to think like a software developer. You are given a description of a problem and must suggest a suitable digital solution. Examiners look for evidence of analysis, design, implementation planning, and evaluation. By practising case studies, you build the skills needed to answer longer, scenario-based questions confidently.

案例分析考察的是你像软件开发者一样思考的能力。你会得到一个问题的描述，并需要提出合适的数字化解决方案。考官看重的是分析、设计、实施规划和评估的证据。通过练习案例分析，你可以建立自信，从容应对基于场景的长篇问题。

2. Reading and Decomposing the Scenario | 阅读并分解场景

Start by reading the case study twice. First, get a general sense of the system’s purpose. Second, underline key nouns (potential classes, variables) and verbs (possible functions, processes). Ask yourself: what needs to go into the system, and what must come out? For a cinema booking system, nouns might include ‘film’, ‘screen’, ‘seat’, ‘customer’, ‘booking’; verbs could be ‘search films’, ‘select seat’, ‘make payment’, ‘print ticket’.

首先，将案例阅读两遍。第一遍，整体了解系统的目的。第二遍，划出关键名词（潜在的类、变量）和动词（可能的功能、过程）。问自己：什么需要进入系统，什么必须从系统输出？对于电影院订票系统，名词可能包括“影片”、“放映厅”、“座位”、“顾客”、“预订”；动词可能是“搜索影片”、“选择座位”、“支付”、“打印票券”。

3. Identifying Stakeholders and Functional Requirements | 确定利益相关者与功能需求

Who will use the system? In a cinema setting, stakeholders are customers, cinema staff, and possibly managers. Each group has different needs. Customers want to browse films, reserve seats, and pay online. Staff need to check in customers and monitor screen occupancy. Managers require sales reports. List the functional requirements in plain English, then refine them into clear system tasks.

谁会使用该系统？在电影院场景中，利益相关者包括顾客、影院工作人员，可能还有经理。每个群体有不同的需求。顾客希望浏览影片、预订座位并在线支付。工作人员需要为顾客检票并监控放映厅占有率。经理需要销售报告。用通俗的语言列出功能需求，然后将其细化为清晰的系统任务。

4. Designing Inputs and Outputs | 设计输入和输出

Map out exactly what data enters the system and what is displayed or produced. Inputs for our cinema system could be: film title, date and time, customer name, email, seat number, payment details. Outputs might include: on-screen seat availability grid, booking confirmation, e-ticket with QR code, and daily revenue summary for the manager.

精确地规划出哪些数据进入系统，哪些数据被显示或生成。我们影院系统的输入可能包括：影片名称、日期和时间、顾客姓名、邮箱、座位号、支付信息。输出可能包括：屏幕上的座位可用性网格、预订确认信息、带二维码的电子票券，以及管理员的每日收入汇总。

5. Designing Data Structures and Storage | 设计数据结构与存储

Think about how data will be organised in your program. A 2D array could represent the seat layout for a screen, with values ‘A’ (available), ‘S’ (selected), or ‘B’ (booked). Records (or dictionaries) can store film details and bookings. A simple file or database table might hold user accounts. Below is a table showing a record structure for a booking.

思考数据在程序中将如何组织。一个二维数组可以表示影厅的座位布局，其值可以是“A”（可用）、“S”（已选）或“B”（已预订）。记录（或字典）可以存储影片详情和预订信息。一个简单的文件或数据库表可以保存用户账户。下表展示了一条预订记录的结构。

Field	Data Type	Example
bookingID	Integer	1042
customerName	String	“Amina Patel”
screeningDate	Date	2025-05-15
seatRow	Integer	3
seatNumber	Integer	8

6. Algorithm Design – Flowcharts | 算法设计 – 流程图

Flowcharts help visualise the logic of a process. For the seat booking process, a flowchart might start with ‘Select film and showtime’, then ‘Display seat plan’, ‘Customer picks seat’, ‘Check if seat available’. If available, proceed to payment; otherwise, display error and loop back. Use standard symbols: oval for start/end, rectangles for processes, diamonds for decisions. Keep it neat and uncluttered.

流程图有助于可视化过程的逻辑。对于座位预订流程，流程图可以从“选择影片和放映时间”开始，然后“显示座位图”，“顾客选择座位”，“检查座位是否可用”。如果可用，则进入支付；否则显示错误并循环回去。使用标准符号：椭圆形表示开始/结束，矩形表示过程，菱形表示决策。保持整洁、不杂乱。

7. Algorithm Design – Pseudocode | 算法设计 – 伪代码

Translate your flowchart into clear, exam-style pseudocode. Use indentation and keywords like INPUT, OUTPUT, IF…THEN…ELSE, WHILE…ENDWHILE. Here is a snippet for checking seat availability and confirming a booking:

将你的流程图转化为清晰的、符合考试风格的伪代码。使用缩进和关键字，如 INPUT、OUTPUT、IF…THEN…ELSE、WHILE…ENDWHILE。以下是检查座位可用性并确认预订的一段代码片段：

seatPlan ← ARRAY[1..10,1..15] OF CHAR
OUTPUT “Enter row and seat number:”
INPUT row, seat
IF seatPlan[row, seat] = ‘A’ THEN
  seatPlan[row, seat] ← ‘B’
  OUTPUT “Booking confirmed”
ELSE
  OUTPUT “Seat not available. Please choose again.”
ENDIF

8. Robustness and Validation | 健壮性与数据验证

Programs must handle unexpected inputs gracefully. For a booking system, validation rules include: row must be 1–10, seat number 1–15, name must not be empty, email must contain ‘@’. Use presence checks, range checks, and format checks. Without validation, the system could crash or accept corrupt data. Describe how you would test these rules in your case study answer.

程序必须优雅地处理意外输入。对于订票系统，验证规则包括：排数必须在1–10之间，座位号1–15，姓名不能为空，邮箱必须包含“@”。使用存在性检查、范围检查和格式检查。如果没有验证，系统可能崩溃或接受损坏的数据。在案例分析答案中，描述你将如何测试这些规则。

9. Planning a Testing Strategy | 规划测试策略

Testing is not an afterthought — it should be part of your design. Produce a test table with columns: Test ID, Test Data, Expected Outcome, Actual Outcome. Include normal, boundary, and erroneous data. For seat booking, a boundary test would use row=1 and row=10, seat=1 and seat=15; an erroneous test might enter row=0 or seat=20. Explain how you would refine the solution based on test results.

测试不是事后才考虑的——它应该是设计的一部分。编制一个测试表，包含列：测试编号、测试数据、预期结果、实际结果。包括正常数据、边界数据和错误数据。对于座位预订，边界测试可以使用行=1和行=10，座位=1和座位=15；错误测试可能输入行=0或座位=20。解释你将如何根据测试结果优化解决方案。

10. Evaluating the Solution | 评估解决方案

In an evaluation, discuss strengths and limitations. Cinema strengths might include user-friendly seat selection grid, instant confirmation, and reduced manual workload. Limitations could involve internet dependency, potential for double-bookings under high traffic, or accessibility issues. Suggest improvements: a waiting list feature, integration with a mobile app, or loyalty points. AQA examiners reward critical reflection.

在评估部分，讨论优点和局限性。影院系统的优点可能包括用户友好的选座网格、即时确认以及减少人工工作量。局限性可能涉及对互联网的依赖、高流量下可能发生重复预订，或者可访问性问题。提出改进建议：候补名单功能、与移动应用程序的集成，或忠诚度积分。AQA 考官会奖励批判性的反思。

11. Common Exam Pitfalls | 考试中常见的陷阱

Many students lose marks by not reading the question carefully, offering a generic solution instead of tailoring it to the case study, or forgetting to use the correct data structures. Another pitfall is writing vague pseudocode without specific variable names. Always refer back to the scenario: if the case study mentions a loyalty programme, your solution must include it. Time management is crucial — practise writing concise yet complete answers.

许多学生丢分的原因是没有仔细阅读题目，给出了一个通用的解决方案而不是针对案例量身定制，或者忘记了使用正确的数据结构。另一个陷阱是编写了模糊的伪代码，没有具体的变量名。始终回顾场景：如果案例提到了忠诚度计划，你的解决方案就必须包含它。时间管理至关重要——练习写出简洁而完整的答案。

12. Full Practice Scenario: CineFlix Booking System | 完整练习场景：CineFlix 订票系统

Let’s apply everything to a complete mini case study. CineFlix is a new multiplex cinema. It needs a system where customers can view the week’s showtimes, select a film, see available seats in a 12×18 grid, and purchase up to 4 tickets per transaction. The system must apply a 10% discount when 3 or more tickets are bought together. Staff require a separate interface to print a daily schedule.

让我们将所有内容应用到一个完整的小型案例研究中。CineFlix 是一家新的多厅影院。它需要一个系统，让顾客可以查看一周的放映时间表、选择影片、在 12×18 的网格中查看可用座位，并且每笔交易最多购买 4 张票。当一次性购买 3 张或更多票时，系统必须打九折。工作人员需要一个单独的界面来打印每日排片表。

Suggested approach: Represent the seat grid as a 2D array of Booleans (True = available). Use a function to calculate total cost. Extract discount logic into a procedure. For the staff menu, use a simple text-based output. Write pseudocode for the main menu and the booking loop. Include validation for seat selection and transaction limit. Sketch a test plan covering zero tickets, maximum 4 tickets, 3-ticket discount, and boundary seat positions. Evaluate the prototype, noting that a real system would need persistent storage and a more secure payment module.

建议的方法：将座位网格表示为一个布尔值的二维数组（True = 可用）。使用一个函数计算总费用。将折扣逻辑提取到一个过程中。对于工作人员菜单，使用简单的文本输出。为主菜单和预订循环编写伪代码。包括对座位选择和交易限制的验证。草拟一个测试计划，涵盖零张票、最多 4 张票、3 张票的折扣以及边界座位位置。评估原型，指出真实系统需要持久存储和更安全的支付模块。

---

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

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