📚 GCSE WJEC Computer Science: Software Engineering Revision Notes | GCSE WJEC 计算机：软件工程 考点精讲
Software engineering is the backbone of modern computing; it provides the structured methods needed to build reliable, maintainable, and efficient software. For the WJEC GCSE Computer Science exam, you are expected to understand the complete software development process, from gathering requirements through to retirement. This revision guide breaks down every essential concept, model, and practice into clear, bilingual explanations, helping you master topics such as the SDLC, testing strategies, coding standards, and professional responsibilities.
软件工程是现代计算的基石，它提供了构建可靠、可维护和高效软件所需的结构化方法。在 WJEC GCSE 计算机科学考试中，你不仅需要理解从需求收集到软件退役的完整开发流程，还要掌握多种开发模型、测试策略、编码规范以及专业责任。本复习指南将每个关键概念拆解为清晰的双语解释，帮助你牢固掌握软件开发生命周期、测试方法、编码标准和伦理考量等核心考点。
1. What Is Software Engineering? | 什么是软件工程？
Software engineering is the application of a systematic, disciplined, and quantifiable approach to the development, operation, and maintenance of software. It treats software creation as an engineering discipline, not merely as coding.
软件工程是以系统化、规范化、可量化的方法来开发、运行和维护软件的过程。它将软件创建视为一门工程学科，而不仅仅是写代码。
Unlike ad-hoc programming, software engineering emphasises team collaboration, project management, quality assurance, and documentation. The goal is to produce software that is fit for purpose, within budget, and easy to adapt as requirements change.
与随意的编程不同，软件工程强调团队协作、项目管理、质量保证和文档编制。其目标是交付符合既定用途、预算之内且易于随需求变化而调整的软件。
In the WJEC specification, this topic bridges “Understanding Computer Science” with “Solving Problems Using Computers,” requiring you to appreciate both theoretical models and practical application.
在 WJEC 大纲中，该主题连接了 “理解计算机科学” 和 “用计算机解决问题” 两个单元，要求你既要理解理论模型，又要知道如何实际应用。
2. The Software Development Life Cycle (SDLC) | 软件开发生命周期
The SDLC is a framework that describes the stages a software project goes through, from initial idea to final withdrawal. It provides a shared vocabulary for developers and stakeholders, ensuring everyone follows the same roadmap.
软件开发生命周期是一个框架，描述了软件项目从最初构思到最终退役所经历的各个阶段。它为开发人员和利益相关者提供了共同语言，确保所有人遵循同一路线图。
The core stages, although named slightly differently across models, are: analysis, design, implementation (coding), testing, installation/deployment, and maintenance. Some models add an explicit planning or feasibility step before analysis.
核心阶段包括：分析、设计、实现（编码）、测试、安装/部署以及维护。某些模型在分析之前还会增加明确的规划或可行性步骤。
For WJEC, you must be able to explain what happens at each stage and recognise that the SDLC is not a one-size-fits-all prescription but a template that can be adapted to different project needs.
就 WJEC 而言，你必须能解释每个阶段发生什么，并认识到 SDLC 不是一成不变的公式，而是一个可根据项目需求调整的模板。
- Analysis: Identify what the system must do. 分析阶段：确定系统必须做什么。
- Design: Decide how the system will be built. 设计阶段：决定如何构建系统。
- Implementation: Write and build the actual code. 实现阶段：编写并构建实际代码。
- Testing: Verify that the system works correctly. 测试阶段：验证系统正确运行。
- Installation: Deliver the system to users. 安装阶段：将系统交付给用户。
- Maintenance: Fix, improve and adapt the system over time. 维护阶段：随时间修复、改进和调整系统。
3. Waterfall Model | 瀑布模型
The waterfall model is a linear sequential approach in which each phase must be fully completed before the next begins. It is one of the earliest SDLC models and is easy to understand because of its straightforward flow: Analysis → Design → Implementation → Testing → Installation → Maintenance.
瀑布模型是一种线性顺序方法，每个阶段必须完全完成后才能进入下一阶段。它是最早的 SDLC 模型之一，因其流程直观（分析 → 设计 → 实现 → 测试 → 安装 → 维护）而容易理解。
Review points, often called “gate checks,” are placed between stages; you cannot go back to a previous phase without restarting the project or incurring significant cost. This makes the model rigid but well-suited for projects where requirements are clear and unlikely to change, such as embedded systems or safety-critical software.
各阶段之间设有评审点（常称为 “关卡检查”），你无法在不重启项目或付出巨大代价的情况下回到上一阶段。这使得该模型很死板，但非常适用于需求明确且不太可能变化的项目，如嵌入式系统或安全关键软件。
For the exam, be ready to identify advantages (clear structure, easy to manage, well-documented stages) and disadvantages (inflexible, no working software until late, poor handling of changing requirements).
考试中要能说出优点（结构清晰、易于管理、各阶段文档齐全）和缺点（缺乏弹性、后期才出现可运行的软件、难以应对需求变更）。
4. Agile Methodologies | 敏捷方法
Agile is a modern, iterative approach that breaks a project into small, manageable increments called sprints. Instead of waiting until the end of a long linear cycle, working software is delivered regularly, and requirements can evolve based on continuous user feedback.
敏捷是一种现代迭代方法，它将项目分解成称为冲刺的小型可管理增量。团队不用等到漫长线形周期结束，而是定期交付可用的软件，同时需求可根据持续的用户反馈演进。
A core principle of Agile, as expressed in the Agile Manifesto, is valuing “individuals and interactions over processes and tools” and “working software over comprehensive documentation.” Popular frameworks include Scrum, Kanban and Extreme Programming (XP).
敏捷宣言所表述的核心原则之一，是重视 “个体和互动高于流程和工具” 以及 “可工作的软件高于详尽的文档”。常见的敏捷框架包括 Scrum、看板和极限编程。
In WJEC questions, you might be asked to contrast waterfall with Agile. Highlight that Agile is more flexible, involves users throughout, and reduces the risk of delivering something nobody wants—but it can be harder to predict time and cost precisely.
在 WJEC 考题中，你可能会被要求对比瀑布与敏捷。要强调敏捷更灵活、用户全程参与，降低了交付无用产品的风险——但较难精确预测时间和成本。
5. Requirements Elicitation and Feasibility | 需求获取与可行性
Before any code is written, engineers must understand what the software should do. Requirements elicitation involves gathering information from clients, end users, and existing documentation through interviews, questionnaires, observation, and document analysis.
在编写任何代码之前，工程师必须了解软件应该做什么。需求获取是通过访谈、问卷、观察和文档分析从客户、最终用户和现有文档中收集信息的过程。
A feasibility study evaluates whether the proposed system is technically possible, economically justified, legally permissible, and operationally viable within the available timeframe. This early analysis prevents wasted effort on a project doomed to fail.
可行性研究评估所提议的系统在技术上是否可行、经济上是否合理、法律上是否允许以及是否能在规定时间内运营。这种早期分析可避免在注定失败的项目上浪费精力。
Common feasibility criteria you must know include: technical feasibility (do we have the technology?), economic feasibility (is it cost-effective?), legal feasibility (does it comply with laws like GDPR?), and operational feasibility (will the organisation accept it?).
你必须了解的常见可行性标准包括：技术可行性（我们有相应技术吗？）、经济可行性（是否划算？）、法律可行性（是否符合《通用数据保护条例》等法律？）和运营可行性（组织会接受吗？）。
6. Software Design and Modelling | 软件设计与建模
The design phase translates requirements into a blueprint for construction. It covers data structures, user interface layout, algorithms, and system architecture. Good design makes implementation faster and reduces errors.
设计阶段将需求转化为施工蓝图，涵盖数据结构、用户界面布局、算法和系统架构。良好的设计可加快实现速度并减少错误。
At GCSE level, you will encounter basic modelling tools such as flowcharts, structure diagrams, and pseudocode. These tools help communicate the logic and flow of the program before coding begins, allowing errors to be caught early.
在 GCSE 阶段，你会接触到基本的建模工具，如流程图、结构图和伪代码。这些工具可在编码开始前传递程序的逻辑和流程，从而尽早发现错误。
For example, a flowchart uses standard symbols—ovals for start/end, parallelograms for input/output, rectangles for processes, and diamonds for decisions—to represent an algorithm visually.
例如，流程图使用标准符号——椭圆表示开始/结束，平行四边形表示输入/输出，矩形表示处理过程，菱形表示决策——用可视化方式表示算法。
Design also considers which programming constructs (sequence, selection, iteration) and data types will be appropriate. Modular design, breaking a program into smaller subprograms, is strongly encouraged for maintainability.
设计阶段还会考虑哪些编程结构（顺序、选择、迭代）和数据类型比较合适。模块化设计——将程序拆分成较小的子程序——被大力提倡，以提升可维护性。
7. Implementation and Coding Standards | 实现与编码规范
Implementation is the stage where the design is turned into executable code using a chosen programming language. However, producing syntactically correct code is not enough; professional developers follow strict coding standards to ensure consistency and readability.
实现阶段是使用所选编程语言将设计转化为可执行代码的阶段。然而，仅写出语法正确的代码是不够的；专业开发人员遵循严格的编码标准，以确保一致性和可读性。
Key conventions include meaningful identifier names, consistent indentation, appropriate use of comments, and avoiding “magic numbers” by using constants. These practices make it easier for other programmers (or your future self) to understand and maintain the code.
关键的编码约定包括：有意义的标识符命名、一致的缩进、恰当地使用注释，以及通过使用常量来避免 “魔数”。这些实践能让其他程序员（或未来的你）更轻松地理解和维护代码。
In the WJEC exam, you could be asked to identify errors or suggest improvements in a given code snippet. Look for poorly named variables (x, y for marks), missing comments, or inconsistent indentation, and explain how these hinder maintainability.
在 WJEC 考试中，你可能会被要求识别给定代码片段中的错误或提出改进建议。应关注命名不佳的变量（如用 x、y 表示分数）、缺少注释或不一致的缩进，并解释这些会如何妨碍可维护性。
8. Testing Strategies | 测试策略
Testing verifies that software behaves as expected and is essential for quality assurance. The two main approaches emphasised at GCSE are black-box testing and white-box testing.
测试验证软件是否按预期运行，是质量保证的关键。GCSE 重点强调的两种主要方法是黑盒测试和白盒测试。
Black-box testing examines the software’s functionality without looking at the internal code structure. Testers design test cases based on the specification; they use typical (normal), boundary, and erroneous data to check that the system handles all situations correctly.
黑盒测试在不查看内部代码结构的情况下检查软件功能。测试人员根据规格说明书设计测试用例，使用典型（正常）数据、边界数据和错误数据来检查系统是否正确处理所有情况。
- Normal data: values that should be accepted, like 55 for a test score out of 100. 正常数据：应该被接受的值，如百分制成绩中 55 分。
- Boundary data: values at the limits, such as 0, 1, 99, 100 for a mark out of 100. 边界数据：处于界限上的值，比如百分制分数的 0、1、99、100。
- Erroneous data: values that should be rejected, like -5 or 150 for that same test score. 错误数据：应当被拒绝的值，如同样的分数 -5 或 150。
White-box testing, by contrast, uses knowledge of the code to design tests that exercise every possible path, branch, and loop. The aim is to achieve high statement coverage and decision coverage, verifying that each line and logic condition works under test.
相比之下，白盒测试利用对代码的了解来设计能执行每一条可能路径、分支和循环的测试。其目标是达到较高的语句覆盖率和判定覆盖率，验证每行代码和每个逻辑条件在测试下都能正常工作。
You should also remember that testing is not debugging: testing finds the presence of defects; debugging is then used to locate and fix the cause.
你还应记住测试不是调试：测试发现缺陷的存在；调试则用于定位并修复根本原因。
9. Debugging and Error Classification | 调试与错误分类
Debugging is the process of identifying, isolating, and correcting errors in a program. Effective debugging relies on a methodical approach, using diagnostic tools and techniques such as breakpoints, watch windows, and step-through execution.
调试是识别、隔离和纠正程序错误的过程。有效的调试依赖于有条理的方法，并使用断点、监视窗口和单步执行等诊断工具和技术。
Errors encountered during development fall into three main categories: syntax errors, logic errors, and runtime errors. Understanding the differences is a common exam requirement.
开发中遇到的错误分为三大类：语法错误、逻辑错误和运行时错误。理解它们的区别是常见的考试要求。
A syntax error occurs when the code violates the language’s grammatical rules, such as a missing colon in Python or a misspelt keyword. The program will not run until these are fixed; the interpreter or compiler usually provides helpful line numbers.
语法错误发生在代码违反语言语法规则时，例如 Python 中缺少冒号或关键字拼写错误。在修正之前程序无法运行，解释器或编译器通常会给出有用的行号。
A logic error is more subtle: the program runs without crashing but produces incorrect results, like computing an average incorrectly. These are tracked down by carefully checking algorithms, variable values, and control flow.
逻辑错误更为隐蔽：程序运行无崩溃，但产生错误结果，如错误地计算平均值。需通过仔细检查算法、变量值和控制流来排查。
A runtime error occurs during program execution, for example, dividing by zero or attempting to open a non-existent file. The program may crash or throw an exception. Good programming includes defensive checks and input validation to prevent these.
运行时错误在程序执行期间发生，例如除以零或试图打开不存在的文件。程序可能崩溃或抛出异常。良好的编程包含防御性检查和输入验证以防止此类错误。
10. Software Maintenance | 软件维护
Software maintenance is the modification of a software product after delivery to correct faults, improve performance, or adapt to a changed environment. It is often the longest and most costly phase of the SDLC.
软件维护是在交付后对软件产品进行修改，以纠正故障、提高性能或适应变化的环境。它通常是 SDLC 中持续时间最长、成本最高的阶段。
There are three classic types of maintenance: corrective maintenance (fixing bugs and defects), adaptive maintenance (adjusting the software to work with new hardware, operating systems, or regulations), and perfective maintenance (enhancing existing features or adding new functionality to meet evolving user needs).
经典的维护类型有三种：纠正性维护（修复错误和缺陷）、适应性维护（调整软件使其适应新的硬件、操作系统或法规）和完善性维护（增强现有功能或添加新功能以满足不断变化的用户需求）。
Good documentation and modular design significantly reduce maintenance effort. If code is messy and poorly commented, even a small change might introduce new bugs—a phenomenon known as regression.
完善的文档和模块化设计可显著减少维护工作量。如果代码杂乱且注释不清，即使一个小改动也可能引入新错误——这种现象称为回归。
11. Software Documentation | 软件文档
Documentation accompanies a software system throughout its life, providing essential guidance for developers, users, and maintainers. It is often divided into internal documentation (for developers) and external documentation (for users and support staff).
文档伴随软件系统的整个生命周期，为开发人员、用户和维护人员提供必要的指导。它通常分为内部文档（面向开发人员）和外部文档（面向用户和支持人员）。
Internal documentation includes detailed comments within the source code, design documents, technical specifications, and algorithmic descriptions. It enables future developers to understand the rationale behind design decisions and to make changes safely.
内部文档包含源代码内部的详细注释、设计文档、技术规范以及算法描述。它使未来的开发人员能够理解设计决策背后的原理，并安全地进行更改。
External documentation includes user manuals, installation guides, and release notes. For the WJEC exam, you might need to explain why both types are critical: internal documentation supports maintenance, while external documentation ensures users can install and operate the software correctly.
外部文档包括用户手册、安装指南和发布说明。在 WJEC 考试中，你可能需要解释为什么这两种类型都至关重要：内部文档支持维护，而外部文档确保用户能正确安装和操作软件。
12. Ethical, Legal and Environmental Issues | 伦理、法律与环境问题
Professional software engineers are bound by ethical codes, such as respect for privacy and intellectual property. The WJEC specification expects you to discuss these responsibilities in the context of software development.
专业软件工程师受到伦理准则的约束，例如尊重隐私和知识产权。WJEC 大纲期望你在软件开发背景下讨论这些责任。
Legal considerations include compliance with the Data Protection Act 2018 (incorporating the GDPR) when handling personal data, respect for the Computer Misuse Act regarding unauthorised access, and adherence to copyright and licensing laws for both code and digital assets.
法律方面的考量包括：处理个人数据时遵守《2018 年数据保护法》（纳入 GDPR）；在未授权访问方面遵守《计算机滥用法》；以及就代码和数字资产而言遵守版权和许可法。
Environmental issues are also relevant: software can be designed to be energy-efficient, and hardware upgrades driven by demanding software contribute to e-waste. Sustainable software engineering seeks to minimise the environmental footprint over a product’s life cycle.
环境问题同样相关：软件可被设计成节能的，而由需求苛刻的软件驱动的硬件升级会加剧电子废弃物。可持续软件工程力求在整个产品生命周期内最小化环境足迹。
When answering exam questions, always connect ethical principles (honesty, fairness, public good) with specific software scenarios, such as collecting user data without consent, using weak encryption, or copying code without permission.
在回答考题时，务必把伦理原则（诚实、公平、公共利益）与具体的软件场景联系起来，例如未经同意收集用户数据、使用弱加密，或未经许可复制代码。
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课程辅导，国外大学本科硕士研究生博士课程论文辅导