📚 Case Study Practical Walkthrough | 案例分析实战演练
In this case study, a secondary school wants to replace its paper-based library system with a digital solution. The current process relies on manual sign-out sheets, making it difficult to track overdue books or generate reports. The school needs a system where students can log in, search for available books, borrow them, and return them electronically. Librarians need administrative access to add new books, update records, and send automated reminders for overdue items. The system must also consider data protection, as it stores personal information of students. As a Computer Science student, you must examine this scenario and propose a well-structured solution using the systems lifecycle.
在这个案例中，一所中学希望用数字化方案取代纸质图书借阅系统。目前流程依赖手动登记表，难以跟踪逾期图书或生成报告。学校需要一个系统，使学生可以登录、搜索可借图书、借阅和归还。图书管理员需要管理权限，可以添加新书、更新记录并发送逾期提醒。系统还必须考虑数据保护，因为它存储学生的个人信息。作为计算机科学学生，你需要分析该场景，并运用系统生命周期提出结构化的解决方案。
1. Understanding the Case Scenario | 理解案例场景
The first step is to fully understand the problem domain. A school library currently uses paper-based sign-out sheets. Students come to the counter, present their ID card, and a librarian manually records the book title, borrower name, date, and due date in a logbook. Returns are recorded similarly. This method leads to issues: incomplete records, illegible handwriting, lost logbooks, and no easy way to generate overdue lists. The school wants a digital system to automate these processes, improve efficiency, and provide useful data such as most popular books. Key constraints are a limited budget of £5,000, existing network infrastructure, and legal compliance with the Data Protection Act 2018.
第一步是充分理解问题领域。一所学校图书馆目前使用纸质登记表。学生来到柜台，出示学生证，图书管理员手动在日志本中记录书名、借阅人姓名、日期和到期日。归还过程同样记录。这种方法导致许多问题：记录不完整、字迹难以辨认、日志本丢失，以及无法轻松生成逾期列表。学校希望有一个数字化系统来自动化这些流程、提高效率，并提供有用数据，如最受欢迎的图书。关键约束条件包括有限的5000英镑预算、现有网络基础设施以及遵守2018年数据保护法的法律要求。
2. Identifying Stakeholders and Requirements | 识别利益相关者与需求
Stakeholders include students, librarians, school administration, and IT staff. Students require a quick search function, clear borrowing rules (e.g., maximum 3 books for 14 days), and the ability to renew online. Librarians need efficient stock management, overdue tracking, and reporting tools. The administration wants cost-effectiveness and compliance with regulations such as GDPR. IT staff will be responsible for maintenance, so the system should be well-documented and built with standard technologies. Identifying these requirements early helps prioritise features and avoid scope creep.
利益相关者包括学生、图书管理员、学校管理层和IT人员。学生需要快速搜索功能、明确的借阅规则（如最多借3本书、14天）以及在线续借功能。图书管理员需要高效的库存管理、逾期跟踪和报表工具。管理层希望系统经济实用，并符合GDPR等法规。IT人员将负责维护，因此系统应有良好文档并使用标准技术构建。尽早识别这些需求有助于优先排序功能并避免范围蔓延。
3. Feasibility Study | 可行性研究
Before building the system, a feasibility study examines whether the project is practical. Economic feasibility looks at costs: the school has a budget of £5,000 for software development and hardware, including a server and barcode scanners. Technical feasibility checks if the school has the network infrastructure and staff expertise; the school already has a local area network and computers in the library. Legal feasibility ensures the system will comply with data protection laws by encrypting personal data and obtaining consent from students (or parents for under 16s). Operational feasibility assesses whether staff and students will accept the new system; training sessions can help smooth the transition.
在构建系统前，可行性研究考察项目是否切实可行。经济可行性考虑成本：学校有5000英镑预算用于软件开发和硬件，包括服务器和条形码扫描器。技术可行性检查学校是否有网络基础设施和人员技能；学校已有局域网和图书馆电脑。法律可行性确保系统遵守数据保护法，通过加密个人数据并获取学生（或未满16岁学生的家长）的同意。操作可行性评估员工和学生是否接受新系统；培训课程可帮助平稳过渡。
4. System Analysis Techniques | 系统分析方法
To gather detailed requirements, the analyst can conduct interviews with the school librarian to understand daily workflows. Questionnaires distributed to students can reveal how often they visit the library and what features they value most. Direct observation of the current paper-based process helps identify bottlenecks, such as long queues during lunchtime. Document analysis of existing sign-out sheets reveals patterns, like popular book genres or frequent late returns. These techniques ensure no requirement is missed before moving to design.
为收集详细需求，分析师可与图书管理员面谈，了解日常工作流程。向学生发放问卷可揭示他们访问图书馆的频率以及最看重的功能。直接观察当前纸质流程有助于发现瓶颈，如午餐时间排长队。对现有登记表的文档分析可揭示模式，如热门图书类型或频繁的逾期归还。这些技术确保在进入设计阶段前不遗漏任何需求。
5. System Design – Flowcharts and Pseudocode | 系统设计 – 流程图和伪代码
Design is a crucial phase. A flowchart can model the borrowing process: start, student scans ID card, system verifies membership, student searches for a book, system checks availability, if available set due date and record transaction, else display ‘not available’, end. Pseudocode might represent the search function:
设计是关键阶段。流程图可以模拟借阅过程：开始，学生扫描ID卡，系统验证会员资格，学生搜索图书，系统检查可借状态，如果可借则设定到期日并记录交易，否则显示“不可借”，结束。伪代码可以表示搜索功能：
START
INPUT searchTerm
results = database.query(“SELECT * FROM Books WHERE title LIKE ‘%searchTerm%’”)
IF results not empty THEN
DISPLAY results
ELSE
DISPLAY “No books found”
ENDIF
END
This structured approach ensures programmers understand the logic before coding. The design also includes a data dictionary defining fields like StudentID (integer, auto-increment, primary key) and screen mock-ups showing the user interface layout.
这种结构化方法确保程序员在编码前理解逻辑。设计还包括数据字典，定义字段如StudentID（整数，自动递增，主键），以及显示用户界面布局的屏幕模型。
6. Database Design | 数据库设计
The system requires a relational database. Three main entities are Students, Books, and Loans. The Students table: StudentID (primary key, integer), FirstName, LastName, YearGroup, Email, PasswordHash. The Books table: BookID (primary key, integer), ISBN, Title, Author, Genre, Status (available/on loan). The Loans table: LoanID (primary key), StudentID (foreign key referencing Students), BookID (foreign key referencing Books), BorrowDate, DueDate, ReturnDate. This normalisation reduces redundancy. For example, a student’s name is stored only once in Students, not repeated in every loan record.
系统需要关系型数据库。三个主要实体是学生(Students)、图书(Books)和借阅(Loans)。Students表：StudentID（主键，整数），FirstName，LastName，YearGroup，Email，PasswordHash。Books表：BookID（主键，整数），ISBN，Title，Author，Genre，Status（可借/已借出）。Loans表：LoanID（主键），StudentID（外键引用Students），BookID（外键引用Books），BorrowDate，DueDate，ReturnDate。这种规范化减少了冗余。例如，学生姓名只在Students表中存储一次，不会在每条借阅记录中重复。
7. Data Validation and Input Design | 数据验证和输入设计
To prevent errors, the system must include validation checks. Presence check ensures required fields like student ID or book title are not left empty. Length check limits the password to a minimum of 8 characters. Type check confirms that YearGroup is an integer. Format check verifies that the email address contains an ‘@’ symbol. Input forms should use drop-down menus for genres, date pickers for dates, and clear error messages to guide users. For example, if a student tries to borrow a book already on loan, the system displays ‘Book currently unavailable. Please try again later.’
为防止错误，系统必须包含验证检查。存在性检查确保学生ID或图书标题等必填字段不为空。长度检查限制密码至少8个字符。类型检查确认YearGroup是整数。格式检查验证邮箱地址包含“@”符号。输入表单应使用下拉菜单选择图书类别，日期选择器选择日期，以及清晰的错误信息引导用户。例如，如果学生尝试借阅已借出的书，系统显示“图书当前不可借，请稍后再试。”
8. Security Considerations | 安全考虑
Security is vital because the system holds personal data. User authentication requires a secure login with hashed passwords (using bcrypt). The database should use parameterised queries or prepared statements to prevent SQL injection attacks. All data transmitted between the client browser and the server must be encrypted using HTTPS. Access rights differentiate between student and librarian roles; students cannot access administrative functions. The system must also comply with the Data Protection Act 2018, meaning data should be stored securely, not kept longer than necessary, and individuals can request their records. Regular backups protect against data loss.
安全至关重要，因为系统存储个人数据。用户认证要求使用加密密码（如bcrypt）的安全登录。数据库应使用参数化查询或预编译语句，防止SQL注入攻击。客户端浏览器与服务器之间传输的所有数据必须使用HTTPS加密。访问权限区分学生和图书管理员角色；学生无法访问管理功能。系统还必须遵守2018年数据保护法，这意味着数据应安全存储、不超期保留，且个人可请求查阅其记录。定期备份防止数据丢失。
9. Test Plan | 测试计划
A thorough test plan ensures the system works correctly. Types of testing include:
完善的测试计划确保系统正常工作。测试类型包括：
- Unit testing: test individual modules, e.g., the ‘calculate due date’ function returns a date exactly 14 days after borrowing.
单元测试：测试单个模块，例如“计算到期日”函数返回借阅后14天的日期。 - Integration testing: check that the borrowing module interacts correctly with the database by inserting a loan record.
集成测试：检查借阅模块与数据库的交互，插入一条借阅记录。 - System testing: end-to-end scenarios, such as a student logs in, searches for a book, borrows it, and the librarian views the updated loan list.
系统测试：端到端场景，如学生登录、搜索图书、借阅，图书管理员查看更新后的借阅列表。 - Acceptance testing: the school librarian verifies that the system meets all requirements before going live.
验收测试：图书管理员确认系统在上线前满足所有需求。
Test data should cover normal, boundary (e.g., borrowing the maximum 3 books), and erroneous data (e.g., entering text in a numeric field). A test table can record test ID, description, expected result, actual result, and pass/fail.
测试数据应覆盖正常、边界（如借满3本）和错误数据（如在数字字段输入文本）。测试表可记录测试ID、描述、预期结果、实际结果和通过/失败。
| Test ID | Description | Expected Result | Actual | Pass/Fail |
|---|---|---|---|---|
| T1 | Login with valid credentials | Redirect to dashboard | As expected | Pass |
| T2 | Borrow when already at max 3 books | Error message displayed | Error shown | Pass |
This structured approach reduces bugs before deployment.
这种结构化方法在部署前减少错误。
10. Implementation and Maintenance | 实施与维护
Implementation can follow a phased approach: first, the book database and user accounts are set up; then the borrowing module is introduced; finally, the overdue reminder system goes live. Training sessions for staff and students are essential. User manuals and online help guides should be provided. Maintenance involves three types: corrective (fixing bugs found by users), adaptive (updating the system for changes like new school policies), and perfective (adding improvements such as a recommendation feature). Regular reviews ensure the system remains effective and secure.
实施可采用分阶段方法：首先，建立图书数据库和用户账户；然后上线借阅模块；最后启用逾期提醒系统。对员工和学生进行培训必不可少。应提供用户手册和在线帮助指南。维护包括三种类型：纠正性维护（修复用户发现的错误）、适应性维护（根据新校规等变化更新系统）和完善性维护（添加改进，如推荐功能）。定期回顾确保系统持续有效和安全。
11. Evaluation | 评估
After development, an evaluation measures the system’s success against original objectives. Did it reduce average borrowing time? Are overdue books now tracked accurately? User feedback from a questionnaire can rate ease of use from 1 to 5. The librarian can report if inventory management is faster. Any limitations, such as initial slow response during peak hours, can be noted for future upgrades. The evaluation report should also reflect on legal compliance and suggest further enhancements, like a mobile app version. This step completes the systems lifecycle and ensures continuous improvement.
开发后，评估衡量系统是否达到最初目标。是否缩短了平均借阅时间？逾期图书现在能否准确跟踪？来自问卷的用户反馈可按1到5分评价易用性。图书管理员可以报告库存管理是否更快。任何局限性，如高峰时段响应慢，均可记录用于未来升级。评估报告还应反映法律合规性，并建议进一步增强功能，如移动应用版本。这一步骤完成了系统生命周期并确保持续改进。
Published by TutorHao | 计算机 Revision Series | aleveler.com
更多咨询请联系16621398022（同微信）
屏轩国际教育cambridge primary/secondary checkpoint, cat4, ukiset,ukcat,igcse,alevel,PAT,STEP,MAT, ibdp,ap,ssat,sat,sat2课程辅导，国外大学本科硕士研究生博士课程论文辅导Cancel reply