📚 SQA Advanced Higher Computing: Report Writing Framework and Exemplar | SQA高级计算机：论文写作框架与范文
Writing the Advanced Higher Computing Science project report is often the most demanding part of the qualification. It requires you to demonstrate not only technical skills but also the ability to plan, analyse, design, implement, test and evaluate a substantial piece of software. This article breaks down the recommended structure and provides practical exemplar text to help you build a high-scoring report.
撰写SQA高级计算机科学项目报告往往是整个资格认证中最具挑战性的部分。它不仅要求你展示技术能力，还需要你证明自己能够规划、分析、设计、实施、测试和评估一个完整的软件作品。本文拆解了推荐的结构框架，并提供了实用的范文片段，帮助你构建一份高分报告。
1. Understanding the SQA Project Report | 理解SQA项目报告
The Advanced Higher Computing Science project is worth 80 marks out of a total of 150 for the course. The report must present a real, working software solution that you have developed independently, following a systematic process. Markers look for evidence of a clear methodology, thorough documentation, and critical reflection.
高级计算机科学项目占课程总分150分中的80分。报告必须呈现一个真实的、可工作的软件解决方案，该方案由你独立开发，并遵循系统化流程。阅卷人看重清晰的方法论、完整的文档记录以及批判性的反思。
Typical project genres include database-driven information systems, mobile apps, web applications, or simulation programs. No matter the topic, the report must follow a logical structure that mirrors the software development lifecycle: Analysis, Design, Implementation, Testing, and Evaluation.
典型的项目类型包括数据库驱动的信息系统、移动应用、网页应用或模拟程序。无论选题如何，报告都必须遵循与软件开发生命周期相对应的逻辑结构：分析、设计、实施、测试和评价。
2. Overall Report Structure | 整体报告结构
SQA does not prescribe a single fixed layout, but a successful report almost always includes these core chapters:
SQA并未规定唯一的固定布局，但一份成功的报告几乎总是包含以下核心章节：
| Section | Typical Marks Weight | 章节 |
|---|---|---|
| Introduction | 4–6 | 引言 |
| Analysis | 16–20 | 分析 |
| Design | 16–20 | 设计 |
| Implementation | 16–20 | 实施 |
| Testing | 12–14 | 测试 |
| Evaluation | 6–8 | 评价 |
| References & Appendices | – | 参考文献和附录 |
Each section should start on a new page and be clearly numbered. Use a consistent font (e.g. 11 pt Arial or Calibri) and 1.5 line spacing. The report typically runs between 40 and 70 A4 pages including screenshots and diagrams.
每个部分应另起一页并清晰编号。使用统一字体（如11磅Arial或Calibri）和1.5倍行距。报告通常在40到70页A4纸之间，包括屏幕截图和图表。
3. Writing the Introduction | 撰写引言
The introduction sets the scene. It must identify the problem, the client (real or fictional), and the aim of the project. Be specific about what the software will do and why it is needed.
引言设定背景。必须明确说明问题、客户（真实的或虚构的）以及项目目标。具体描述软件将要做什么，以及为什么需要它。
Exemplar (English): “This project was undertaken for ‘Green Leaf Bookshop’, a small independent retailer that currently manages stock manually using paper records. The aim is to develop a bespoke stock management system that will allow staff to add, update, search and delete book records, track sales, and generate low-stock alerts. The software will be developed in Python with an SQLite database, and will feature a graphical user interface built with Tkinter.”
范文（中文）：“本项目是为「绿叶书店」而做，这是一家小型独立零售商，目前使用纸质记录手工管理库存。目标是开发一个定制的库存管理系统，让员工能够添加、更新、搜索和删除书籍记录、追踪销售，并生成低库存提醒。软件将使用Python开发，数据库采用SQLite，并用Tkinter构建图形用户界面。”
Keep the introduction concise — about half a page. Avoid technical details that belong in later chapters.
引言要简洁——大约半页。避免在此处加入属于后续章节的技术细节。
4. Conducting and Documenting Analysis | 进行分析并记录
The analysis chapter is the foundation of your project. It must demonstrate a thorough understanding of the problem from the user’s perspective and translate that understanding into clear, testable requirements.
分析章节是项目的基础。它必须展现出你从用户角度对问题的透彻理解，并将这种理解转化为清晰、可测试的需求。
Key elements to include: (1) description of current system and its limitations, (2) stakeholder interviews or questionnaires, (3) a comprehensive requirements specification divided into functional, non-functional and user interface requirements, (4) data flow diagrams or use case diagrams, and (5) a clear scope boundary.
需要包含的关键要素：（1）当前系统描述及其局限性，（2）利益相关者访谈或问卷，（3）划分为功能性、非功能性和用户界面需求的综合需求规格说明，（4）数据流图或用例图，以及（5）明确的范围边界。
Exemplar requirement: “FR-04: The system must allow a user to search for a book by title, author or ISBN. The search must return results within 2 seconds for a database of up to 10,000 records.”
需求范例句：“FR-04：系统必须允许用户按书名、作者或ISBN搜索图书。对于最多10,000条记录的数据库，搜索必须在2秒内返回结果。”
Always number your requirements for traceability. Use a table to organise them, and add a column for ‘priority’ (e.g., Must, Should, Could). You should also document any legal or ethical considerations, such as GDPR compliance when storing customer names.
务必给需求编号以便追溯。用表格来组织需求，并添加一列「优先级」（例如：必须、应该、可以）。你还应记录任何法律或伦理考量，比如存储客户姓名时的GDPR合规性。
5. Designing the Solution | 设计解决方案
The design chapter translates requirements into a blueprint for implementation. It should cover user interface design, data structure design, and algorithmic design. Use standard diagramming techniques — wireframes, entity-relationship diagrams (ERDs), flowcharts, and structure charts.
设计章节将需求转化为实施蓝图。它应涵盖用户界面设计、数据结构设计和算法设计。使用标准的图表技术——线框图、实体关系图（ERD）、流程图和结构图。
Exemplar ERD description: “The database consists of three core entities: Book (BookID, Title, Author, ISBN, Price, StockQuantity), Sale (SaleID, Date, TotalAmount), and SaleItem (ItemID, SaleID, BookID, Quantity). A one-to-many relationship exists between Sale and SaleItem, and between Book and SaleItem.”
ERD描述范文：“数据库由三个核心实体组成：Book（BookID, Title, Author, ISBN, Price, StockQuantity）、Sale（SaleID, Date, TotalAmount）和SaleItem（ItemID, SaleID, BookID, Quantity）。Sale与SaleItem之间、Book与SaleItem之间均为一对多关系。”
For the user interface, include annotated wireframes of every screen. Describe navigation paths and justify design choices with reference to usability principles (e.g., Nielsen’s heuristics). The algorithmic design should provide pseudocode for complex operations, such as the low-stock alert algorithm or the stock update procedure.
对于用户界面，要包含每个页面的带注释线框图。描述导航路径，并参照可用性原则（例如尼尔森启发式原则）来论证设计选择。算法设计应提供复杂操作的伪代码，比如低库存提醒算法或库存更新程序。
6. Implementation: Showing the Process | 实施：展示过程
The implementation chapter is not just a code dump. It should explain how you built the system, highlight interesting challenges, and showcase key code snippets alongside explanations. Maintain a development log as you work and include excerpts in the report.
实施章节不只是代码堆砌。它应当解释你如何构建系统，突出有趣的挑战，并展示关键代码片段及其说明。开发过程中要持续记录开发日志，并在报告中摘录部分内容。
Structure this chapter by module or feature. For example, you might have subsections: 6.1 Database Connection Module, 6.2 User Authentication, 6.3 Book Search and Filter. In each, show a short code snippet (5–15 lines) and immediately explain what it does and why you chose that particular approach.
按模块或功能来组织本章。例如，你可以设置子章节：6.1 数据库连接模块，6.2 用户认证，6.3 图书搜索与筛选。在每一部分，展示一小段代码（5-15行），并立即解释它做什么以及为什么选择这种特定方法。
Exemplar snippet with explanation: “The following function uses a parameterised SQL query to prevent SQL injection attacks. By passing the user input as a tuple, we ensure the database treats it as data, not executable code.”
带解释的代码片段范文：“以下函数使用了参数化SQL查询以防止SQL注入攻击。通过将用户输入作为元组传递，我们确保数据库将其视为数据而非可执行代码。”
def search_book(title):
cursor.execute("SELECT * FROM Book WHERE Title LIKE ?", ('%'+title+'%',))
return cursor.fetchall()
Remember to refer back to your design documents and explain any deviations. This demonstrates critical thinking.
记得回顾你的设计文档并解释任何偏差。这体现了批判性思维。
7. Testing Strategies and Reporting | 测试策略与报告
Testing must be planned and systematic. The testing chapter should present a test plan, test data (normal, boundary, exceptional), actual results, and evidence such as screenshots. A table format works best here.
测试必须有计划且系统化。测试章节应展示测试计划、测试数据（正常、边界、异常）、实际结果以及截图等证据。这里最适合使用表格格式。
Example test table structure:
测试表格结构示例：
| Test ID | Requirement | Description | Input Data | Expected Outcome | Actual Outcome | Pass/Fail |
|---|---|---|---|---|---|---|
| TC-07 | FR-04 | Search with partial title match | “orwell” | Display all books containing “orwell” | 1984, Animal Farm shown | Pass |
You should also discuss any testing tools used (e.g., automated unit tests with unittest or pytest) and include the test code in an appendix. A section on user acceptance testing, with feedback from your client, adds strong validity.
你还应讨论使用的测试工具（例如，使用unittest或pytest进行的自动化单元测试），并将测试代码放在附录中。若有一节关于用户验收测试，并附上客户反馈，会大大增强项目的可信度。
8. Evaluation and Reflection | 评价与反思
The evaluation chapter is your opportunity to step back and objectively assess what you have achieved. Compare the final product against the original requirements. What worked well? What proved difficult? What would you do differently next time?
评价章节是你退后一步、客观评估自己工作成果的机会。将最终产品与最初的需求进行对比。哪些做得好？哪些困难重重？下次你会采取什么不同做法？
A strong evaluation uses specific evidence. For example: “Requirement FR-04 (search speed) was fully met; timing tests showed an average response of 0.8 seconds, well within the 2-second target. However, the barcode scanning feature (FR-09) was not implemented due to hardware compatibility issues, though the system provides a manual ISBN entry workaround.”
一份有力的评价会使用具体证据。例如：“需求FR-04（搜索速度）完全满足；计时测试显示平均响应时间为0.8秒，远在2秒目标内。然而，由于硬件兼容性问题，条码扫描功能（FR-09）未能实现，但系统提供了手动ISBN输入替代方案。”
Include a personal reflection on skills gained, challenges overcome, and lessons learned about project management and software development. This shows maturity and is highly valued by markers.
还要包含个人反思，谈谈获得的技能、克服的挑战，以及在项目管理和软件开发方面学到的经验教训。这体现了你的成熟思考，阅卷人非常看重这一点。
9. Final Presentation Tips | 最终呈现技巧
The way your report looks matters. Use a clear, professional structure with consistent headings. Number all pages and figures. Every diagram must have a caption and be referenced from the text. Avoid dense blocks of text — use bullet points, tables, and screenshots to break up the content.
报告的外观很重要。采用清晰、专业的结构，标题一致。所有页码和图表都要编号。每个图表必须有标题，并在正文中引用。避免密集的大段文字——使用项目符号、表格和截图来分割内容。
Proofread for spelling and grammar errors. Ask a peer or teacher to read through your report for clarity. Common pitfalls include: forgetting to label axes on charts, unclear screenshots, missing captions, and failing to cross-reference requirements in the testing section.
校对拼写和语法错误。请同学或老师通读你的报告以确保清晰。常见的问题包括：图表没标坐标轴标签、截图模糊不清、缺少标题，以及在测试部分没有交叉引用需求。
10. References and Academic Integrity | 参考文献与学术诚信
You must acknowledge all sources, including any code libraries, tutorials, or articles you used. Use a consistent referencing style such as Harvard or APA. Cite in-text and provide a full reference list at the end. Plagiarism, even of code, is taken very seriously by SQA.
你必须声明所有来源，包括你使用的任何代码库、教程或文章。使用统一的参考文献格式，如哈佛或APA格式。在正文中引用，并在结尾提供完整的参考文献列表。SQA对剽窃行为，包括代码剽窃，处理非常严肃。
For open-source code or libraries, state the licence and clearly mark which parts of your program use them. The Implementation chapter should clearly distinguish between your own code and third-party components.
对于开源代码或库，要说明许可证，并清晰地标明你程序的哪些部分使用了它们。实施章节应清楚地区分你自己的代码和第三方组件。
11. Using the Exemplar as a Guide | 以范文为参考
The excerpts in this article are drawn from a hypothetical stock management project. They illustrate the level of detail and the analytical tone expected. Do not copy them directly, but use them as a model to shape your own writing. Your own report must be built around your unique project and decisions.
本文中的摘录均取自一个假设的库存管理项目。它们展示了预期的详细程度和分析性语气。不要直接复制，而应将其作为模型来塑造你自己的写作。你自己的报告必须围绕你独特的项目和决策来构建。
Remember that the best reports demonstrate consistent thinking from Analysis through to Evaluation. When you write, continually ask yourself: “Does this section link back to my requirements?” and “Have I justified this choice?” If you can answer yes, you are on the right track.
请记住，最优秀的报告展示出从分析到评价的一贯思维。写作时，不断问自己：“这一节是否与我的需求相关联？”以及“我是否论证了这个选择？”如果你能给出肯定回答，那么你就走在了正确的道路上。
12. Summary Checklist | 总结清单
Before submitting, go through this quick checklist:
提交前，快速检查以下清单：
- Introduction: Clear problem, client, aim
- Analysis: Numbered requirements, diagrams, client input
- Design: ERD, wireframes, pseudocode, justification
- Implementation: Annotated code, references to design
- Testing: Full test table, evidence, user feedback
- Evaluation: Requirement-by-requirement comparison, personal reflection
- Presentation: Consistent formatting, clear headings, numbered pages
- References: Acknowledged all sources
- 引言：清晰的问题、客户、目标
- 分析：编号的需求、图表、客户输入
- 设计：ERD、线框图、伪代码、论证
- 实施：带注释的代码、对设计文档的引用
- 测试：完整的测试表格、证据、用户反馈
- 评价：逐条需求对比、个人反思
- 呈现：格式一致、标题清晰、页码
- 参考文献：声明所有来源
A well-structured report not only earns high marks but also builds skills that are invaluable for university and professional software development. Good luck!
一份结构良好的报告不仅能获得高分，还能培养大学学习和专业软件开发中极为宝贵的技能。祝你好运！
Published by TutorHao | Computing Revision Series | aleveler.com
更多咨询请联系16621398022（同微信）
屏轩国际教育cambridge primary/secondary checkpoint, cat4, ukiset,ukcat,igcse,alevel,PAT,STEP,MAT, ibdp,ap,ssat,sat,sat2课程辅导，国外大学本科硕士研究生博士课程论文辅导