Year 12 WJEC Computer Science: Key Points for Practical Assessment | Year 12 WJEC 计算机：实践考核要点

📚 Year 12 WJEC Computer Science: Key Points for Practical Assessment | Year 12 WJEC 计算机：实践考核要点

The WJEC Year 12 Computer Science practical assessment (often the on-screen Unit 2 exam) is a demanding test of your programming, problem-solving and debugging skills under timed conditions. Success requires more than just knowing how to code — you must be able to interpret a scenario, design a solution, write clean code, test thoroughly and manage your time wisely. This guide breaks down the critical areas to focus on, helping you approach the exam with confidence.

WJEC Year 12 计算机科学实践考核（通常是Unit 2上机考试）是对你在限时条件下编程、解决问题和调试能力的严格检验。成功不仅需要会写代码，你还必须能够解读场景、设计解决方案、编写清晰的代码、进行彻底测试并合理管理时间。本指南将分解你需要关注的关键领域，帮助你自信地应对考试。

1. Exam Format and Environment | 考试形式与环境

The WJEC Unit 2 on-screen exam typically lasts 2 hours and revolves around one or two programming tasks based on a given scenario. You will be working on a computer with your chosen programming language (Python, Java, C#, VB.NET, etc.) and a suitable IDE (e.g., IDLE, NetBeans, Visual Studio). Familiarise yourself with the exact software setup your centre provides well before the exam day.

WJEC Unit 2 上机考试通常持续2小时，围绕给定场景下的一个或两个编程任务展开。你将在电脑上使用所选编程语言（如 Python、Java、C#、VB.NET 等）和合适的集成开发环境（例如 IDLE、NetBeans、Visual Studio）作答。务必在考试前熟悉你所在考点提供的具体软件配置。

The final deliverables usually include the source code file(s) and evidence of testing, such as screenshots or a brief test log. Some centres may also ask you to type testing comments directly into your code. Always read the instructions on the question paper to confirm what you need to submit.

最终提交物通常包括源代码文件以及测试证据，如屏幕截图或简短的测试日志。部分考点也可能要求你将测试注释直接写入代码中。请务必仔细阅读试卷上的说明，确认你需要提交的内容。

2. Understanding the Problem Statement | 理解问题描述

Carefully read the entire scenario and requirements before you start typing any code. Highlight or note down the key inputs, processes and outputs. Look for constraints, data types and any validation rules that must be implemented. Misunderstanding the problem is the quickest way to lose marks.

在动手编写任何代码之前，仔细阅读整个场景和需求描述。标出或记下关键输入、处理和输出。留意约束条件、数据类型以及必须实现的验证规则。误解问题是丢分的最快途径。

Identify the main tasks: they might be separated into parts, such as (a) reading from a file, (b) calculating a result, and (c) displaying or saving results. The mark allocation will give you a hint about the complexity of each part — consider spending more time on heavier-weighted sections.

明确主要任务：它们可能会被分成若干部分，例如 (a) 从文件读取数据，(b) 计算结果，(c) 显示或保存结果。分数分配会暗示各部分的复杂度——建议在分值更重的部分投入更多时间。

3. Algorithm Design and Planning | 算法设计与规划

Even in a timed exam, spending 5–10 minutes planning saves time later. Sketch a simple structure chart or flowchart, or write pseudocode annotations in comments at the top of your file. This helps you organise logic and spot potential issues early.

即使在限时考试中，花5到10分钟做规划也能为后续节省时间。画一个简单的结构图或流程图，或者在文件顶端用注释写下伪代码。这有助于你组织逻辑并及早发现潜在问题。

Break the problem into smaller reusable functions or procedures. For instance, separate functions for input validation, calculation and output formatting as modular code is easier to debug and test.

将问题分解为更小的可重用函数或过程。例如，将输入验证、计算和输出格式化分离为独立的函数，因为模块化代码更便于调试和测试。

4. Coding Best Practices | 编码最佳实践

Use meaningful variable and function names that reflect their purpose. For example, ‘student_mark’ is far better than ‘sm’ or ‘x’. Choose a consistent naming convention (camelCase or snake_case) and stick to it throughout your program.

使用反映其用途的有意义的变量和函数名。例如 ‘student_mark’ 比 ‘sm’ 或 ‘x’ 好得多。选择一种一致的命名规范（camelCase 或 snake_case）并在整个程序中坚持使用。

Pay attention to indentation, especially in languages like Python where indentation defines block structure. Consistent spacing makes your code more readable for the examiner and reduces the risk of logical errors.

注意缩进，特别是在像 Python 这样用缩进来定义代码块的语言中。一致的间距能让考官更容易阅读你的代码，并降低逻辑错误的风险。

Include inline comments to explain the purpose of complex logic, but avoid over-commenting obvious statements. For the WJEC assessment, brief comments on your solution approach can also serve as part of your evaluation evidence.

在复杂逻辑处添加行内注释解释其目的，但避免对显而易见的语句过度注释。在 WJEC 考核中，关于解决方案思路的简要注释也可作为评估证据的一部分。

5. Debugging and Testing | 调试与测试

Build a testing table (mentally or on paper) that covers normal data, boundary data and erroneous data for every input. Test your program progressively — do not wait until the very end. After writing a key section, run it immediately to check it behaves as expected.

为每项输入制定一个测试表（心理构思或纸上记录），涵盖正常数据、边界数据和异常数据。逐步测试你的程序，不要拖到最后。写完一个关键部分后，立即运行以检查其是否按预期工作。

Learn to diagnose common errors: syntax errors from missing colons or parentheses, runtime errors like division by zero, and logic errors that produce wrong results. Use print statements or the IDE’s debugger to trace variable values during execution.

学会诊断常见错误：遗漏冒号或括号导致的语法错误、除以零等运行时错误，以及产生错误结果的逻辑错误。使用打印语句或 IDE 的调试器来跟踪执行过程中的变量值。

If the exam requires evidence of testing, capture clear screenshots showing inputs and the corresponding outputs. Annotate them briefly so the examiner can see what you were testing.

若考试要求提供测试证据，请截取清晰的屏幕截图，展示输入和对应的输出。对截图添加简短注释，以便考官了解你测试的内容。

6. File Handling and Data Structures | 文件处理与数据结构

Practical exams often involve reading from or writing to text files. Ensure you know how to open files in the correct mode (‘r’ for reading, ‘w’ for writing, ‘a’ for appending) and how to handle exceptions such as FileNotFoundError. Always close files, or better, use a ‘with’ statement (in Python) to manage resources automatically.

实践考试常常涉及读/写文本文件。确保你了解如何以正确的模式打开文件（’r’ 读取，’w’ 写入，’a’ 追加）以及如何处理 FileNotFoundError 等异常。文件用完后务必关闭，或更推荐使用 ‘with’ 语句（Python）来自动管理资源。

You may need to store data using lists, arrays, dictionaries (key-value pairs) or records/classes. Choose the structure that makes searching, sorting or updating your data most efficient. For instance, a dictionary is ideal for rapid lookups by a unique key.

你可能需要用列表、数组、字典（键-值对）或记录/类来存储数据。选择能让数据搜索、排序或更新最高效的结构。例如，字典非常适合通过唯一键进行快速查找。

7. Time Management During the Exam | 考试中的时间管理

At the start, scan the whole task and allocate approximate time slots: perhaps 10 minutes for planning, 60–70 minutes for coding and testing, 20–25 minutes for final checks and evidence gathering, leaving buffer time. Stick to your plan but be flexible if you get stuck.

考试开始时，快速浏览全部任务并分配大致时间段：比如10分钟规划，60-70分钟编码与测试，20-25分钟最终检查和收集证据，并留出缓冲时间。按计划执行，但如果卡住了要灵活调整。

If a bug is taking too long to fix, note it in comments, leave a placeholder solution, and move on. You can return to it later with fresh eyes. A partially working program that demonstrates the correct approach can still earn significant marks.

如果某个错误耗时太久仍未解决，在注释中说明，保留一个占位解决方案，然后继续推进。你可以稍后再回头用新的视角处理。一个能部分运行并展示了正确方法的程序仍然能获得可观的分数。

8. Common Mistakes to Avoid | 常见错误避免

Ignoring input validation — the scenario will nearly always require checking that user inputs are within an expected range or format.

忽略输入验证——题目场景几乎总是要求检查用户输入是否在预期范围或格式内。
Hardcoding values instead of using variables or named constants — if a data value appears in the scenario description, make it configurable.

硬编码数值而不用变量或命名常量——如果某个数据值出现在场景描述中，要让它可配置。
Failing to initialise accumulators or counters — this leads to unpredictable results or runtime errors.

忘记初始化累加器或计数器——这会导致不可预测的结果或运行时错误。
Using global variables excessively — this makes the program harder to debug and understand.

过度使用全局变量——这使得程序更难调试和理解。
Not reading the file format correctly — a common pitfall is missing newline characters or extra spaces at the end of lines when parsing data from a file.

未能正确读取文件格式——一个常见陷阱是解析文件数据时忽略了行尾的换行符或多余空格。

9. Using Provided Code and Libraries | 使用提供的代码和库

Sometimes the exam paper provides skeleton code or pre-written functions. Do not waste time re-writing them. Understand what they do and how to call them. If the skeleton contains a specific data structure, build your solution around it rather than replacing it.

有时试卷会提供骨架代码或预先写好的函数。不要浪费时间重写它们。理解它们的功能以及如何调用。如果骨架代码包含特定的数据结构，应基于该结构构建你的解决方案，而不是替换它。

Know the standard libraries allowed in the exam. For Python, this might include ‘math’, ‘random’, ‘os’, ‘datetime’ and ‘csv’. Use built-in functions whenever possible, as they are efficient and reduce the chance of introducing errors.

了解考试中允许使用的标准库。以 Python 为例，可能包括 ‘math’、’random’、’os’、’datetime’ 和 ‘csv’。尽可能使用内置函数，因为它们效率高且能减少引入错误的机会。

10. Commenting and Documentation | 注释与文档

Use comments strategically to explain your approach, document assumptions, and highlight key decision points. At the top of each function, a brief one-line comment describing its purpose, parameters, and return value can make your logic crystal clear to the marker.

有策略地使用注释来解释你的方法、记录假设并标出关键决策点。在每个函数的顶部，用一行简短的注释描述其用途、参数和返回值，能让你的逻辑对阅卷人一目了然。

However, do not write a comment for every single line. Focus on the ‘why’ rather than the ‘what’. For example, ‘// Using a while loop because the number of iterations is unknown’ is more valuable than ‘// loop runs 10 times’.

但是，不必给每一行都写注释。重在解释“为什么”而不是“做什么”。例如，’// 使用 while 循环，因为迭代次数未知’ 比 ‘// 循环运行10次’ 更有价值。

11. Evaluation and Reflection | 评估与反思

If the task includes a reflective or evaluative section, discuss what worked well, any limitations of your solution, and how you could improve it with more time. Be specific — mention the constraints you faced and outline possible alternative approaches, such as using a different sorting algorithm or a more advanced data structure.

如果任务包含反思或评估环节，讨论哪些地方做得好、解决方案的局限性，以及如果时间充裕你会如何改进。要具体说明——提及你遇到的限制并概述可能的替代方案，比如使用不同的排序算法或更高级的数据结构。

Back up your evaluation with evidence from your testing. For example, point to a test case that revealed a boundary issue, and explain how you fixed it. This demonstrates strong analytical skills aligned with AO3 ‘Evaluate’.

用你的测试证据支撑评估。例如，指出某个暴露出边界问题的测试用例，并解释你是如何修复的。这能展示与 AO3 “评价” 目标相符的强大分析能力。

12. Final Checks and Submission | 最终检查与提交

In the last 10–15 minutes, systematically check that your program compiles and runs without errors. Re-run a sample of test cases with the expected inputs and verify the outputs. Ensure all filenames match the submission requirements exactly.

在最后10-15分钟里，系统检查你的程序能否编译并无错误运行。重新运行一部分带有预期输入的测试用例并核对输出。确保所有文件名与提交要求完全一致。

Double-check that you have not left any temporary debug print statements active and that your code is as readable as possible. Save your work in the specified location and confirm that the files are accessible. If screenshot evidence is required, verify they are clear and correctly named.

再次检查是否遗留了任何调试用打印语句，确保代码尽可能易读。将作品保存到指定位置并确认文件可访问。如果需要屏幕截图证据，确认它们清晰且命名正确。

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

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

Year 12 WJEC Computer Science: Key Points for Practical Assessment | Year 12 WJEC 计算机：实践考核要点