📚 Year 10 CCEA Computer Science: Case Study Practical Drill | Year 10 CCEA 计算机：案例分析实战演练
Welcome to this practical drill for the CCEA Year 10 Computer Science case study. In this article, we will walk through a complete system lifecycle using a realistic scenario: designing a Library Book Management System for a school library. You will learn how to apply analysis, design, implementation, testing, and evaluation. This hands-on guide will strengthen your understanding of the software development process and prepare you for exam-style case study questions.
欢迎参加 CCEA Year 10 计算机案例分析的实战演练。本文将使用一个真实场景——为学校图书馆设计图书管理系统，带你完整走一遍系统生命周期。你将学习如何运用分析、设计、实施、测试和评估。这份实操指南将加深你对软件开发过程的理解，帮助你应对考试中的案例分析题。
1. Understanding the Case Study Scenario | 理解案例场景
A case study typically describes a real-world problem that requires a computerised solution. In our scenario, the school librarian currently uses paper records to track books, borrowers, and due dates. This manual system is inefficient, error-prone, and cannot generate reports quickly. The goal is to create a digital Library Book Management System that can store book details, manage loans, and produce overdue notices automatically.
案例研究通常描述一个需要计算机化解决方案的现实问题。在我们的场景中，学校图书管理员目前使用纸质记录来追踪图书、借阅者和到期日。这种手工系统效率低下、容易出错，且无法快速生成报告。目标是创建一个数字图书管理系统，能够存储图书详细信息、管理借阅并自动生成逾期通知。
2. Requirements Analysis | 需求分析
Requirements analysis involves gathering information from stakeholders. We will interview the librarian, students, and teachers. Key functional requirements include: add new books, search for books by title/author, register borrowers, issue and return books, and display overdue items. Non-functional requirements include: the system must be easy to use, respond within 2 seconds, and protect borrower data with a login.
需求分析涉及从利益相关者那里收集信息。我们将采访图书管理员、学生和老师。关键功能需求包括：添加新书、按书名/作者搜索图书、登记借阅者、借出与归还图书，以及显示逾期项目。非功能需求包括：系统必须易于使用、响应时间在 2 秒以内，并通过登录保护借阅者数据。
A list of requirements can be tabulated:
需求列表可整理如下：
| ID | Requirement | Type |
|---|---|---|
| R1 | Add a new book with ISBN, title, author | Functional |
| R2 | Search books by keyword | Functional |
| R3 | Issue a book to a borrower | Functional |
| R4 | Return a book and calculate fines | Functional |
| R5 | System response time < 2 seconds | Non-functional |
This structured approach ensures that no critical feature is overlooked.
这种结构化的方法确保没有遗漏关键特性。
3. Feasibility Study | 可行性研究
Before proceeding, we must assess technical, economic, and operational feasibility. Technical feasibility: the school has computers and a network; we can use Python with SQLite for a lightweight database. Economic feasibility: development by students reduces cost; no expensive software licences needed. Operational feasibility: the librarian is willing to adopt a digital system and training can be provided.
在继续进行之前，我们必须评估技术、经济和操作可行性。技术可行性：学校有计算机和网络；我们可以使用 Python 搭配 SQLite 构建轻量数据库。经济可行性：由学生开发降低成本；不需要昂贵的软件许可证。操作可行性：图书管理员愿意采用数字系统，并可提供培训。
A simple cost-benefit analysis table:
一个简单的成本收益分析表：
| Cost | Benefit |
|---|---|
| Development time (approx 3 months) | Faster book issuing, reduced errors |
| Maintenance by school IT club | Automated overdue notices save staff time |
The project is deemed feasible and will proceed to design.
该项目被认为是可行的，将进入设计阶段。
4. System Design – Inputs, Outputs, Processes | 系统设计 – 输入、输出、处理
Designing the system involves specifying what data enters the system, what processing occurs, and what outputs are produced. We can use a data flow diagram or simply a structured table. For the library system, key inputs are book details, borrower ID, and loan actions; processes include adding records, searching, updating loans; outputs are search results, loan confirmations, and overdue lists.
系统设计需要明确什么数据进入系统、执行什么处理以及产生什么输出。我们可以使用数据流图或简单的结构化表格。对于图书管理系统，关键输入是图书详细信息、借阅者 ID 和借阅操作；处理包括添加记录、搜索、更新借阅状态；输出则是搜索结果、借阅确认和逾期清单。
We can summarise with an IPO table:
我们可以用 IPO 表格总结：
| Input | Process | Output |
|---|---|---|
| New book ISBN, title, author | Validate data, store in Books table | Confirmation message |
| Search keyword | Query database, filter results | List of matching books |
| Borrower ID, book ID | Check availability, create loan record | Due date slip or message |
| Returned book ID | Update loan status, calculate fine if overdue | Fine amount (0 if on time) |
This design makes it clear what each part of the program must handle.
这种设计明确了程序的每个部分必须处理什么。
5. Data Design and File Structures | 数据设计及文件结构
The data will be stored in a relational database. We identify three main tables: Books (BookID, ISBN, Title, Author, Copies), Borrowers (BorrowerID, Name, Class, Contact), and Loans (LoanID, BookID, BorrowerID, IssueDate, Due
Published by TutorHao | Year 10 Computer Science Revision Series | aleveler.com
更多咨询请联系16621398022（同微信）
或截图后用「扫一扫 → 相册」选择本图