📚 Case Study Practice: Real-World Problem Solving | 案例分析实战演练
In AQA GCSE Computer Science, case studies are not just theoretical – they reflect real-world systems. Mastering case study analysis allows you to demonstrate your ability to apply computational thinking to practical situations. This article walks through a typical school library book borrowing system, covering all stages from problem decomposition to algorithm design, data structures, testing and evaluation.
在AQA GCSE计算机科学中，案例分析不仅限于理论，它们反映了真实世界的系统。掌握案例分析能让你展示将计算思维应用于实际情境的能力。本文通过一个典型的学校图书馆借阅系统，涵盖从问题分解、算法设计、数据结构、测试到评估的各个阶段。
1. Understanding the Case Study Scenario | 理解案例分析场景
The case study involves a school library that wants a computerised system to manage book borrowing. Students can borrow up to three books at a time, and each book has a unique ISBN, title, author and availability status. The system should allow searching for a book, borrowing a book if available, returning a book, and viewing a student's borrowed books. The librarian must also be able to add new books and view all overdue books.
案例涉及一个想要计算机化系统管理图书借阅的学校图书馆。学生一次最多可借三本书，每本书有唯一的ISBN、书名、作者和可借状态。系统应允许搜索图书、在有空时借阅、归还图书、查看学生已借图书。图书馆员还必须能添加新书并查看所有逾期图书。
2. Identifying Inputs, Outputs and Processes | 识别输入、输出和处理过程
Inputs include: student ID (to identify the borrower), book ISBN (to search or borrow), search queries, and book details when adding a new title. Outputs are confirmation messages, lists of books, error messages, and overdue reports. The main processes are: validating student and book data, checking borrowing limits, updating book availability status, calculating due dates (14 days from today), and generating overdue reports.
输入包括：学生ID（识别借阅者）、图书ISBN（用于搜索或借阅）、搜索查询，以及添加新书时的图书详细信息。输出是确认消息、图书列表、错误消息和逾期报告。主要处理过程有：验证学生和图书数据、检查借阅限制、更新图书可借状态、计算到期日（从当天起14天）以及生成逾期报告。
3. Decomposing the Problem | 问题分解
Breaking the system into smaller, manageable sub-problems makes it easier to design and implement. Key modules: user authentication, book search, borrow book, return book, manage catalogue (add/remove books), and overdue detection. Each module can be coded as a separate function or procedure, reducing complexity and making the code reusable.
将系统分解为更小、可管理的子问题使得设计和实现更加容易。关键模块有：用户身份验证、图书搜索、借阅图书、归还图书、管理目录（添加/删除图书）以及逾期检测。每个模块都可以作为独立的函数或过程编码，降低复杂度并使代码可重用。
4. Designing an Algorithm Using Pseudocode | 使用伪代码设计算法
Pseudocode helps you focus on logic without worrying about syntax. Below is the borrow book algorithm. It checks the student's current loans, searches for the book, verifies availability, updates records, and sets a due date.
伪代码帮助你专注于逻辑而无需担心语法。下面是借阅图书算法。它检查学生当前的借阅数，搜索图书，验证可借性，更新记录并设置到期日。
FUNCTION borrowBook(studentID, ISBN)
IF length(student.borrowedList) >= 3 THEN
RETURN "Borrowing limit reached"
ENDIF
book = searchBookByISBN(ISBN)
IF book = NULL THEN
RETURN "Book not found"
ENDIF
IF book.available = False THEN
RETURN "Book currently unavailable"
ENDIF
SET book.available = False
APPEND ISBN to student.borrowedList
SET dueDate = currentDate + 14 days
RETURN "Borrow successful. Due: " + dueDate
ENDFUNCTION
The algorithm uses a function searchBookByISBN that scans the book array. It returns the book record or NULL. After successful borrowing, the book's available flag is set to False and the ISBN is added to the student's loan list.
该算法使用函数searchBookByISBN扫描图书数组，返回图书记录或NULL。借阅成功后，图书的available标志设为False，ISBN被添加到学生的借阅列表。
5. Creating Flowcharts for Visual Representation | 创建流程图进行可视化表示
Flowcharts use standard symbols to represent the flow of an algorithm. They are especially useful when communicating ideas to non-programmers. Common symbols in a borrow book flowchart include ovals for start/end, parallelograms for input/output, rectangles for processes, and diamonds for decisions like 'book found?' and 'available?'.
流程图使用标准符号表示算法的流程。它们在向非编程人员传达想法时特别有用。借阅图书流程图中常见的符号包括：椭圆表示开始/结束，平行四边形表示输入/输出，矩形表示处理过程，菱形表示诸如“找到书了吗？”和“可借吗？”的决策。
| Shape | Meaning | 形状 |
|---|---|---|
| Oval | Start / End | 开始 / 结束 |
| Parallelogram | Input / Output | 输入 / 输出 |
| Rectangle | Process | 处理 |
| Diamond | Decision | 判断 |
You can draw the flowchart for the borrow book function, connecting the decisions 'Borrowing limit reached?', 'Book found?', and 'Available?' in sequence. Arrows show the flow, and the final process updates the data and displays the success message.
你可以画出借阅函数的流程图，依次连接决策“达到借阅上限了吗？”、“找到书了吗？”和“可借吗？”。箭头显示流程，最后的处理更新数据并显示成功消息。
6. Data Structures: Arrays and Records | 数据结构：数组和记录
Storing data efficiently is crucial. A book can be represented as a record with fields: ISBN (string), title (string), author (string), available (boolean). An array of such records holds the library catalogue. A student record can contain studentID, name, and an array borrowedBooks (max 3 strings).
高效存储数据至关重要。一本书可以表示为包含字段的记录：ISBN（字符串）、书名（字符串）、作者（字符串）、可借（布尔值）。这样的记录数组保存图书馆目录。学生记录可以包含学生ID、姓名和一个数组borrowedBooks（最多3个字符串）。
DECLARE bookRecord : ARRAY[0:n] OF {ISBN : STRING, title : STRING, author : STRING, available : BOOLEAN}
The array index can act as a simple way to locate a book when its ISBN is known. To search, you loop through the array comparing the ISBN field. If the list is large, a more efficient search method like binary search (after sorting by ISBN) can be considered.
数组索引可以作为得知ISBN时定位图书的简单方法。搜索时，循环遍历数组比较ISBN字段。如果列表很大，可以考虑更高效的搜索方法，如（按ISBN排序后）使用二分查找。
7. Implementing Data Validation | 实现数据验证
Data validation prevents incorrect data from corrupting the system. When a student enters their ID, the system must check it exists in the registered student list. ISBNs must be exactly 13 digits. A borrow request must confirm the student has fewer than three active loans. Additional validation includes ensuring dates are valid and not in the past.
数据验证可防止错误数据破坏系统。当学生输入ID时，系统必须检查它是否存在于注册学生列表中。ISBN必须恰好是13位数字。借阅请求必须确认学生当前借阅数少于3。其他验证包括确保日期有效且不是过去的日期。
For example, a length check on ISBN ensures the input string has length 13, and a presence check guarantees it is not empty. A range check on the number of borrowed books ensures it remains within 0–3.
例如，对ISBN的长度检查确保输入字符串长度为13，存在检查确保它不为空。对借阅数量的范围检查确保其保持在0-3之间。
8. File Handling: Reading and Writing Data | 文件处理：读写数据
Data must persist between program runs. In Python-like pseudocode, we can open a text file to read the catalogue on startup and write it back when a change occurs. For instance, reading book records line by line, splitting each line by comma, and constructing the array.
数据必须在程序运行之间持久保存。在类似Python的伪代码中，我们可以在启动时打开文本文件读取目录，并在发生更改时写回。例如，逐行读取图书记录，按逗号分割每行并构建数组。
OPEN "books.csv" FOR READ
WHILE NOT EOF
line = READLINE()
fields = SPLIT(line, ",")
book = {fields[0], fields[1], fields[2], BOOLEAN(fields[3])}
APPEND book TO catalogue
ENDWHILE
CLOSE "books.csv"
When a book is borrowed, the programme rewrites the entire file to reflect the updated availability. This approach is simple and works well for moderate amounts of data.
当图书被借出时，程序重写整个文件以反映更新后的可借性。这种方法简单，对于中等数据量效果良好。
9. Trace Tables for Algorithm Dry-Running | 用于算法跟踪的跟踪表
A trace table is a manual testing technique where you step through the code, recording the values of variables at each step. Given student S001 has already borrowed two books (ISBNs '9781234567890', '9789876543210'), and tries to borrow a third '9781111111111' that is available.
跟踪表是一种手动测试技术，你逐步走查代码，记录每一步变量的值。假设学生S001已借了两本书（ISBN '9781234567890', '9789876543210'），并尝试借第三本可借的书'9781111111111'。
| Line executed | student.borrowedList | book.available | Output |
|---|---|---|---|
| IF length >= 3 | [2 books] | - | - |
| Find book | [2 books] | True | - |
| IF available=False | [2 books] | True → condition false | - |
| SET available=False | [2 books] | False | - |
| APPEND ISBN | [3 books] | False | Success |
of >=3, a student could borrow four books. Trace tables catch such mistakes before coding.
这有助于识别逻辑错误。例如，如果限制检查错误地使用了>3而不是>=3，学生可能借到四本书。跟踪表在编码之前就能发现这类错误。
10. Error Handling and Testing | 错误处理与测试
A robust system must handle errors gracefully. Testing involves normal, boundary and erroneous data. A test plan table documents test ID, input, expected outcome and actual outcome.
健壮的系统必须优雅地处理错误。测试包括正常、边界和错误数据。测试计划表记录测试ID、输入、预期结果和实际结果。
- Normal test: Student with 2 books borrows an available book → Success.
- 正常测试：借有2本书的学生借阅一本可借书 → 成功。
- Boundary test: Student with exactly 3 books tries to borrow → Error 'limit reached'.
- 边界测试：刚好借满3本书的学生尝试借阅 → 错误“已达上限”。
- Non-existent ISBN entered, or already borrowed book requested → appropriate error message.
- 错误测试：输入不存在的ISBN，或请求已被借出的书 → 适当的错误消息。
Error handling code can include pre-condition checks at the start of each function, such as verifying the student ID is valid before proceeding. Using TRY...CATCH constructs (if available) for file operations can prevent crashes if the file is missing.
错误处理代码可以在每个函数开始时包括前置条件检查，例如在进行之前验证学生ID有效。对文件操作使用TRY...CATCH结构（如果可用）可以防止因文件缺失而崩溃。
11. Evaluating the Solution and Improvements | 评估解决方案与改进
The array-based solution works well for a small school library, but it has limitations. Searching through an unsorted array is linear O(n) – slow for thousands of books. File handling by rewriting the entire file can be inefficient. Future improvements could include using a database (SQL) for persistent storage, implementing a hash table or binary search tree for faster lookups, and adding a graphical user interface (GUI) for ease of use.
基于数组的解决方案对于小型学校图书馆很有效，但有局限性。在未排序数组中搜索是线性O(n)——对于数千本书会很慢。重写整个文件的文件处理可能低效。未来的改进可以包括使用数据库（SQL）进行持久存储，实现哈希表或二叉搜索树以加速查找，以及添加图形用户界面（GUI）以提高易用性。
Additionally, security features such as password protection for librarian functions and logging all transactions would make the system more professional. The evaluation should always consider trade-offs between simplicity and scalability.
此外，安全特性如为图书馆员功能设置密码保护以及记录所有交易将使系统更专业。评估应始终考虑简单性与可扩展性之间的权衡。
Published by TutorHao | Computer Science Revision Series | aleveler.com
更多咨询请联系16621398022（同微信）
或截图后用「扫一扫 → 相册」选择本图