📚 Year 12 AQA Computer Science: Practical Assessment Essentials | Year 12 AQA 计算机：实验/实践考核要点
In Year 12 AQA Computer Science, practical programming skills are not just about writing code — they form the bedrock of the Non‑Exam Assessment (NEA) and deepen your understanding of theoretical concepts. This article distils the key assessment points for practical work, helping you build robust projects that meet AQA’s marking criteria across analysis, design, implementation, testing and evaluation.
在 AQA 计算机科学 Year 12 课程中，实践编程技能不仅仅是写代码——它们是非考试评估（NEA）的基础，也能加深你对理论概念的理解。本文浓缩了实践工作的核心考核要点，帮助你构建严谨的项目，在分析、设计、实现、测试和评估各方面满足 AQA 的评分标准。
1. Understanding the AQA NEA Assessment Objectives | 理解 AQA NEA 评估目标
The AQA NEA (Non-Exam Assessment) contributes 20% of the final A‑level mark and is assessed against five categories: Analysis (9 marks), Design (12 marks), Technical Solution (42 marks), Testing (10 marks) and Evaluation (7 marks). Every practical exercise in Year 12 should align with these objectives so you develop the right habits early.
AQA 的非考试评估（NEA）占 A‑level 总成绩的 20%，并根据五个类别进行评分：分析（9 分）、设计（12 分）、技术解决方案（42 分）、测试（10 分）和评估（7 分）。Year 12 的每一次实践练习都应当与这些目标对齐，以便尽早养成正确的习惯。
| Assessment Objective | 评估目标 | Marks |
|---|---|---|
| Analysis | 分析 | 9 |
| Design | 设计 | 12 |
| Technical Solution | 技术解决方案 | 42 |
| Testing | 测试 | 10 |
| Evaluation | 评估 | 7 |
2. Problem Analysis and Decomposition | 问题分析与分解
Start every project by identifying the core computational problem, stakeholders and the scope of the solution. Use tools like context diagrams, user stories and a detailed list of functional and non‑functional requirements. Clear analysis directly feeds into higher marks.
每个项目都应从识别核心计算问题、利益相关者和解决方案的范围开始。可使用上下文图、用户故事以及详细的功能与非功能需求列表等工具。清晰的分析直接关系到更高的分数。
Top‑down decomposition breaks a complex problem into manageable sub‑tasks. Write a problem statement in plain English first, then convert it into a numbered list of sub‑problems that can be solved independently by separate modules.
自顶向下的分解将复杂问题拆分为可管理的子任务。先用简单英语写出问题陈述，然后将其转换为可以用独立模块分别解决的编号子问题列表。
3. Algorithm Design and Pseudocode | 算法设计与伪代码
Before any code is typed, sketch your algorithms using AQA‑style pseudocode. Ensure you handle sequence, selection (IF‑ELSE) and iteration (WHILE, FOR, REPEAT‑UNTIL). Include meaningful variable names and comments to explain the logic.
在输入任何代码之前，先用 AQA 风格的伪代码勾勒出你的算法。确保你处理了顺序、选择（IF‑ELSE）和迭代（WHILE、FOR、REPEAT‑UNTIL）。包含有意义的变量名和注释来解释逻辑。
Design at least two alternative approaches for a non‑trivial algorithm, such as searching and sorting. Explain the trade‑offs using Big O notation — for example, linear search is O(n) while binary search is O(log n) — and justify your final choice.
对于非平凡算法，例如搜索和排序，至少设计两种替代方案。用大 O 表示法解释权衡——例如，线性搜索是 O(n)，而二分搜索是 O(log n)——并为你最终的选择提供理由。
4. Programming Best Practices | 编程最佳实践
Write clean, maintainable code that follows conventions of your chosen language (Python, Java, C# or VB.NET). Use meaningful identifiers, consistent indentation and avoid global variables. Modularise with functions and procedures, each performing a single task.
编写符合所选语言（Python、Java、C# 或 VB.NET）规范的整洁、可维护代码。使用有意义的标识符、一致的缩进并避免全局变量。用函数和过程实现模块化，每个模块执行单一任务。
Always validate user input and handle edge cases gracefully. Implement exception handling (try‑except or try‑catch) to prevent crashes, and log errors so you can explain them during evaluation.
始终验证用户输入并优雅地处理边缘情况。实现异常处理（try‑except 或 try‑catch）以防止崩溃，并记录错误以便在评估时解释它们。
5. Data Structures and File Handling | 数据结构与文件处理
Choose appropriate data structures: arrays for homogeneous data, records/classes for composite data, and dictionaries/maps for key‑value lookups. For dynamic collections, use lists or ArrayLists. Justify each choice in your design commentary.
选择适当的数据结构：数组用于同质数据，记录/类用于复合数据，字典/映射用于键‑值查找。对于动态集合，使用列表或 ArrayList。在设计评述中为每个选择提供理由。
Many NEA projects require persistent storage. Read from and write to text files, CSV files or a simple SQLite database. Ensure your code closes files properly and uses a clear serialisation strategy so data is not corrupted.
许多 NEA 项目需要持久化存储。从文本文件、CSV 文件或简单的 SQLite 数据库读取和写入。确保代码正确关闭文件，并使用清晰的序列化策略，以免数据损坏。
6. User Interface and Usability | 用户界面与可用性
AQA does not require a graphical user interface, but if you use one, it must be intuitive and consistent. Label all inputs clearly, provide informative error messages and ensure the layout follows a logical flow. Even a text‑based menu should be easy to navigate.
AQA 不要求图形用户界面，但如果你使用，它必须直观且一致。清晰地标记所有输入，提供有用的错误消息，并确保布局遵循逻辑流程。即使是基于文本的菜单也应该易于导航。
Usability testing doesn’t have to be complex: ask a peer to complete a task and observe where they struggle. Record their feedback and use it to improve the interface. Evidence of iterative refinement scores highly under Technical Solution.
可用性测试不必复杂：让一位同伴完成一项任务，观察他们在哪里遇到困难。记录反馈并用来改进界面。迭代改进的证据在技术解决方案部分能获得高分。
7. Systematic Testing | 系统化测试
Plan testing during the design phase. Use a test table that includes test ID, description, input data, expected outcome, actual outcome and a pass/fail column. Cover normal, boundary and erroneous data. This structured approach satisfies the Testing mark scheme.
在设计阶段规划测试。使用包含测试编号、描述、输入数据、预期结果、实际结果和通过/失败列的测试表格。覆盖正常、边界和错误数据。这种结构化方法能满足测试评分方案。
For each failed test, diagnose the root cause, correct the code and re‑run the test until it passes. Keep screenshots or terminal logs as evidence. AQA expects to see that you have fixed bugs, not just discovered them.
对于每个失败的测试，诊断根本原因，修正代码并重新运行测试直到通过。保存屏幕截图或终端日志作为证据。AQA 期望看到你已经修复了错误，而不仅仅是发现它们。
8. Documentation and Report Writing | 文档与报告撰写
Your NEA report is not an afterthought — it is the primary vehicle for demonstrating your skills. Write as you go, not at the end. Keep a development diary that records decisions, challenges and the rationale for changes.
你的 NEA 报告不是事后才考虑——它是展示你技能的主要载体。边做边写，不要到最后才写。保持一份开发日记，记录决策、挑战和变更的理由。
Use clear headings mirroring the assessment objectives: Analysis, Design, Technical Solution, Testing and Evaluation. Embed code snippets, screenshots and diagrams. Reference any sources and explain how external code has been adapted.
使用与评估目标相对应的清晰标题：分析、设计、技术解决方案、测试和评估。嵌入代码片段、屏幕截图和图表。引用任何来源，并解释外部代码是如何改编的。
9. Evaluation and Reflective Practice | 评估与反思实践
A strong evaluation goes beyond 'it works'. Discuss what you would do differently with more time, which skills you have developed and how the solution meets the original objectives. Compare your finished product against the initial requirements and user feedback.
强有力的评估不仅仅是 '它是有效的'。讨论如果有更多时间你会做哪些不同，你发展了哪些技能，以及解决方案如何满足最初目标。将完成的产品与最初要求和用户反馈进行比较。
Quantitative measures, such as time taken to sort 1000 records, or memory usage comparisons between two algorithms, add rigour. Include these metrics and comment on their significance in real‑world contexts.
定量测量，例如排序 1000 条记录所需的时间，或两种算法之间的内存使用比较，增加了严谨性。纳入这些指标，并评论它们在现实世界背景下的意义。
10. Time Management and Version Control | 时间管理与版本控制
Treat the practical project like a series of sprints. Set intermediate deadlines for each phase: requirements by week 2, design by week 4, prototype by week 8, and so on. This prevents a last‑minute rush that compromises quality.
将实践项目视为一系列冲刺。为每个阶段设定中间截止日期：第 2 周完成需求，第 4 周完成设计，第 8 周完成原型等。这可以防止因最后一刻赶工而影响质量。
Use a simple version‑control system like Git or even dated backups. Being able to roll back to a previous version saves hours when an experiment goes wrong. It also demonstrates professional working practices — a plus in the Technical Solution criteria.
使用简单的版本控制系统，如 Git，甚至带日期的备份。当实验出错时，能够回滚到之前的版本可以节省大量时间。这也展示了专业的工作实践——在技术解决方案标准中是一个加分项。
11. Common Mistakes to Avoid | 常见错误避免
Many students submit a working program but neglect the analysis and design sections, losing easy marks. Others hard‑code values instead of using constants or config files, making the project hard to adapt. Always think about scalability and maintainability.
许多学生提交了一个能运行的程序，却忽略了分析和设计部分，丢掉了容易得到的分数。还有人硬编码数值而不是使用常量或配置文件，导致项目难以调整。始终要考虑可扩展性和可维护性。
Avoid over‑complicating the problem; a well‑executed simple project scores higher than an ambitious but unfinished one. Also, never leave testing until the end — integrate it continuously and document as you go.
避免过度复杂化问题；一个执行良好的简单项目比一个雄心勃勃但未完成的项目得分更高。此外，永远不要将测试留到最后——持续集成测试并边做边记录。
12. Final Checklist Before Submission | 提交前最终检查清单
Use this rapid checklist to ensure nothing is missed: requirements document complete; design includes pseudocode and data structures; code modular and commented; validation and error handling present; test table with normal, boundary and erroneous data; evidence of iterative development; evaluation that references objectives and user feedback.
使用这份快速检查清单确保无遗漏：需求文档完整；设计包含伪代码和数据结构；代码模块化且有注释；存在验证和错误处理；包含正常、边界和错误数据的测试表格；迭代开发的证据；引用目标和用户反馈的评估。
Published by TutorHao | Computer Science Revision Series | aleveler.com
更多咨询请联系16621398022（同微信）
或截图后用「扫一扫 → 相册」选择本图