📚 Software Engineering Key Points for IB WJEC Computer Science | IB WJEC 计算机：软件工程 考点精讲
Software engineering is a disciplined approach to the design, development, and maintenance of software systems. For IB and WJEC Computer Science students, understanding the software lifecycle, development models, testing strategies, and project management is essential. This revision guide breaks down the core concepts, equipping you with both theoretical knowledge and practical insight to excel in your exams.
软件工程是设计、开发和维护软件系统的规范方法。对于 IB 和 WJEC 计算机科学考生而言，理解软件生命周期、开发模型、测试策略和项目管理至关重要。本考点精讲将逐一拆解这些核心概念，帮助你掌握理论知识，并提升应试所需的实践洞见。
1. What is Software Engineering? | 什么是软件工程？
Software engineering is the systematic application of engineering principles to the creation of software. It goes beyond mere programming by incorporating structured analysis, design, documentation, testing, and maintenance. The goal is to produce reliable, efficient, and scalable software that meets user requirements within budget and time constraints.
软件工程是将工程化原则系统性地应用于软件创作的过程。它超越了单纯的编程，融合了结构化分析、设计、文档、测试与维护。其目标在于生产可靠、高效且可扩展的软件，在预算和时间约束内满足用户需求。
The key difference between a program and a software product is that software is designed for a broader audience, accompanied by documentation, and must be maintained over a long period. Software engineering addresses the ‘software crisis’ where projects often run over time, exceed budget, or fail to deliver quality.
程序与软件产品的关键区别在于，软件面向更广泛的用户，附有文档，并需长期维护。软件工程要应对“软件危机”——项目时常超期、超预算或质量不达标。
- Attributes of good software: Maintainability, dependability, efficiency, usability, and portability.
- 优质软件的特性：可维护性、可靠性、效率、易用性和可移植性。
- Software process: A structured set of activities required to develop a software system, typically including specification, development, validation, and evolution.
- 软件过程：开发软件系统所需的一组结构化活动，通常包括规格说明、开发、验证和演进。
2. Software Development Life Cycle (SDLC) | 软件开发生命周期
The SDLC provides a framework for planning and controlling the creation of an information system. It consists of several distinct phases: feasibility study, requirements analysis, design, implementation, testing, deployment, and maintenance. Each phase produces deliverables that feed into the next stage, ensuring a systematic progression.
软件开发生命周期（SDLC）为信息系统的创建提供了规划与控制框架。它包括几个明确阶段：可行性研究、需求分析、设计、实现、测试、部署和维护。每一阶段产出的交付物会进入下一阶段，确保系统化推进。
Understanding SDLC models is crucial because the choice of model impacts project risk, customer involvement, and adaptability to change. The main models include the Waterfall, V-Model, Iterative, Spiral, and Agile families. IB and WJEC exam papers frequently ask to compare these models, highlighting their advantages and disadvantages.
理解 SDLC 模型至关重要，因为模型的选择会影响项目风险、客户参与度以及对变更的适应性。主要模型包括瀑布模型、V 模型、迭代模型、螺旋模型与敏捷系列。IB 和 WJEC 考试经常要求比较这些模型，突出其优缺点。
| Phase (阶段) | Key Activities (关键活动) |
|---|---|
| Feasibility (可行性) | Assess technical, economic, legal, and operational viability. |
| Requirements (需求) | Gather functional and non-functional requirements from stakeholders. |
| Design (设计) | Architectural design, interface design, database design. |
| Implementation (实现) | Coding, unit testing, integration. |
| Testing (测试) | System testing, acceptance testing, debugging. |
| Maintenance (维护) | Corrective, adaptive, perfective, and preventive maintenance. |
3. Waterfall Model | 瀑布模型
The Waterfall model is a linear sequential approach where each phase must be completed before the next begins. It is easy to understand and manage due to its rigid structure and well-defined milestones. Documentation is produced at each stage, making it suitable for projects with stable, clearly understood requirements.
瀑布模型是一种线性顺序方法，每一阶段必须完成后才能进入下一阶段。它结构固定、里程碑明确，易于理解和管理。每个阶段均产出文档，因此适合需求稳定且清晰的项目。
However, the Waterfall model is inflexible. Once a phase is completed, it is difficult and costly to go back and make changes. It does not accommodate evolving user needs well, and real working software is not seen until late in the cycle. Typical applications include large government or safety-critical systems where requirements are heavily regulated and change is minimal.
然而，瀑布模型缺乏灵活性。一旦某个阶段完成，回退修改困难且成本高昂。它难以适应不断演变的用户需求，并且直到后期才能看到实际可工作的软件。典型应用包括大型政府项目或安全关键系统，这类项目需求受到严格管控且变更极少。
- Advantages: Simple, milestones clear, good for fixed requirements.
- 优点：简单，里程碑清晰，适合需求固定的项目。
- Disadvantages: Rigid, no early feedback, high risk of change.
- 缺点：僵化，没有早期反馈，变更风险高。
4. Agile Methodologies | 敏捷方法
Agile software development focuses on iterative progress, collaboration, and responding to change. Instead of a single long development cycle, projects are divided into small increments called sprints (typically 1-4 weeks). Each sprint delivers a potentially shippable product increment, allowing stakeholders to provide continuous feedback.
敏捷软件开发注重迭代进展、协作与响应变化。项目被分为名为冲刺（通常1–4周）的小增量，而非单一的长期开发周期。每个冲刺交付一个潜在可发布的产品增量，让利益相关者能够持续提供反馈。
Popular frameworks include Scrum and Kanban. Scrum defines roles (Product Owner, Scrum Master, Development Team), artifacts (Product Backlog, Sprint Backlog), and ceremonies (Daily Stand-up, Sprint Review). Kanban visualizes workflow on a board to identify bottlenecks and limit work-in-progress. IB/WJEC syllabi often expect knowledge of the Agile Manifesto’s four values: individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, responding to change over following a plan.
流行框架包括 Scrum 和看板（Kanban）。Scrum 定义了角色（产品负责人、Scrum Master、开发团队）、工件（产品待办列表、冲刺待办列表）与仪式（每日站会、冲刺评审）。看板则在板上可视化工作流，以识别瓶颈并限制在制品。IB/WJEC 课程大纲通常要求掌握敏捷宣言的四个价值观：个体与互动高于流程与工具；可工作软件高于详尽的文档；客户合作高于合同谈判；响应变化高于遵循计划。
5. Requirements Engineering | 需求工程
Requirements engineering is the process of establishing the services a system should provide and the constraints under which it operates. It involves elicitation, analysis, specification, validation, and management. High-quality requirements are the foundation of successful software; errors here propagate and become increasingly expensive to fix.
需求工程是确定系统应提供的服务及其运行约束的过程，包括需求获取、分析、规格说明、验证和管理。高质量的需求是成功软件的基础；此处的错误会扩散，并使得修复成本成倍增加。
Requirements are classified into functional (what the system does, e.g., ‘calculate interest’) and non-functional (how the system performs, e.g., response time, security). Fact-finding techniques include interviews, questionnaires, observation, and document analysis. A key document is the Software Requirements Specification (SRS), which should be unambiguous, complete, and verifiable.
需求分为功能性需求（系统做什么，例如“计算利息”）和非功能性需求（系统表现如何，例如响应时间、安全性）。事实调查技术包括访谈、问卷、观察和文档分析。一份关键文档是软件需求规格说明书（SRS），它应清晰、完整且可验证。
- Functional: User login, generate report, process payment.
- 功能性需求：用户登录、生成报告、处理付款。
- Non-functional: Response ≤ 2 seconds, 99.9% uptime, compliance with GDPR.
- 非功能性需求：响应时间 ≤ 2 秒，99.9% 正常运行时间，符合 GDPR。
6. System Design Principles | 系统设计原则
Design transforms requirements into a blueprint for building the software. It covers architectural design (high-level structure), component-level design, interface design, and database design. Good design reduces complexity, facilitates reuse, and makes the system easier to code, test, and maintain.
设计将需求转化为构建软件的蓝图，涵盖架构设计（高层次结构）、组件级设计、接口设计和数据库设计。良好的设计可以降低复杂度、促进复用，并使系统更易于编码、测试和维护。
Key principles include abstraction (hiding complex details behind simple interfaces), modularity (dividing a system into separate, manageable modules), cohesion (elements within a module should be closely related), and coupling (minimizing dependencies between modules). Design patterns like Model-View-Controller (MVC) help structure interactive applications. UML (Unified Modeling Language) diagrams such as class diagrams, sequence diagrams, and use case diagrams are standard tools for visualising design.
关键原则包括抽象（在简单接口后隐藏复杂细节）、模块化（将系统划分为独立、可管理的模块）、内聚（模块内元素应紧密相关）和耦合（最小化模块间的依赖）。设计模式如模型-视图-控制器（MVC）有助于构建交互式应用。UML（统一建模语言）图，如类图、顺序图和用例图，是可视化设计的标准工具。
7. Implementation and Coding Standards | 实现与编码标准
Implementation is the phase where design is translated into executable code. It involves selecting appropriate programming languages, development environments, and following coding standards. Consistent naming conventions, indentation, and commenting improve code readability and maintainability, which is particularly vital for large teams.
实现阶段将设计转化为可执行代码，涉及选择合适的编程语言、开发环境并遵循编码规范。一致的命名约定、缩进和注释能提升代码可读性与可维护性，这对大型团队尤为重要。
Version control systems (e.g., Git) are used to track changes and enable collaboration. Code reviews and pair programming are common practices to catch defects early. The concept of technical debt—the implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer—is an important consideration in professional software projects.
版本控制系统（如 Git）用于跟踪变更并支持协作。代码评审与结对编程是及早发现缺陷的常见实践。“技术债务”概念（因当下选择捷径而非更优但耗时方案而引发的额外返工成本）是专业软件项目中的重要考量。
8. Software Testing Strategies | 软件测试策略
Testing is the process of executing a program with the intent of finding errors. It is a crucial part of quality assurance and can be performed at multiple levels: unit testing (individual modules), integration testing (interaction between modules), system testing (the complete, integrated system), and acceptance testing (customer validation).
测试是以发现错误为目的而执行程序的过程。它是质量保证的关键部分，可在多层次上进行：单元测试（针对单个模块）、集成测试（模块间交互）、系统测试（完整的集成系统）和验收测试（客户验证）。
IBM’s black-box and white-box testing techniques are widely referenced. Black-box testing focuses on inputs and outputs without knowledge of internal structure; techniques include equivalence partitioning and boundary value analysis. White-box testing uses knowledge of the code to design test cases that cover specific paths, branches, and statements. Test-driven development (TDD) is an Agile practice where tests are written before the code.
黑盒与白盒测试技术被广泛引用。黑盒测试关注输入输出，不关注内部结构；常用技术包括等价类划分和边界值分析。白盒测试利用对代码的了解，设计覆盖特定路径、分支和语句的测试用例。测试驱动开发（TDD）是一种敏捷实践，要求在编写代码之前先写测试。
Cyclomatic complexity = E – N + 2P (for structured graphs)
圈复杂度 = E – N + 2P（针对结构化图）
where E = edges, N = nodes, P = connected components. A higher cyclomatic complexity indicates a more complex program logic and requires more testing effort.
其中 E = 边数，N = 节点数，P = 连通分量数。圈复杂度越高，表明程序逻辑越复杂，需要更多的测试投入。
9. Maintenance and Evolution | 维护与演进
After deployment, software enters the maintenance phase, which can account for over 50% of total lifecycle costs. There are four types: corrective (fixing bugs), adaptive (modifying to work in a new environment), perfective (improving performance or maintainability), and preventive (reducing future risk).
部署后，软件进入维护阶段，该阶段可能占总生命周期成本的50%以上。维护分为四类：纠正性维护（修复缺陷）、适应性维护（为适应新环境而修改）、完善性维护（提升性能或可维护性）和预防性维护（降低未来风险）。
Legacy systems often pose challenges because documentation may be outdated, original developers may be unavailable, and the system uses obsolete technology. Re-engineering and refactoring are techniques to improve the internal structure without changing external behavior. The goal is to keep the system useful and cost-effective for as long as possible.
遗留系统常带来挑战，因为文档可能过时，原始开发人员可能联系不上，且系统使用过时技术。再工程和重构是改善内部结构而不改变外部行为的技术。目标是尽可能长时间地保持系统的有用性和成本效益。
10. Project Management and Tools | 项目管理与工具
Software project management ensures that projects are delivered on time, within budget, and to the required quality. It involves planning, scheduling, risk management, and resource allocation. Gantt charts and PERT (Program Evaluation and Review Technique) charts are common visual tools for scheduling and tracking progress.
软件项目管理确保项目按时、在预算内并以所需质量交付，涉及规划、调度、风险管理和资源分配。甘特图和 PERT（项目评审技术）图是常见的进度安排与跟踪可视化工具。
The critical path method identifies the longest sequence of dependent tasks that determines the minimum project duration. Any delay on the critical path directly impacts the project completion date. Risk management involves identifying potential risks (e.g., staff turnover, technology change) and preparing mitigation strategies.
关键路径法可识别决定最短项目周期的依赖任务最长序列。关键路径上的任何延误都会直接影响项目完成日期。风险管理包括识别潜在风险（如人员流失、技术变更）并制定缓解策略。
Critical Path Duration = Sum of durations on the longest path
关键路径持续时间 = 最长路径上各持续时间之和
11. Ethical and Legal Considerations | 伦理与法律考量
Software engineers must adhere to professional codes of conduct, such as the ACM/IEEE Software Engineering Code of Ethics. This includes principles like acting in the public interest, maintaining integrity, and ensuring that software does no harm. Privacy, data protection, and intellectual property are particularly relevant.
软件工程师必须遵守专业行为准则，如 ACM/IEEE 软件工程伦理规范，包括维护公共利益、保持诚信、确保软件不造成伤害等原则。隐私、数据保护和知识产权尤其相关。
Legal frameworks such as GDPR (General Data Protection Regulation) in Europe require software to handle personal data responsibly. Licensing models (open source vs proprietary) and copyright issues also form part of the syllabus. IB and WJEC often integrate ethical scenarios into exam questions, asking students to evaluate the impact of software decisions on stakeholders.
法律框架如欧洲的 GDPR（通用数据保护条例）要求软件负责任地处理个人数据。许可模式（开源与专有）和版权问题也是课程的一部分。IB 和 WJEC 考试常将伦理场景融入试题，要求学生评估软件决策对利益相关者的影响。
12. Exam Tips for IB/WJEC | IB/WJEC 考试技巧
When answering software engineering questions, always link theory to practical examples. For comparison questions (e.g., Waterfall vs Agile), present a balanced view with pros and cons before drawing a context-dependent conclusion. Diagrams such as the SDLC cycle, Gantt charts, and use case diagrams can earn marks if clearly labelled and explained.
在回答软件工程问题时，务必将理论与实际案例相联系。对于比较类题目（如瀑布与敏捷），要呈现平衡的观点，列出优缺点，再给出取决于具体情境的结论。SDLC 循环、甘特图和用例图等图表若能清晰标注并加以解释，将可获得加分。
Common pitfalls include confusing verification with validation, ignoring the maintenance phase, and describing tools without explaining their purpose. Pay attention to command terms: ‘describe’ requires a detailed account; ‘compare’ needs both similarities and differences; ‘evaluate’ demands a judgement supported by evidence. Practice past papers under timed conditions to refine your application of knowledge.
常见误区包括混淆验证与确认、忽视维护阶段、描述工具却不解释其用途。注意指令词：“描述”要求详细叙述；“比较”需涉及相同点和不同点；“评估”则需给出有证据支持的判断。在限时条件下练习历年试卷，以提升知识运用能力。
- Verification: ‘Are we building the product right?’ (internal correctness).
- 验证：“我们是否正确构建了产品？”（内部正确性）。
- Validation: ‘Are we building the right product?’ (meets user needs).
- 确认：“我们是否构建了正确的产品？”（满足用户需求）。
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