📚 A-Level Computer Science: Computing Project Overview and Requirements | A-Level计算机科学：计算项目总体描述及要求
The CIE A-Level Computer Science (9618) includes a mandatory computing project, assessed as Paper 4. This project is a substantial piece of work that requires you to produce a complete solution to a real-world problem, using a structured approach. It carries 75 marks and contributes 25% of the total A-Level qualification. Understanding its overall description and detailed requirements is essential for achieving a top grade.
CIE A-Level 计算机科学（9618）课程包含一个必修的计算项目，作为试卷 4 进行考核。这是一个规模较大的任务，要求你运用系统化方法，为一个真实问题制作完整的解决方案。该项目满分为 75 分，占 A-Level 总成绩的 25%。理解其总体描述和详细要求，是取得高分的关键。
1. What Is the Computing Project? | 什么是计算项目？
The computing project is an independent, problem-solving task in which you must create a software solution for a user with a genuine need. You will select a problem, analyse it, design a computational solution, implement the solution as a working program, test it thoroughly, and then evaluate the outcome. The project is internally assessed by your teacher and externally moderated by Cambridge.
计算项目是一项独立的、以解决问题为核心的任务，你需要为有真实需求的用户制作软件解决方案。你需要选择一个实际问题，对其进行分析，设计计算解决方案，将方案实现为可运行的程序，进行彻底测试，最后评估结果。该项目由校内教师评分，并由剑桥考试局进行外部审核。
Key features of the project include:
项目的主要特点包括：
- Real problem: The problem must be identified from real life, not a trivial or artificial exercise.
- 真实问题：必须从现实生活中识别问题，而不是琐碎的或人为设计的练习。
- Structured approach: You must follow a recognised development cycle, typically from analysis to evaluation.
- 结构化方法：必须遵循公认的开发周期，通常从分析到评估。
- Full working solution: The final program must be fully functional and meet the user's requirements.
- 完整可运行的解决方案：最终程序必须功能完备，满足用户需求。
- Documented evidence: You must submit a written report documenting all stages of the project, plus the code itself.
- 文档证据：必须提交书面报告，记录项目的所有阶段，并附带代码本身。
2. Assessment Objectives and Mark Allocation | 考核目标与分值分配
The project is marked against four main assessment objectives. Each objective targets a different skill set, and the total mark is 75. The following table summarises the mark breakdown:
项目按四个主要考核目标评分。每个目标对应不同的技能组，总分为 75 分。下表总结了分值的分配：
| Assessment Objective | 考核目标 | Skills Covered | 涵盖技能 | Marks | 分值 |
|---|---|---|
| AO1: Knowledge and understanding | Analysis and design of a solution | 25 |
| AO2: Application and development | Implementation of a solution (coding) | 25 |
| AO3: Testing and evaluation | Testing, evaluation and recommendations | 15 |
| AO4: Documentation and communication | Quality of the written report and code comments | 10 |
| Total | 总分 | 75 |
To score well, you must address all objectives explicitly. Many candidates lose marks by not justifying their design decisions or by providing incomplete test evidence.
要想取得好成绩，你必须明确地回应所有考核目标。许多考生因未能论证设计决策，或提供不完整的测试证据而失分。
3. Stage 1: Problem Identification and Analysis | 阶段一：问题识别与分析
The first stage is to identify a real problem and analyse it thoroughly. You need to describe the current system, the stakeholders involved, and the limitations of the existing approach. This analysis forms the foundation for all later decisions.
第一阶段是识别真实问题并深入分析。你需要描述当前系统、相关利益方以及现有方法的局限性。该分析是后续所有决策的基础。
Your analysis should include:
你的分析应包括：
- Title and overview of the problem: Explain what the problem is, who experiences it, and why a computer-based solution is beneficial.
- 问题和概述：解释问题是什么、谁遇到该问题，以及为什么基于计算机的解决方案是有益的。
- Data collection: Gather information via interviews, questionnaires, observation, or existing documents. Show evidence of this (e.g., annotated interview notes or questionnaire results).
- 数据收集：通过访谈、问卷、观察或现有文档收集信息，并展示证据（如注释过的访谈记录或问卷结果）。
- Current system model: Describe how the problem is handled today, using diagrams or process descriptions. Identify inefficiencies, errors, or time-consuming steps.
- 现有系统模型：描述问题目前如何处理，使用图表或流程描述。找出低效、错误或耗时的环节。
- User requirements: List the specific needs and expectations of the end user, expressed in non-technical language.
- 用户需求：以非技术语言列出最终用户的具体需求和期望。
- Quantifiable objectives: Set measurable targets, e.g., "Reduce data entry time from 10 minutes to 2 minutes per record."
- 可量化目标：设定可衡量的目标，例如“将每个记录的数据录入时间从 10 分钟减少到 2 分钟”。
This stage is worth up to 10 marks. A common mistake is to jump straight to design without demonstrating a genuine understanding of the problem.
这一阶段最高可得 10 分。常见错误是在未显示对问题的真正理解时，就直接跳到设计阶段。
4. Stage 2: Design of the Solution | 阶段二：解决方案设计
In the design stage, you must plan a complete solution based on your analysis. The design must be detailed enough that a third party could implement it without further clarification.
在设计阶段，你必须根据分析规划一个完整的解决方案。设计的详细程度应足以让第三方无需进一步澄清即可实现。
The design section typically includes:
设计部分通常包括：
- Variables and data structures: List all variables, arrays, records, and files you plan to use, with their data types and purposes.
- 变量和数据结构：列出计划使用的所有变量、数组、记录和文件，并说明其数据类型和用途。
- Algorithms: Write pseudocode or flowcharts for every major function, including validation, calculation, and data retrieval.
- 算法：为每个主要功能（包括验证、计算和数据检索）编写伪代码或流程图。
- Input and output design: Create mock-ups of input screens, output reports, and user interfaces. Label all elements clearly.
- 输入和输出设计：制作输入界面、输出报告和用户界面的原型图。清楚标注所有元素。
- Hardware and software requirements: State the programming language, operating system, and any libraries or frameworks used.
- 硬件和软件需求：说明编程语言、操作系统以及所用的任何库或框架。
- Security and integrity: Describe how you will keep data secure and maintain its integrity (e.g., validation checks, backup plans).
- 安全性和完整性：描述如何保护数据安全并维护其完整性（例如验证检查、备份计划）。
Design is worth about 15 marks. Use diagrams (e.g., structure charts, flowcharts, wireframes) to make your design visual and clear.
设计约占 15 分。使用图表（如结构图、流程图、线框图）使设计直观而清晰。
5. Stage 3: Implementation | 阶段三：程序实现
Implementation is the coding phase, where you turn your design into a working program. Your code should be modular, well-commented, and easy to read. You must also show evidence that the program works as intended.
实现是编码阶段，将设计转化为可运行的程序。代码应模块化、注释良好且易于阅读。你还必须展示程序按预期工作的证据。
Requirements for implementation include:
实现部分的要求包括：
- Code listing: Provide the full source code, with clear structure (e.g., sections for data structures, procedures, functions, and main program).
- 代码清单：提供完整源代码，结构清晰（如数据结构、过程、函数和主程序分区）。
- Comments: Explain each key logic step in the code; ideally, also justify why certain techniques were used.
- 注释：解释代码中每个关键逻辑步骤；最好同时说明为何使用某些技术。
- Modularity: Use procedures and functions to avoid repetition and improve maintainability.
- 模块化：使用过程和函数以避免重复并提高可维护性。
- Screenshots: Show annotated screenshots/recordings of the program running, demonstrating each major feature.
- 截图：展示注释过的程序运行截图或录像，演示每个主要功能。
- Error handling: Include robust validation and exception handling, and show how errors are reported to the user.
- 错误处理：包括稳健的验证和异常处理，并展示错误如何报告给用户。
This section carries 25 marks. Half of these marks come from the technical quality of the code, and the other half from the evidence that the program satisfies the user's requirements.
该部分占 25 分。其中一半分数来自代码的技术质量，另一半来自程序满足用户需求的证据。
6. Stage 4: Testing | 阶段四：测试
Testing is not just about showing that the program runs; it is about systematically proving that it behaves correctly for a range of inputs, including normal, boundary, and invalid data. You must design a test plan and record the results.
测试不仅仅是展示程序能运行；而是要系统地证明程序对一系列输入——包括正常、边界和无效数据——表现正确。你必须设计测试计划并记录结果。
Your testing section should include:
你的测试部分应包括：
- Test strategy: Explain whether you used black-box testing, white-box testing, or both, and why.
- 测试策略：说明你使用黑盒测试、白盒测试还是两者兼用，以及原因。
- Test plan: Create a formal table with columns for test number, test type, purpose, input data, expected output, actual output, and pass/fail status.
- 测试计划：创建正式表格，包含测试编号、测试类型、目的、输入数据、预期输出、实际输出和通过/失败状态等列。
- Normal data testing: Use typical inputs that the user would encounter.
- 正常数据测试：使用用户会遇到的典型输入。
- Boundary data testing: Test values at the minimum and maximum limits, e.g., exactly 0, exactly 100, or the largest allowed string.
- 边界数据测试：测试最小和最大极限值，例如恰好为 0、恰好为 100，或允许的最长字符串。
- Invalid data testing: Enter incorrect data types, out-of-range values, or missing fields, and verify that error messages appear.
- 无效数据测试：输入错误的数据类型、超范围的值或缺失字段，并验证错误信息是否出现。
- Live evidence: For each test, provide a screenshot or other evidence showing the program's output.
- 实时证据：针对每个测试，提供截图或其他证据显示程序的输出。
A weak area is often the lack of a clear, repeatable test plan. Always include the exact test data and expected result before showing the output.
常见的薄弱环节是缺乏清晰、可重复的测试计划。务必在展示输出之前，写明确切的测试数据和预期结果。
7. Stage 5: Evaluation and Recommendations | 阶段五：评估与建议
Evaluation is a critical stage where you reflect on the success of your solution against the original objectives. It is not a simple case of saying "it works"; you must provide evidence and reasoned judgement.
评估是一个关键阶段，你需要对照原始目标反思解决方案的成功程度。它不是简单地说“可行”，而是必须提供证据和有理由的判断。
Your evaluation should cover:
评估应包括：
- Success against objectives: Revisit each quantifiable objective from your analysis and decide whether it was met, partially met, or not met. Provide evidence (e.g., timing test results, user feedback).
- 目标达成情况：重新审视分析中的每个可量化目标，判断其是否达成、部分达成或未达成。提供证据（如计时测试结果、用户反馈）。
- User feedback: Ask the user to try the system and record their comments. Include their quotations in your report.
- 用户反馈：请用户试用系统并记录评论，在报告中引用他们的话。
- Strengths and limitations: Identify what the system does well and what it cannot handle. Be honest and specific.
- 优点和局限：指出系统擅长什么，无法处理什么，要诚实且具体。
- Recommendations for improvements: Suggest at least two or three realistic enhancements, explaining how they would improve the solution.
- 改进建议：提出至少两三个切实可行的增强方案，并解释它们如何改进解决方案。
This stage is worth 15 marks. Use phrases like "This met the objective because..." or "The user reported that..." to ground your evaluation in evidence.
这一阶段占 15 分。使用“这达成了目标，因为……”或“用户反馈说……”等表述，将评估建立在证据之上。
8. Project Report and Submission Requirements | 项目报告与提交要求
Your final submission must include a written report, the program code, and any necessary supporting files. The report should be clear, well-organised, and written in a professional style. Cambridge provides specific guidance, but the typical structure is as follows:
你的最终提交必须包括书面报告、程序代码以及必要的支持文件。报告应清晰、组织良好，并以专业风格撰写。剑桥提供了具体指南，典型结构如下：
| Report Section | 报告章节 | Content | 内容 |
|---|---|
| 1. Introduction | Problem statement, user, and objectives |
| 1. 引言 | 问题陈述、用户和目标 |
| 2. Analysis | Current system, data collection, user requirements |
| 2. 分析 | 现有系统、数据收集、用户需求 |
| 3. Design | Hardware/software, algorithms, UI design, file structures |
| 3. 设计 | 硬件/软件、算法、界面设计、文件结构 |
| 4. Implementation | Code listing, comments, screenshots of running system |
| 4. 实现 | 代码清单、注释、运行系统截图 |
| 5. Testing | Test plan, test data, results, error corrections |
| 5. 测试 | 测试计划、测试数据、结果、错误修正 |
| 6. Evaluation | Success criteria, user feedback, recommendations |
| 6. 评估 | 成功标准、用户反馈、建议 |
Submit your work as a single PDF document, with the code included in an appendix. Check your school's deadline and any additional formatting rules before submission.
请将作品以单个 PDF 文件提交，代码包含在附录中。提交前请核对学校的截止日期及任何附加的格式规则。
9. Choosing a Good Project Topic | 选择好的项目主题
The quality of your project topic significantly affects your final grade. A good topic is neither too simple (e.g., a basic calculator) nor too complex (e.g., a full operating system). It should have a clear, real user and allow you to demonstrate a wide range of programming skills.
项目主题的质量会显著影响最终成绩。好的主题不会太简单（如基础计算器），也不会太复杂（如完整的操作系统）。它应当有清晰、真实的用户，并能让你展示广泛的编程技能。
Examples of suitable projects:
适合的项目示例：
- School timetabling system: Allocates teachers and rooms to classes, avoiding clashes.
- 学校排课系统：为班级分配教师和教室，避免冲突。
- Library management system: Tracks borrowing, returns, and overdue items.
- 图书馆管理系统：跟踪借阅、归还和逾期物品。
- Sports league results manager: Updates tables, calculates statistics, and generates reports.
- 体育联赛成绩管理器：更新积分表、计算统计并生成报告。
- Small business invoice system: Creates invoices, calculates totals and tax, and stores customer data.
- 小企业发票系统：创建发票、计算总额和税费，并存储客户数据。
- Personal fitness tracker: Records workouts, meal calories, and progress graphs.
- 个人健身追踪器：记录训练、食物热量和进度图表。
Choose a topic you are genuinely interested in and one that allows you to use file handling, database queries, algorithms (searching/sorting), and user interfaces. Avoid topics that rely heavily on a graphical framework you cannot explain.
选择一个你真正感兴趣的主题，并且能够让你使用文件处理、数据库查询、算法（搜索/排序）和用户界面。避免那些严重依赖你无法解释的图形框架的主题。
10. Common Pitfalls and How to Avoid Them | 常见误区与避免方法
Many candidates lose marks because of preventable mistakes. Knowing these pitfalls in advance can save you several grade boundaries.
许多考生因为可避免的错误而失分。提前了解这些误区可以帮你挽回多个分数档。
- Skipping the analysis: Jumping to design without evidence of user research leads to a solution that does not fit the problem.
- 跳过分析：没有用户研究证据就进入设计，会导致解决方案不适合实际问题。
- Overly ambitious scope: Trying to build a huge system often results in incomplete features and poor code. Start small and expand if time allows.
- 范围过于庞大：试图构建大型系统常常导致功能不完整和代码质量差。从小规模开始，如果时间允许再扩展。
- Poor test evidence: Saying "tested and works" without screenshots, exact inputs, or expected results is not sufficient.
- 测试证据不足：只写“已测试并通过”而没有截图、具体输入或预期结果，是不充分的。
- Ignoring user feedback: Not incorporating or reporting honest user feedback weakens your evaluation.
- 忽视用户反馈：不纳入或如实报告用户反馈，会削弱评估部分。
- Poor code style: No comments, unclear variable names, and long unwieldy blocks are hard to understand and lose marks.
- 代码风格差：没有注释、变量名不清晰以及冗长笨重的代码块难以理解，会丢分。
Plan your time carefully. A typical project takes 40–60 hours of work, including report writing. Do not leave everything to the last month.
请仔细规划时间。一个典型项目需要 40-60 小时的工作量，包括报告撰写。不要把所有工作留到最后一个月。
11. The Importance of the Logbook | 日志的重要性
Although the logbook is not directly marked in Paper 4, it is a vital working document. You should keep a dated log of every decision, change, and problem encountered during the project. This helps you write an accurate and detailed report, and it also serves as evidence of your time management and problem-solving process.
虽然日志在试卷 4 中不直接计分，但它是重要的工作文档。你应当记录项目期间每个决策、更改和遇到的问题的日期。这有助于你撰写准确而详细的报告，同时也可以作为时间管理和问题解决过程的证据。
Your logbook might include:
你的日志可以包括：
- Initial ideas and why they were rejected or accepted
- 初始想法及其被接受或拒绝的原因
- Meetings or emails with your client/user
- 与客户/用户的会面或邮件往来
- Problems encountered while coding and how you fixed them
- 编码中遇到的问题及其修复方法
- Changes to the design and their rationale
- 对设计的更改及其理由
- Testing sessions and immediate outcomes
- 测试会话及即时结果
Use your logbook as a reference when writing the final report. It will also prevent you from forgetting important details under exam pressure or deadline stress.
在撰写最终报告时，把日志作为参考。它也能防止你在考试压力或截止期限压力下忘记重要细节。
12. Final Tips for Success | 成功的最终建议
To maximise your mark on the computing project, adopt a professional mindset. Treat your user as a real client, follow a clear methodology, and document everything as you go. The following practical tips will help you:
为了在计算项目中取得最高分，请采用专业心态。将你的用户视为真实客户，遵循清晰的方法论，并边做边记录。以下实用建议会帮助你：
- Start early: Begin the proposal at least three months before the deadline.
- 尽早开始：至少在截止日期前三个月开始提出项目建议书。
- Choose the right programming language: Use a language you know well and that is suitable for the problem, such as Python, Java, or C#.
- 选择合适的编程语言：使用你熟悉的且适合问题的语言，如 Python、Java 或 C#。
- Write code iteratively: Develop small modules and test them individually before integrating them.
- 迭代编码：先开发小型模块并单独测试，然后再集成。
- Keep backups: Use version control (e.g., Git) or save dated copies of your files to avoid data loss.
- 备份：使用版本控制（如 Git）或保存带日期的文件副本，以避免数据丢失。
- Re-read the syllabus: Check that you have addressed every assessment objective and requirement from Cambridge.
- 重读大纲：检查你是否已满足剑桥每个考核目标和所有要求。
- Get a second opinion: Ask a classmate or teacher to review your draft report for clarity and completeness.
- 获取第二意见：请同学或老师审阅你的报告草稿，确保清晰完整。
Remember, the computing project is not just about coding. It is a complete problem-solving exercise that mirrors real-world software development. By following the description and requirements outlined above, you can build a solution that is both functional and well-documented, and earn the marks you deserve.
请记住，计算项目不仅仅是编程。它是一个完整的问题解决过程，反映真实世界的软件开发。通过遵循上文概述的总体描述和要求，你可以构建一个功能正常且文档完善的解决方案，并获得应得的分数。
Published by TutorHao | Computer Science Revision Series | aleveler.com
更多咨询请联系16621398022（同微信）
或截图后用「扫一扫 → 相册」选择本图