Case Study in Action: Designing a Library Management System | 案例实战：设计一个图书馆管理系统

📚 Case Study in Action: Designing a Library Management System | 案例实战：设计一个图书馆管理系统

Case studies are one of the most effective ways to learn computer science. Instead of just memorizing facts, you get to apply your knowledge to a realistic situation, just like a real software developer would. In this article, we will walk through a practical case study step by step, designing a simple library management system. You will see how the key concepts you learn in Year 8 OCR Computer Science — such as abstraction, decomposition, algorithms, data structures, and testing — all come together to create a real-world solution.

案例分析是学习计算机科学最有效的方法之一。你不必死记硬背知识点，而是可以像真正的软件开发人员一样，将所学知识应用于真实场景。在本文中，我们将一步步经历一个实践案例，设计一个简单的图书馆管理系统。你会看到Year 8 OCR计算机科学课程中的关键概念——如抽象化、分解、算法、数据结构和测试——如何全部协同工作，创造出解决现实问题的方案。

1. Understanding the Case Study | 理解案例背景

Imagine that your school library wants a digital system to manage books and borrowers. At present, they use paper cards and a spreadsheet, which makes searching, borrowing, and returning books slow and error-prone. The librarian has asked you to design a program that can store information about books, keep track of who has borrowed a book, and automatically calculate return due dates. The system should also be able to search for a book by title or author and check its availability.

假设你学校的图书馆想要一个数字系统来管理图书和借阅者。目前他们使用纸质卡片和电子表格，这使得查找、借阅和归还书籍变得缓慢且容易出错。图书管理员请求你设计一个程序，能够存储图书信息，追踪谁借了哪本书，并自动计算应归还日期。该系统还应能通过书名或作者搜索图书，并检查其是否可借。

This is a classic example of a problem that requires computational thinking. Before writing a single line of code, we need to break the problem down (decomposition), focus on what is important (abstraction), and come up with a step-by-step plan. The case study will follow the software development life cycle: requirements, design, implementation, testing, and evaluation.

这是一个需要计算思维的经典问题案例。在编写任何代码之前，我们需要将问题分解（分解法），聚焦于重要信息（抽象化），并制定一步步的计划。本案例分析将遵循软件开发生命周期：需求、设计、实施、测试和评估。

2. Requirements Analysis | 需求分析

Let’s list what the system must do. These are the functional requirements:

让我们列出系统必须做什么。以下是功能性需求：

Add new books to the catalogue (including title, author, ISBN, genre).
Register new library members.
Allow a member to borrow a book (mark it as unavailable, record due date).
Allow a member to return a book (mark it as available, remove borrowing record).
Search for a book by title or author.
Display a list of books currently borrowed by a member.
Calculate fine if book is returned late (e.g., 10 pence per day).

添加新书到目录（包括书名、作者、ISBN、类型）。
注册新图书馆成员。
允许成员借阅图书（标记为不可借，记录应还日期）。
允许成员归还图书（标记为可借，删除借阅记录）。
按书名或作者搜索图书。
显示某成员当前借阅的图书列表。
如果超期归还，计算罚款（例如每天10便士）。

We also need non-functional requirements: the system should be easy to use, respond quickly to searches, and protect personal data. Data must be saved between sessions (we can use a file).

我们还需要非功能性需求：系统应易于使用，搜索响应迅速，并保护个人数据。数据必须在会话间保存（我们可以使用文件）。

3. Decomposition and Abstraction | 分解与抽象

Decomposition means breaking a big problem into smaller, manageable parts. For our library system, we can identify these modules: Book Management, Member Management, Borrowing & Returning, Search, and Fine Calculation. Abstraction means focusing on the essential details and ignoring irrelevant ones. For a book, the essential attributes are title, author, ISBN, genre, and whether it is available. For a member, we need name, member ID, and contact details, but not things like favourite colour, because they are not relevant to the library functions.

分解意味着将一个大问题拆分成更小、更易管理的部分。对于我们的图书馆系统，可以识别出这些模块：图书管理、成员管理、借阅与归还、搜索和罚款计算。抽象意味着聚焦于必要细节，忽略无关信息。对于一本书，必要属性是书名、作者、ISBN、类型以及是否可借。对于成员，我们需要姓名、会员ID和联系方式，而不需要诸如最喜欢的颜色等，因为它们与图书馆功能无关。

Entity	Essential Data
Book	Title, Author, ISBN, Genre, Available (yes/no)
Member	Member ID, Name, Class, Email
Borrow	ISBN, Member ID, Borrow Date, Due Date

实体	必要数据
图书	书名、作者、ISBN、类型、是否可借
成员	会员ID、姓名、班级、邮箱
借阅	ISBN、会员ID、借出日期、应还日期

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

Designing the user interaction helps clarify how data will flow through the system. We can list sample inputs and expected outputs for each function.

设计用户交互有助于理清数据如何流经系统。我们可以为每个功能列出示例输入和预期输出。

For searching a book, the input could be a keyword typed by the user, and the output is a list of matching books with their availability status. For borrowing, the input is the member’s ID and the book’s ISBN; the output is a confirmation with the due date.

对于搜索图书，输入可以是用户输入的关键词，输出是匹配的图书列表及其可借状态。对于借阅，输入是会员ID和图书ISBN；输出是带应还日期的确认信息。

We must also consider validation: what if the ISBN is not found? The system should display a friendly error message. What if a book is already on loan? The system should inform the user that the book is currently unavailable.

我们还必须考虑验证：如果未找到ISBN怎么办？系统应显示友好的错误消息。如果图书已借出怎么办？系统应告知用户该书当前不可借。

5. Data Structures in Practice | 实践中的数据结构

In Python, we can represent a book using a dictionary, and the collection of books as a list of dictionaries. This allows us to loop through and search easily. Let’s see a concrete example:

在Python中，我们可以用字典表示一本书，用字典列表表示图书集合。这样便于循环和搜索。我们来看一个具体例子：

English: books = [{‘title’: ‘The Hobbit’, ‘author’: ‘Tolkien’, ‘isbn’: ‘978-0-26110-200-2’, ‘genre’: ‘Fantasy’, ‘available’: True}, … ]

中文：书籍 = [{‘书名’: ‘霍比特人’, ‘作者’: ‘托尔金’, ‘isbn’: ‘978-0-26110-200-2’, ‘类型’: ‘奇幻’, ‘可借’: True}, … ]

Members can be stored similarly. The borrowing records can be a list of dictionaries where each record links a member ID, book ISBN, borrow date, and due date. The due date could be calculated as borrow date plus 14 days using the datetime module.

成员可以类似地存储。借阅记录可以是字典列表，每条记录关联会员ID、图书ISBN、借出日期和应还日期。应还日期可以通过借出日期加14天计算，使用datetime模块。

6. Designing Algorithms | 算法设计

Algorithms are the heart of any program. Let’s design the core algorithm for borrowing a book using structured English (pseudocode) and a flowchart. The steps are:

算法是任何程序的核心。我们用结构化英语（伪代码）和流程图来设计借阅图书的核心算法。步骤如下：

Input member ID and book ISBN.
Search for the book in the book list by ISBN.
If the book is not found, display an error message and stop.
If the book is found but not available, display “Book already on loan” and stop.
If the book is available, check that the member ID exists in the member list.
If member ID invalid, display error and stop.
Otherwise, mark the book as unavailable, create a new borrow record with today’s date and due date (today + 14 days), and display confirmation.

输入会员ID和图书ISBN。
在图书列表中按ISBN搜索图书。
若未找到该书，显示错误消息并停止。
若找到图书但不可借，显示 “图书已借出” 并停止。
若图书可借，检查会员ID是否存在于成员列表中。
若会员ID无效，显示错误并停止。
否则，将该书标记为不可借，创建一个新借阅记录，包含今天的日期和应还日期（今天+14天），并显示确认信息。

This algorithm can be expressed as a flowchart with decision diamonds for each condition. This structured approach makes it easy to translate into code later.

该算法可以用流程图表示，每个条件对应一个决策菱形。这种结构化的方法便于后续转化为代码。

7. User Interface Prototype | 用户界面原型

A simple text-based menu is enough for a first version. We can design it as follows:

文本菜单对于初版来说足够了。我们可以这样设计：

=== Library System ===
1. Add new book
2. Register new member
3. Borrow a book
4. Return a book
5. Search books
6. View member loans
7. Exit
Enter your choice: _

This menu repeats until the user chooses 7. Each option calls a corresponding function. We will also include sub-menus, for example, after choosing search, the user may enter a keyword and choose to search by title or author.

这个菜单会循环显示，直到用户选择7。每个选项调用对应的函数。我们还会包含子菜单，例如选择搜索后，用户可以输入关键词并选择按标题还是按作者搜索。

Good user interface design ensures that instructions are clear and that the user always knows what to do next. Error messages should be helpful, not scary.

良好的用户界面设计确保指令清晰，用户始终知道下一步该做什么。错误消息应有所帮助，而非令人恐惧。

8. Test Plan | 测试计划

Testing is not just finding bugs; it is about ensuring the system meets its requirements. We can create a test table that lists test cases, inputs, expected outcomes, and actual results.

测试不仅仅是寻找错误；它关乎确保系统满足需求。我们可以创建一个测试表，列出测试用例、输入、预期结果和实际结果。

Test ID	Description	Input Data	Expected Result
T1	Borrow available book	Member ID: M001, ISBN: 978-…-002	Confirmation with due date; book marked unavailable
T2	Borrow unavailable book	Member ID: M001, ISBN: 978-…-002 (already borrowed)	Error: “Book already on loan”
T3	Search by author	Keyword: “Tolkien”	List of books by Tolkien with status

测试ID	描述	输入数据	预期结果
T1	借阅可借图书	会员ID: M001, ISBN: 978-…-002	确认信息含应还日期；图书标记为不可借
T2	借阅已借出图书	会员ID: M001, ISBN: 978-…-002（已借出）	错误：”图书已借出”
T3	按作者搜索	关键词: “Tolkien”	列出托尔金的所有图书及其状态

Boundary testing is also important: what happens if we return a book on the due date? Fine should be 0. If returned one day late, fine should be 0.10. We can test these edge cases.

边界测试也很重要：如果我们在到期日当天归还图书会怎样？罚款应为0。如果逾期一天归还，罚款应为0.10。我们可以测试这些边界情况。

9. Simple Implementation in Python | 简单的Python实现

Let’s look at a code snippet that demonstrates the book search function. This is a key part of the system and shows how we use loops and conditionals.

让我们看一段演示图书搜索功能的代码片段。这是系统的关键部分，展示了如何使用循环和条件语句。

English code example:

def search_books(keyword, search_by='title'):
    results = []
    for book in book_list:
        if search_by == 'title' and keyword.lower() in book['title'].lower():
            results.append(book)
        elif search_by == 'author' and keyword.lower() in book['author'].lower():
            results.append(book)
    return results

中文说明：这个函数遍历图书列表，检查关键词是否出现在书名或作者中（取决于搜索方式）。它返回匹配书籍的列表。注意我们使用 .lower() 使搜索不区分大小写。

We would then display the results with availability information. Full implementation would include saving data to a file using the json module so that books and members persist between runs.

然后我们将显示结果及其可借状态信息。完整实现会包括使用json模块将数据保存到文件，以便图书和成员信息在程序运行间持久保留。

10. Fine Calculation Algorithm | 罚款计算算法

The fine calculation is a small but important feature. If a book is returned after the due date, we charge 10 pence per day. The algorithm deducts the due date from the return date to find the number of days late. If days ≤ 0, fine is 0; else fine = days * 0.10.

罚款计算是一个小而重要的功能。如果图书在应还日期之后归还，我们每天收取10便士。算法用归还日期减去应还日期，得出逾期天数。若天数 ≤ 0，罚款为0；否则罚款 = 天数 × 0.10。

The calculation can be written as: fine = max(0, (return_date − due_date).days) × 0.10

公式可写为：罚款 = max(0, (归还日期 − 应还日期).天数) × 0.10

This uses Python’s datetime module: (return_date – due_date).days gives an integer number of days. The max function ensures we never charge a negative fine. We then display the fine to the user.

这里使用了Python的datetime模块：(归还日期 – 应还日期).days 给出整数天数。max函数确保我们不会收取负罚款。然后我们将罚款金额显示给用户。

11. Legal and Ethical Considerations | 法律与道德考虑

When handling personal data like member names and emails, we must comply with the Data Protection Act 2018 and GDPR principles. Data should be stored securely, only used for the library’s purposes, and not shared without consent. In our design, we can add a simple login system to protect access. Also, fines should be fair and transparent — the system must clearly explain how the fine is calculated.

当处理会员姓名和邮箱等个人数据时，我们必须遵守《2018年数据保护法》和GDPR原则。数据应安全存储，仅用于图书馆目的，未经同意不得共享。在我们的设计中，可以添加一个简单的登录系统来保护访问。此外，罚款应公平透明——系统必须清晰说明罚款是如何计算的。

Ethically, we must ensure the system does not discriminate against any user. It should treat all members equally and provide the same quality of service. Accessibility is also important: for a text-based interface, we can offer larger fonts or voice output for visually impaired users.

道德上，我们必须确保系统不歧视任何用户。它应平等对待所有成员，提供相同质量的服务。无障碍同样重要：对于文本界面，我们可以为视障用户提供更大字体或语音输出。

12. Evaluating the Solution and Future Improvements | 评估方案与未来改进

After building and testing the system, we need to evaluate it against the original requirements. Did we meet all functional requirements? Is the system easy to use? Does it process data correctly and quickly? Feedback from the librarian and a few student testers would help identify weaknesses.

在构建和测试系统后，我们需要根据原始需求对其进行评估。我们是否满足了所有功能性需求？系统是否易于使用？它是否能正确、快速地处理数据？图书管理员和一些学生测试者的反馈将有助于识别薄弱环节。

Possible future improvements could include: a graphical user interface (using tkinter), a barcode scanner for faster book check-out, online reservation of books, and automated email reminders for overdue books. This iterative improvement is exactly how real software evolves.

未来可能的改进可以包括：图形用户界面（使用tkinter）、用于更快借书的条形码扫描器、在线预约图书，以及超期图书的自动邮件提醒。这种迭代改进正是真实软件演进的方式。

By completing this case study, you have practised the full software development lifecycle and connected many OCR Computer Science topics. Next time you encounter a problem, try to decompose it, abstract the key details, design algorithms, and test thoroughly. That is the mindset of a computational thinker.

通过完成这个案例分析，你实践了完整的软件开发生命周期，并串联了许多OCR计算机科学的主题。下次你遇到问题时，尝试分解它，抽象关键细节，设计算法，并进行全面测试。这就是计算思维者的心智模式。

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

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

Case Study in Action: Designing a Library Management System | 案例实战：设计一个图书馆管理系统