📚 Software Engineering Key Concepts for AQA IGCSE Computer Science | IGCSE AQA 计算机：软件工程 考点精讲
Software engineering is the disciplined application of engineering principles to the design, development, testing, and maintenance of software systems. For the AQA IGCSE Computer Science specification, you need to understand the key stages of the software development life cycle, different programming paradigms, testing strategies, and the importance of documentation and version control. This article breaks down the core concepts in a bilingual format to help you master every essential point.
软件工程是将工程原理规范地应用于软件系统的设计、开发、测试和维护的学科。针对 AQA IGCSE 计算机科学大纲，你需要理解软件开发生命周期的关键阶段、不同的编程范式、测试策略，以及文档和版本控制的重要性。本文以中英双语形式拆解核心概念，帮助大家掌握每一个必考点。
1. The Software Development Life Cycle (SDLC) | 软件开发生命周期
The Software Development Life Cycle is a structured process used to plan, create, test, and deploy information systems. AQA recognises several models, but the two most prominent are the waterfall model and iterative/incremental models. Each model breaks down the project into phases, though they approach these phases differently.
软件开发生命周期是用于规划、创建、测试和部署信息系统的结构化过程。AQA 认可多种模型，但最突出的是瀑布模型和迭代/增量模型。每种模型都将项目分解为若干阶段，只是处理这些阶段的方式不同。
The waterfall model follows a linear, sequential flow. Each phase must be completed before the next begins, making it easy to manage but inflexible to changes. Typical phases are requirements analysis, design, implementation, testing, deployment, and maintenance.
瀑布模型遵循线性顺序流程。每个阶段必须在下一个阶段开始前完成，因此易于管理但不易应对变化。典型阶段包括需求分析、设计、实现、测试、部署和维护。
Iterative and incremental models, such as the spiral model, develop software through repeated cycles (iterations). A working version of the software is produced early and refined over time. This allows for user feedback and changing requirements, reducing risk but requiring more active management.
迭代和增量模型（如螺旋模型）通过重复的循环（迭代）来开发软件。早期即生成可运行版本，并随时间不断完善。这种方式允许用户反馈和需求变更，降低了风险，但需要更积极的管理。
2. Requirements Analysis and Specification | 需求分析与规格说明
Requirements analysis is the first and most critical phase in any SDLC. It involves gathering, analysing, and documenting what the software must do from the user’s perspective. Failure here leads to expensive rework later.
需求分析是所有软件开发生命周期中第一个也是最关键的阶段。它涉及从用户角度收集、分析和记录软件必须做什么。此阶段失败会导致后期昂贵的返工。
A requirements specification document is produced, describing functional requirements (what the system does, like calculate tax) and non-functional requirements (how the system performs, like security, reliability, and speed). It must be clear, unambiguous, and agreed upon by stakeholders.
生成的需求规格说明文档描述了功能需求（系统做什么，如计算税款）和非功能需求（系统如何表现，如安全性、可靠性和速度）。它必须清晰、无歧义，并得到利益相关者的一致同意。
Techniques for gathering requirements include interviews, questionnaires, observation of existing systems, and document analysis. In AQA exams, you may need to suggest appropriate methods for a given scenario.
收集需求的技术包括访谈、问卷调查、观察现有系统和分析文档。在 AQA 考试中，你可能需要针对给定情境建议合适的方法。
3. System Design and Modelling | 系统设计与建模
System design translates requirements into a blueprint for building the software. It covers both high-level architecture and detailed component design. Key design tools include structure diagrams, flowcharts, and pseudocode, all of which appear frequently in the AQA syllabus.
系统设计将需求转化为构建软件的蓝图。它涵盖高层架构和详细的组件设计。关键设计工具包括结构图、流程图和伪代码，这些都在 AQA 大纲中频繁出现。
Structure diagrams (hierarchy charts) show the breakdown of a system into sub-systems and modules. They illustrate the top-down modular approach, which is fundamental to structured programming. Each box represents a module, and lines show the calling hierarchy.
结构图（层次图）展示系统如何分解为子系统和模块。它们体现了自顶向下的模块化方法，这是结构化编程的基础。每个方框代表一个模块，连线表示调用层次。
Flowcharts use standard symbols (ovals for start/end, parallelograms for input/output, rectangles for processes, diamonds for decisions) to represent algorithms. Pseudocode is a textual, near-English description of an algorithm that follows structured conventions. For AQA, you must be able to read, interpret, and write both.
流程图使用标准符号（椭圆表示开始/结束，平行四边形表示输入/输出，矩形表示处理，菱形表示决策）来表示算法。伪代码是一种遵循结构化约定的类英语算法文本描述。在 AQA 考试中，你必须能够阅读、解释和编写这两者。
4. Structured vs Object-Oriented Programming | 结构化与面向对象编程
AQA expects you to understand two fundamental programming paradigms: structured programming and object-oriented programming (OOP). Structured programming focuses on sequences, selections, and iterations, breaking problems into subroutines or functions.
AQA 希望你理解两种基本编程范式：结构化编程和面向对象编程（OOP）。结构化编程侧重于顺序、选择和循环，将问题分解为子程序或函数。
Structured programs use local and global variables, and data is separate from procedures. It promotes readability and testing but can become difficult to manage for very large systems.
结构化程序使用局部和全局变量，并且数据与过程是分离的。它提高了可读性和可测试性，但对于非常大型的系统可能变得难以管理。
Object-oriented programming organises code around objects, which are instances of classes. A class groups attributes (data) and methods (procedures) together. Key OOP concepts are encapsulation (hiding internal data), inheritance (creating new classes from existing ones), and polymorphism (methods behaving differently depending on the object). OOP improves reuse and maintainability.
面向对象编程围绕对象（类的实例）组织代码。类将属性（数据）和方法（过程）组合在一起。关键的 OOP 概念包括封装（隐藏内部数据）、继承（从现有类创建新类）和多态（方法根据对象而表现不同）。OOP 提高了重用性和可维护性。
5. Implementation and Coding Best Practices | 实现与编码最佳实践
Implementation is the phase where design is converted into actual code. AQA assesses your ability to write code in a high-level language (often Python, VB.NET, or C# at centres). Best practices include meaningful variable naming, indentation, and commenting to enhance readability.
实现是将设计转换为实际代码的阶段。AQA 会评估你用高级语言（通常是 Python、VB.NET 或 C#）编写代码的能力。最佳实践包括有意义的变量命名、缩进和添加注释以增强可读性。
You must use constants for fixed values, employ local variables where possible to reduce side effects, and avoid global variables unless necessary. The use of subroutines (procedures and functions) is essential to avoid repeated code.
你必须使用常量表示固定值，尽可能使用局部变量以减少副作用，除非必要否则避免全局变量。使用子程序（过程和函数）对于避免重复代码至关重要。
Data validation and sanitisation should be built in at this stage. For example, checking that an input falls within a valid range before processing. Defensive programming techniques, such as input validation loops, prevent runtime errors.
在此阶段应内置数据验证和清理。例如，在处理前检查输入是否在有效范围内。防范性编程技术（如输入验证循环）可防止运行时错误。
6. Testing: Types, Test Data, and Strategies | 测试：类型、测试数据与策略
Testing aims to find errors and ensure the software meets its requirements. AQA distinguishes between black-box testing (testing functionality without looking at the code) and white-box testing (testing internal paths and logic). Both are needed for robust verification.
测试旨在发现错误并确保软件满足需求。AQA 区分了黑盒测试（不查看代码而测试功能）和白盒测试（测试内部路径和逻辑）。两者对于稳健的验证都是必需的。
Test data should cover normal (valid typical values), boundary (values at the edges of acceptance, like minimum and maximum), and erroneous/invalid data. A good test plan includes a unique ID, description, input, expected outcome, actual outcome, and pass/fail status.
测试数据应覆盖正常（有效的典型值）、边界（可接受范围边缘的值，如最小值和最大值）和错误/无效数据。一份好的测试计划包含唯一标识、描述、输入、预期结果、实际结果以及通过/失败状态。
Testing levels include unit testing (individual modules), integration testing (combined modules), system testing (whole system against requirements), and acceptance testing (by the end user). Iterative testing is integrated into agile methodologies.
测试级别包括单元测试（单个模块）、集成测试（组合模块）、系统测试（针对需求的整个系统）和验收测试（由最终用户进行）。敏捷方法中集成了迭代测试。
7. Debugging and Error Types | 调试与错误类型
Debugging is the process of locating and fixing errors (bugs) in code. You must be able to categorise errors as syntax errors (grammar mistakes detected by the compiler/interpreter), runtime errors (occur during execution, like division by zero), and logical errors (program runs but produces wrong results).
调试是定位和修复代码中错误（bug）的过程。你必须能够将错误分类为语法错误（编译器/解释器检测到的语法错误）、运行时错误（执行期间发生，如除以零）和逻辑错误（程序运行但产生错误结果）。
Tools such as breakpoints, watch windows, and stepping through code help isolate logical errors. A trace table is a manual method where you track variable values line by line to identify where logic goes wrong. AQA may ask you to complete a trace table for a given algorithm.
断点、监视窗口和单步执行代码等工具有助于隔离逻辑错误。跟踪表是一种手动方法，你逐行跟踪变量值以确定逻辑出错的位置。AQA 可能会要求你为给定算法填写跟踪表。
8. Types of Maintenance | 维护的类型
Once software is deployed, it enters the maintenance phase, which often accounts for the majority of total cost. AQA identifies three main types: corrective maintenance (fixing bugs discovered after release), adaptive maintenance (modifying software to work with new hardware, OS, or regulations), and perfective maintenance (improving performance or adding new features in response to user requests).
软件部署后就进入了维护阶段，这通常占总成本的大部分。AQA 确定了三种主要类型：纠正性维护（修复发布后发现的错误）、适应性维护（修改软件以适应新的硬件、操作系统或法规）和完善性维护（根据用户要求改进性能或添加新功能）。
Perfective maintenance is not about fixing flaws but about enhancing an already functional system. A school’s registration system being updated to send SMS alerts is an example of perfective maintenance. Good documentation is critical to enable efficient maintenance.
完善性维护不是为了修复缺陷，而是增强已经可运行的系统。学校注册系统升级以发送短信提醒便是一个完善性维护的例子。良好的文档对于实现高效维护至关重要。
9. Documentation: User and Technical | 文档：用户文档和技术文档
Comprehensive documentation is produced throughout the SDLC. AQA expects you to differentiate between user documentation and technical documentation. User documentation helps the end user operate the software; technical documentation helps developers and maintainers understand the internal design and code.
全面的文档在整个软件开发生命周期中生成。AQA 希望你能区分用户文档和技术文档。用户文档帮助最终用户操作软件；技术文档帮助开发人员和维护人员理解内部设计和代码。
User documentation includes an installation guide, a user manual (with screenshots and step-by-step instructions), a troubleshooting section, and FAQs. It must be written in plain, non-technical language appropriate for the audience.
用户文档包括安装指南、用户手册（带有截图和分步说明）、故障排除部分和常见问题解答。它必须用适合受众的通俗、非技术性语言编写。
Technical documentation includes the requirements specification, design diagrams (flowcharts, structure charts, class diagrams), annotated source code, test plans, and data dictionaries. It serves as a reference for future updates and corrective maintenance.
技术文档包括需求规格说明、设计图（流程图、结构图、类图）、带注释的源代码、测试计划以及数据字典。它可作为未来更新和纠正性维护的参考。
10. Version Control and Collaboration | 版本控制与协作
Version control systems track changes to source code over time. They are essential in team environments to manage contributions from multiple developers. AQA mentions the benefits: you can revert to previous versions, see who made which change, and work on different features in parallel using branches.
版本控制系统追踪源代码随时间的变化。它们在团队环境中对于管理多个开发人员的贡献至关重要。AQA 提到了其优点：你可以回滚到以前的版本，查看谁做了哪些更改，并使用分支并行处理不同功能。
Basic operations include commit (save changes with a message), merge (combine branches), and rollback. While you don’t need to know commands in detail, you should understand concepts like repository, working copy, and conflict resolution. A centralised system uses a single server; distributed systems like Git give every developer a full copy.
基本操作包括提交（通过消息保存更改）、合并（组合分支）和回滚。虽然你不需要详细掌握命令，但应理解仓库、工作副本和冲突解决等概念。集中式系统使用单一服务器；像 Git 这样的分布式系统给每个开发者完整的副本。
11. Systems Development Methodologies in Practice | 实践中的系统开发方法论
Different projects suit different SDLC models. The waterfall model suits projects with stable, well-understood requirements and low risk of change, such as a payroll system with fixed tax legislation. The iterative model suits projects where requirements may evolve, like a new mobile app with user feedback driving features.
不同项目适合不同的软件开发生命周期模型。瀑布模型适合需求稳定、明了且变更风险低的项目，例如具有固定税收法规的工资系统。迭代模型适合需求可能演进的项目，如用户反馈推动功能的新移动应用。
Rapid Application Development (RAD) is another iterative approach that emphasises prototyping and quick user feedback. Prototypes can be throwaway (used to clarify requirements and then discarded) or evolutionary (refined into the final product). AQA may ask you to select and justify a methodology for a given scenario.
快速应用开发（RAD）是另一种迭代方法，强调原型设计和快速用户反馈。原型可以是抛弃型（用于澄清需求然后丢弃）或演化型（逐步完善成为最终产品）。AQA 可能会让你为给定情境选择并论证某一种方法。
12. Ethical, Legal, and Environmental Considerations | 伦理、法律与环境考量
Software engineering projects must comply with legal frameworks such as the Data Protection Act, Computer Misuse Act, and Copyright, Designs and Patents Act. For AQA, you must link these to scenarios—for example, ensuring a system encrypts personal data or does not facilitate unauthorised access.
软件工程项目必须遵守《数据保护法》、《计算机滥用法》和《版权、设计与专利法》等法律框架。对于 AQA，你必须将这些与情境联系起来——例如，确保系统加密个人数据或不助长未经授权的访问。
Ethical considerations include digital inclusion (designing for users with disabilities), the digital divide, and the impact of software on employment and society. Environmental concerns relate to energy consumption of data centres and e-waste. Sustainable software engineering promotes efficient algorithms and hardware reuse.
伦理考量包括数字包容性（为残障用户设计）、数字鸿沟以及软件对就业和社会的影响。环境问题涉及数据中心的能源消耗和电子废弃物。可持续软件工程提倡高效算法和硬件重用。
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课程辅导，国外大学本科硕士研究生博士课程论文辅导