📚 School Library System Upgrade: A Case Study | 学校图书馆系统升级案例分析实战演练
In Cambridge Year 8 Computer Science, mastering the art of case study analysis is a crucial skill. It bridges theoretical concepts with real-world problem-solving. This article walks you through a complete case study of upgrading a school's outdated library management system, demonstrating how to apply computational thinking, system design, and algorithm development. By following each step, you will learn to dissect a problem, gather requirements, model data flows, design solutions, implement pseudocode, test, evaluate, and reflect on ethical considerations.
在剑桥八年级计算机科学中，掌握案例分析的艺术是一项关键技能。它将理论概念与实际问题解决有机地结合起来。本文将通过一个完整的案例——升级一所学校过时的图书馆管理系统，为你演示如何应用计算思维、系统设计和算法开发。通过跟随每一步，你将学会如何剖析问题、收集需求、建模数据流、设计解决方案、实现伪代码、测试、评估并反思其中的伦理考量。
1. Understanding the Problem | 理解问题
The school library houses over 5,000 books and serves 800 students. The current system, built on a spreadsheet, runs painfully slowly during lunch breaks when most borrowing occurs. Librarians report that records sometimes get corrupted, losing borrow history. Students often wait in long queues, and some books are misplaced because the manual return labeling is unclear. The core problem is poor performance and data reliability under peak load.
学校图书馆藏有5000多册图书，服务于800名学生。现行系统建立在电子表格之上，在借阅高峰的午餐时段运行极为缓慢。图书管理员反映，记录有时会损坏，导致借阅历史丢失。学生们经常排长队等候，并且由于手工归还标记不清晰，一些书籍会被放错位置。核心问题是高峰负荷下的性能低下和数据可靠性差。
2. Gathering Requirements | 收集需求
Through interviews with the head librarian and student representatives, we identified key functional requirements: the system must allow fast check-out and check-in, maintain accurate book availability, and generate overdue notices. Non-functional requirements include response time under 2 seconds per transaction and the ability to handle 50 simultaneous users during peaks. It must also back up data daily to prevent loss.
通过与图书馆馆长和学生代表的访谈，我们确定了关键的功能需求：系统必须支持快速的借出手续和归还手续，维护准确的图书可借状态，并生成逾期通知。非功能性需求包括每笔交易响应时间低于2秒，以及能在高峰期处理50个并发用户。系统还必须每日备份数据以防丢失。
3. Identifying Stakeholders | 识别利益相关者
Stakeholders are anyone affected by the system. Primary stakeholders are students and library staff who interact with the system directly. Secondary stakeholders include teachers who depend on library resources for lessons, the school administration that funds the upgrade, and the IT support team responsible for maintenance. Each group has distinct concerns: speed for students, reliability for librarians, cost for administrators, and maintainability for IT.
利益相关者是任何受系统影响的人。主要利益相关者是直接与系统互动的学生和图书馆工作人员。次要利益相关者包括依赖图书馆资源授课的教师、资助升级的学校管理层以及负责维护的IT支持团队。每一群体都有不同的关注点：学生关注速度，图书馆员关注可靠性，管理员关注成本，IT人员关注可维护性。
4. Modeling the Current System | 建模当前系统
We created a data flow diagram (DFD) of the existing manual-spreadsheet hybrid. A student hands a book to the librarian, who manually types the book ID and student ID into the spreadsheet. The spreadsheet calculates due dates but often freezes. A physical card catalog is still used as a backup. The process reveals heavy reliance on a single slow file, with no validation, leading to duplicate entries and lost records.
我们为现有的人工-电子表格混合系统创建了数据流图。学生将书交给馆员，馆员手动将图书ID和学生ID输入电子表格。电子表格会计算到期日，但经常冻结。纸质卡片目录仍被用作备份。该过程揭示了对单一缓慢文件的高度依赖，缺乏验证，从而导致重复条目和记录丢失。
5. Data Flow and Storage | 数据流与存储
For the new system, data flow will be streamlined. A central database replaces the spreadsheet. When a student checks out a book, the system reads the barcode, validates the student ID, updates the book status to 'borrowed', and records a new loan entry. Data storage tables include Books (BookID, Title, Author, ISBN, Status), Students (StudentID, Name, Class), and Loans (LoanID, BookID, StudentID, DateOut, DateDue, DateReturned).
在新系统中，数据流将得到精简。一个中央数据库将取代电子表格。当学生借出一本书时，系统读取条形码，验证学生ID，将图书状态更新为“已借出”，并记录一条新的借阅条目。数据存储表包括图书（图书ID、书名、作者、ISBN、状态）、学生（学生ID、姓名、班级）和借阅（借阅ID、图书ID、学生ID、借出日期、到期日期、归还日期）。
6. Designing the Solution – Algorithms | 解决方案设计 – 算法
We need a clear algorithm for borrowing a book. Steps: 1. Scan book barcode; 2. If book status is 'available', proceed; else show error. 3. Scan student ID; 4. Validate student is active; if not, deny. 5. Create a new loan record with today's date and set due date to +14 days. 6. Update book status to 'borrowed'. 7. Display confirmation. This simple sequence uses sequence, selection, and iteration implicitly in the overall system.
我们需要一个清晰的借书算法。步骤：1. 扫描图书条形码；2. 如果图书状态为“可借”，继续；否则显示错误。3. 扫描学生ID；4. 验证学生为在册状态；若不是，则拒绝。5. 以当天日期创建新借阅记录，并将到期日设为 +14 天。6. 将图书状态更新为“已借出”。7. 显示确认信息。这一简单序列隐含地运用了顺序、选择和循环结构。
7. Choosing Appropriate Data Types | 选择适当的数据类型
ng due to dashes. Status is a Boolean (TRUE = available, FALSE = borrowed). DateOut should be a date type, not a string, to allow easy calculation of overdue fines. Choosing an integer for BookID saves memory compared to a string. For example, storing 5,000 BookIDs as 4-byte integers uses only 20 KB, whereas as 8-character strings it would need about 40 KB.
选择正确的数据类型可以提高效率并防止错误。图书ID可以是整数（例如10245）。书名必须为字符串。由于带有连字符，ISBN是字符串。状态是布尔型（TRUE = 可借，FALSE = 已借出）。借出日期应为日期类型，而非字符串，以便轻松计算逾期罚款。与字符串相比，为图书ID选择整数可节省内存。例如，将5000个图书ID存储为4字节整数仅占用20 KB，而存储为8字符字符串则大约需要40 KB。
Memory saved ≈ 5000 × (8 - 4) bytes = 20 000 bytes = 20 KB
8. Implementing with Pseudocode | 使用伪代码实现
Pseudocode bridges the gap between algorithm design and actual coding. Here is a pseudocode snippet for the check-out function:
伪代码弥合了算法设计与实际编码之间的鸿沟。以下是借出函数的伪代码片段：
PROCEDURE CheckOut(BookID, StudentID)
IF BookStatus(BookID) = 'Available' AND StudentActive(StudentID) THEN
CreateLoan(BookID, StudentID, Today, Today+14)
SetBookStatus(BookID, 'Borrowed')
DISPLAY 'Success'
ELSE
DISPLAY 'Cannot borrow'
ENDIF
END PROCEDURE
This structured English makes the logic transparent, using indentation to show blocks, and can be easily translated into Python or Scratch.
这种结构化的英语使逻辑透明，利用缩进显示代码块，并且可以轻松地转换为 Python 或 Scratch。
9. Testing the System | 测试系统
A robust test plan ensures the system works under various conditions. Test cases include: normal borrow (book available, valid student), borrow a book already on loan (expect error), borrow with invalid student ID (deny), return a book on time, return a book late (calculate fine), and concurrent borrows by 50 users. We can record results in a table:
一个健壮的测试计划可确保系统在各种条件下都能正常工作。测试用例包括：正常借阅（图书可借，学生有效）、借阅已借出的图书（预期报错）、使用无效学生ID借阅（拒绝）、按时归还图书、逾期归还图书（计算罚款）以及50个用户并发借阅。我们可以将结果记录在表格中：
| Test ID | Description | Expected Outcome | Actual |
|---|---|---|---|
| TC01 | Borrow available book | Loan created, status 'borrowed' | Pass |
| TC02 | Borrow already borrowed book | Error 'Not available' | Pass |
| TC03 | Return after due date | Fine calculated at £0.10/day | Pass |
10. Evaluating the Solution | 评估解决方案
After testing, we evaluate against the requirements. The new system processes a transaction in 0.8 seconds, well under the 2-second target. Concurrency tests show stable performance with up to 60 simultaneous users. Data integrity is ensured through validation rules and daily automated backups. Users reported a much smoother experience. However, we identified a weakness: the barcode scanner occasionally misreads damaged labels, requiring a manual fallback.
测试之后，我们对照需求进行评估。新系统每笔交易处理时间为0.8秒，远低于2秒的目标。并发测试显示，在多达60个同时用户的情况下性能稳定。通过验证规则和每日自动备份，确保了数据完整性。用户报告称体验流畅了许多。然而，我们发现了一个弱点：条形码扫描器偶尔会误读损坏的标签，需要一个手动回退方案。
11. Considering Security and Ethics | 考虑安全与伦理
Student borrowing data is personal information and must be protected. The system needs role-based login so that only librarians can modify loan records, while students can only view their own accounts. Passwords must be hashed and stored securely. Data disposal policies should ensure that records of graduated students are anonymized after a set period. Ethical design also includes making the interface accessible to students with visual impairments, following Cambridge's emphasis on responsible computing.
学生的借阅数据属于个人信息，必须受到保护。系统需要基于角色的登录，以便只有图书馆员能够修改借阅记录，而学生只能查看自己的账户。密码必须经过哈希处理并安全存储。数据定期销毁政策应确保已毕业学生的记录在设定期间后被匿名化处理。符合伦理的设计还包括使界面可供视力障碍学生使用，这遵循了剑桥课程对负责任计算的强调。
12. Reflection and Improvement | 反思与改进
This case study highlighted how computational thinking breaks down a messy real-world problem into manageable components. Future improvements could include a machine learning module that predicts book demand based on past borrowing patterns, or a mobile app allowing students to renew books remotely. The iterative nature of design means we always return to the stakeholders for feedback, ensuring the solution continuously evolves.
本案例研究凸显了计算思维如何将一个混乱的现实问题分解为可管理的组件。未来的改进可以包括一个机器学习模块，根据过去的借阅模式预测图书需求，或者一个允许学生远程续借的移动应用。设计的迭代本质意味着我们始终要回到利益相关者那里获取反馈，确保解决方案持续演进。
Published by TutorHao | Computer Science Revision Series | aleveler.com
更多咨询请联系16621398022（同微信）
或截图后用「扫一扫 → 相册」选择本图