📚 Year 13 OCR Computer Science: Practical Assessment Key Points | Year 13 OCR 计算机：实践考核要点
The Practical Assessment (Programming Project) is a core component of the OCR A Level Computer Science H446, contributing 20% of your final grade. Success depends on a methodical approach encompassing analysis, design, development, testing and evaluation.
实践考核（编程项目）是OCR A Level计算机科学H446的核心组成部分，占最终成绩的20%。成功取决于涵盖分析、设计、开发、测试和评估的系统性方法。
1. Understanding the NEA Requirements | 理解非考试评估要求
Read the official OCR specification and guidance document carefully. Your project must solve a genuine problem for a real end user, not a trivial exercise. The mark scheme rewards depth, not breadth, so choose a problem that allows you to demonstrate complex programming skills.
仔细阅读OCR官方规格和指导文件。你的项目必须为真实终端用户解决一个实际问题，而不是一个琐碎的练习。评分方案奖励深度而非广度，因此选择一个能让你展示复杂编程技能的问题。
You must produce a report that covers analysis, design, development, testing and evaluation. Ensure your documentation clearly maps to each marking criterion.
你必须撰写一份涵盖分析、设计、开发、测试和评估的报告。确保文档清晰地对应每项评分标准。
2. Stakeholder Identification and Problem Analysis | 利益相关者识别与问题分析
Conduct a thorough analysis by interviewing your client. Identify functional requirements (what the system must do) and non-functional requirements (usability, performance, security). Use tools such as use case diagrams or context diagrams to visualise the system boundary.
通过采访客户进行全面分析。识别功能需求（系统必须做什么）和非功能需求（可用性、性能、安全性）。使用用例图或上下文图等工具将系统边界可视化。
Document the current system’s limitations and define measurable success criteria. This becomes the foundation for your evaluation later.
记录当前系统的局限性，并定义可衡量的成功标准。这将为后续的评估奠定基础。
3. Computational Thinking and Decomposition | 计算思维与分解
Break the problem into manageable sub-problems. Apply abstraction to focus on relevant details and ignore unnecessary complexity. Decomposition helps you plan modules and assign tasks if working in a team, but for individual projects it clarifies the logical structure.
将问题分解为可管理的子问题。应用抽象化来关注相关细节并忽略不必要的复杂性。分解有助于规划模块，并在团队合作时分配任务，但对于个人项目，它能理清逻辑结构。
Identify data flows and processing stages. Use structure diagrams or hierarchy charts to show the relationships between components.
识别数据流和处理阶段。使用结构图或层次图来展示组件之间的关系。
4. Designing with UML and Flowcharts | 使用UML与流程图进行设计
Create a detailed design that includes UML class diagrams for object-oriented projects, entity-relationship diagrams if using databases, and flowcharts or pseudocode for key algorithms. The design must be sufficiently detailed so that a third party could implement the solution.
创建详细的设计，包括面向对象项目的UML类图、若使用数据库则需实体关系图，以及关键算法的流程图或伪代码。设计必须足够详细，以便第三方能够实现该解决方案。
Consider user interface design: sketch wireframes or mock-ups. Justify your design choices in the report, linking them back to the requirements.
考虑用户界面设计：绘制线框图或模型。在报告中解释你的设计选择，并将其与需求联系起来。
5. Selecting Data Structures and Algorithms | 选择数据结构与算法
Choose appropriate data structures such as arrays, records, lists, stacks, queues, trees or hash tables based on the problem’s needs. Explain the time and space complexity of your algorithms using Big O notation, e.g., O(n log n) or O(n²).
根据问题需求选择合适的数据结构，如数组、记录、列表、栈、队列、树或哈希表。使用大O表示法解释算法的时间与空间复杂度，例如O(n log n)或O(n²)。
Implement searching and sorting algorithms if required, and state why you selected them. Evidence your understanding by including code snippets and performance analysis.
如有需要，实现搜索和排序算法，并说明选择它们的原因。通过包含代码片段和性能分析来证明你的理解。
6. Coding Best Practices and Code Quality | 编码最佳实践与代码质量
Write clean, maintainable code using meaningful variable names, consistent indentation and comments that explain why a section exists, not what it does. Use modular programming: break code into functions, procedures or classes with single responsibilities.
编写干净、可维护的代码，使用有意义的变量名、一致的缩进和注释，注释要解释某段代码存在的理由，而非描述其做什么。使用模块化编程：将代码分解为单一职责的函数、过程或类。
Apply defensive programming: validate inputs, handle exceptions gracefully, and use assertions to catch bugs early. Employ version control (e.g., Git) to track changes and back up your progress.
采用防御性编程：验证输入、优雅地处理异常，并使用断言尽早捕获错误。利用版本控制（如Git）跟踪变更并备份进度。
7. Comprehensive Testing Strategies | 综合测试策略
Plan a testing strategy that includes unit tests for individual modules, integration tests for combined components, and system tests for end-to-end functionality. Create test tables with unique test IDs, test data, expected results and actual results. Show evidence through screenshots or log excerpts.
规划测试策略，包括针对单个模块的单元测试、组合组件的集成测试以及端到端功能的系统测试。创建测试表格，包含唯一测试编号、测试数据、预期结果和实际结果。通过截图或日志摘录提供证据。
Perform boundary testing and erroneous data testing. For user interfaces, conduct usability testing with real users. Document any bugs found, their fixes and retest results to demonstrate iterative improvement.
执行边界测试和错误数据测试。对于用户界面，与真实用户进行可用性测试。记录发现的任何错误、修复方法及重新测试结果，以展示迭代改进。
8. Iterative Development and Prototyping | 迭代开发与原型设计
Adopt an iterative or agile approach: build a core version early, gather feedback from the client and refine the product. Create a development log or diary that records each cycle, challenges encountered and solutions.
采用迭代或敏捷方法：尽早构建核心版本，收集客户反馈并改进产品。创建开发日志或日记，记录每个周期、遇到的挑战及解决方案。
Consider prototyping a key feature (e.g., a database connection) before full-scale implementation. This reduces risk and helps you validate technical choices.
考虑在全规模实施前，对关键功能（如数据库连接）进行原型设计。这可以降低风险，并帮助你验证技术选择。
9. Documentation and Report Writing | 文档与报告撰写
Produce a well-structured report with a table of contents, clear headings, and appendices for full code listings. Reference external sources appropriately. The report should tell a coherent story: from the problem to the solution and its evaluation.
撰写结构良好的报告，包含目录、清晰的标题以及用于完整代码列表的附录。适当引用外部资源。报告应讲述一个连贯的故事：从问题到解决方案及其评估。
Include annotated code snippets in the development section to explain complex routines. Use screenshots to illustrate working features, not just code. Proofread to avoid spelling and grammar errors that could detract from professionalism.
在开发部分包含带注释的代码片段以解释复杂的例程。使用截图来展示可用的功能，而不仅仅是代码。仔细校对，避免拼写和语法错误损害专业性。
10. Evaluation and Critical Reflection | 评估与批判性反思
Evaluate the final product against the success criteria you set during analysis. Be honest about limitations and discuss what you would do differently in a future version. Compare your solution to existing alternatives, explaining any trade-offs.
对照你在分析阶段设定的成功标准评估最终产品。坦诚地讨论其局限性，并说明在未来的版本中你会做出哪些不同的决定。将你的解决方案与现有替代方案进行比较，解释任何权衡取舍。
Seek end-user feedback and incorporate it into the evaluation. This demonstrates a genuine consideration of the client’s perspective. Reflect on your personal learning and technical growth throughout the project.
寻求终端用户的反馈，并将其纳入评估。这展示了对客户视角的真正考虑。反思你在整个项目中的个人学习和技术成长。
11. Common Pitfalls and Tips for Success | 常见陷阱与成功技巧
Pitfall: choosing an overly ambitious project that cannot be completed on time. Tip: scope the project carefully and aim for depth in a few features rather than many shallow ones.
陷阱：选择一个过于宏伟而无法按时完成的项目。技巧：仔细界定项目范围，力求在少数几个功能上深入，而不是浅显地覆盖很多功能。
Pitfall: weak analysis leading to a mismatch between solution and client needs. Tip: revisit the client regularly and keep the requirements document alive.
陷阱：分析薄弱导致解决方案与客户需求不匹配。技巧：定期回访客户，并保持需求文档的动态更新。
Pitfall: neglecting evidence in testing and development. Tip: take screenshots, keep logs, and store versions to provide rich evidence for the report.
陷阱：忽视测试和开发中的证据。技巧：截取屏幕截图、保留日志并存储版本，以便为报告提供丰富的证据。
Published by TutorHao | Computer Science Revision Series | aleveler.com
更多咨询请联系16621398022（同微信）
屏轩国际教育cambridge primary/secondary checkpoint, cat4, ukiset,ukcat,igcse,alevel,PAT,STEP,MAT, ibdp,ap,ssat,sat,sat2课程辅导，国外大学本科硕士研究生博士课程论文辅导Cancel reply