📚 Software Engineering Key Points | 软件工程考点精讲
Software engineering is the systematic application of engineering approaches to the development, operation, and maintenance of software. It encompasses a broad range of activities — from initial concept and requirements gathering to design, coding, testing, deployment, and ongoing evolution. This revision guide covers the essential topics examined in IB and AQA Computer Science specifications, presenting key concepts, models, and practices in a bilingual format to support deeper understanding.
软件工程是将工程化方法系统性地应用于软件的开发、运行和维护的学科。它涵盖了从最初的概念和需求收集，到设计、编码、测试、部署以及持续演进的一系列活动。本复习指南涵盖IB和AQA计算机科学考试大纲中的核心主题，以中英双语形式呈现关键概念、模型和实践，帮助加深理解。
1. Software Development Life Cycle (SDLC) | 软件开发生命周期
The Software Development Life Cycle (SDLC) is a structured framework that defines the stages involved in the creation of software. Common phases include planning, analysis, design, implementation, testing, deployment, and maintenance. Each phase produces deliverables that feed into the next, ensuring a disciplined and manageable process.
软件开发生命周期（SDLC）是一个结构化框架，定义了软件创建过程中涉及的各个阶段。常见的阶段包括规划、分析、设计、实施、测试、部署和维护。每个阶段都会产生交付物，作为下一阶段的输入，从而确保流程有序且易于管理。
Different SDLC models exist to suit project needs — the Waterfall model follows a linear sequential flow, while iterative models allow revisiting earlier phases. In IB and AQA examinations, you are expected to compare these models and justify the choice of a particular lifecycle for a given scenario.
针对不同的项目需求，存在多种SDLC模型——瀑布模型遵循线性顺序流程，而迭代模型允许回溯早期阶段。在IB和AQA考试中，期望你能够比较这些模型，并针对给定场景论证选择特定生命周期模型的理由。
2. The Waterfall Model | 瀑布模型
The Waterfall model is the earliest and simplest SDLC approach, where phases flow sequentially downwards like a waterfall. Requirements must be fully specified before design begins, design is completed before coding, and so on. It is easy to manage and works well for projects with clear, stable requirements.
瀑布模型是最早且最简单的SDLC方法，各个阶段像瀑布一样自上而下顺序进行。需求必须在设计开始前完全确定，设计在编码前完成，依此类推。该模型易于管理，适用于需求明确且稳定的项目。
However, the Waterfall model is inflexible; late-stage changes are costly because returning to an earlier phase requires significant rework. Examiners often ask students to evaluate its suitability for safety-critical systems (where thorough upfront documentation is essential) versus dynamic environments where Agile might be preferred.
然而，瀑布模型缺乏灵活性；后期变更代价高昂，因为回到早期阶段需要大量返工。考官常要求学生评估它在安全关键系统（必须进行全面的前期文档编写）和动态环境（可能更倾向使用敏捷方法）中的适用性。
3. Agile Methodologies | 敏捷方法
Agile is an iterative, incremental approach that prioritises individuals and interactions, working software, customer collaboration, and responding to change. Teams work in short cycles called sprints (typically 2–4 weeks) to deliver potentially shippable product increments. Popular frameworks include Scrum and Kanban.
敏捷是一种迭代、增量的方法，优先考虑个体与交互、可工作的软件、客户协作以及响应变更。团队在称为冲刺的短周期（通常2–4周）内工作，交付潜在可发布的产品增量。流行的框架包括Scrum和看板。
Agile thrives in environments where requirements are likely to evolve. It mitigates risk by delivering value early and continuously incorporating feedback. In IB/AQA contexts, you should be able to contrast Agile with plan-driven models, citing benefits such as faster user feedback and drawbacks like less predictable schedules.
敏捷在需求可能不断变化的环境中表现出色。它通过尽早交付价值并持续融入反馈来降低风险。在IB/AQA的情境中，你需要能够对比敏捷与计划驱动模型，列举诸如更快的用户反馈等优点，以及诸如进度较难预测等缺点。
4. Requirements Elicitation and Analysis | 需求获取与分析
Requirements elicitation gathers the functional and non-functional needs of stakeholders through interviews, questionnaires, observation, and document analysis. The goal is to produce a clear, consistent requirements specification that serves as the foundation for design.
需求获取通过访谈、问卷调查、观察和文档分析来收集利益相关者的功能性和非功能性需求。目标是生成清晰、一致的需求规格说明，作为设计的基础。
Functional requirements describe what the system should do (e.g., ‘generate monthly sales report’), while non-functional requirements specify quality attributes (e.g., performance, security, usability). In exam answers, distinguishing between these two types and using tools like use case diagrams earns marks.
功能性需求描述系统应该做什么（例如“生成月度销售报告”），而非功能性需求规定了质量属性（例如性能、安全性、可用性）。在考试答案中，区分这两类需求并使用用例图等工具会为你赢得分数。
5. System Design Principles | 系统设计原则
System design transforms requirements into a blueprint for construction. It involves defining architecture, components, modules, interfaces, and data. Key principles include modularity (breaking a system into manageable parts), abstraction (hiding complexity), and cohesion/coupling (maximising intra-module relatedness while minimising inter-module dependency).
系统设计将需求转化为构建蓝图，涉及定义架构、组件、模块、接口和数据。关键原则包括模块化（将系统分解为可管理的部分）、抽象（隐藏复杂性）以及内聚与耦合（最大化模块内部关联性，最小化模块间依赖性）。
Designers often use UML (Unified Modeling Language) diagrams such as class diagrams, sequence diagrams, and entity-relationship diagrams to communicate structure and behaviour. Both IB and AQA papers may require interpretation or creation of such diagrams.
设计师通常使用UML（统一建模语言）图，如类图、顺序图和实体关系图，来传达结构和行为。IB和AQA试卷均可能要求解释或创建此类图示。
6. Implementation and Coding Standards | 实施与编码标准
Implementation is the phase where design documents are converted into executable code. Adhering to coding standards — rules and guidelines for writing source code — improves readability, maintainability, and team collaboration. Common standards cover naming conventions, indentation, and commenting.
实施阶段是将设计文档转化为可执行代码的阶段。遵守编码标准——编写源代码的规则和指南——可以提高可读性、可维护性和团队协作。常见的标准涵盖命名约定、缩进和注释。
Version control systems such as Git are crucial during implementation, enabling tracking of changes and collaboration. Exam questions might ask about the role of integrated development environments (IDEs) or the importance of refactoring to keep code clean and efficient.
版本控制系统如Git在实施过程中至关重要，可以追踪变更并促进协作。考题可能询问集成开发环境（IDE）的作用，或重构对于保持代码简洁高效的重要性。
7. Software Testing Strategies | 软件测试策略
Testing verifies that the software meets specified requirements and identifies defects. Strategies range from unit testing (individual components) to integration testing (combined modules), system testing (entire system), and acceptance testing (user validation). Automation is frequently used for regression testing.
测试用于验证软件是否满足规定需求并识别缺陷。策略包括单元测试（单独组件）、集成测试（组合模块）、系统测试（整个系统）和验收测试（用户验证）。自动化常用于回归测试。
Test data should include normal, boundary, and erroneous (invalid) values. In trace tables and pseudocode walkthroughs, students are expected to demonstrate how testing reveals logic errors. Black-box testing (based on inputs/outputs) and white-box testing (based on internal logic) are also examined.
测试数据应包括正常值、边界值和错误（无效）值。在迹表和伪代码走查中，期望学生展示测试如何揭示逻辑错误。黑盒测试（基于输入/输出）和白盒测试（基于内部逻辑）也是考查内容。
8. Deployment and Maintenance | 部署与维护
Deployment involves releasing the software to users, which can be done via direct installation, phased rollout, or parallel running alongside the old system. Post-deployment, the system enters the maintenance phase, which corrects defects (corrective), adapts to new environments (adaptive), enhances functionality (perfective), or prevents future issues (preventive).
部署涉及将软件发布给用户，可以通过直接安装、分阶段推出或与旧系统并行运行来完成。部署后，系统进入维护阶段，该阶段包括纠正缺陷（纠正性）、适应新环境（适应性）、增强功能（完善性）或预防未来问题（预防性）。
Maintenance typically consumes the largest proportion of total lifecycle costs. Students should be able to explain how good design and documentation reduce maintenance effort, and they may be given scenario-based questions on selecting an appropriate deployment strategy.
维护通常占整个生命周期成本的最大比例。学生应能解释良好的设计和文档如何减少维护工作量，并可能遇到基于场景的选择适当部署策略的题目。
9. Software Documentation | 软件文档
Documentation accompanies a software system throughout its lifecycle. Internal documentation includes comments within the source code and technical documents for developers. External documentation comprises user manuals, installation guides, and API references for end-users or integrators.
文档伴随软件系统贯穿整个生命周期。内部文档包括源代码中的注释和面向开发人员的技术文档。外部文档则包括用户手册、安装指南和提供给最终用户或集成人员的API参考。
High-quality documentation is critical for maintenance and knowledge transfer. In IB’s internal assessment and AQA’s non-exam assessments, candidates must produce clear documentation for their programmed solutions, demonstrating an understanding of audience and purpose.
高质量的文档对于维护和知识转移至关重要。在IB内部评估和AQA非考试评估中，考生必须为其编程解决方案提供清晰的文档，展示对受众和目的的理解。
10. Ethical, Legal, and Social Considerations | 伦理、法律与社会考量
Software engineers must navigate intellectual property rights, data protection laws (such as GDPR), and professional ethics. Issues like software piracy, algorithmic bias, privacy invasions, and the digital divide require careful consideration during development.
软件工程师必须应对知识产权、数据保护法（如GDPR）以及职业道德等问题。软件盗版、算法偏见、侵犯隐私和数字鸿沟等问题在开发过程中需要仔细考虑。
Computer science syllabi increasingly emphasise the social impact of technology. Essays and case-study questions may probe the balance between innovation and regulation, or the responsibility of developers when designing systems that affect public life.
计算机科学教学大纲越来越强调技术的社会影响。论文和案例研究类题目可能探讨创新与监管之间的平衡，或开发人员在设计影响公共生活的系统时的责任。
11. Prototyping and Rapid Application Development (RAD) | 原型与快速应用开发
Prototyping involves building a scaled-down working version of a system to clarify requirements and gather early user feedback. Throwaway prototypes are discarded after eliciting needs, while evolutionary prototypes are refined incrementally into the final product.
原型设计涉及构建系统的缩小版工作版本，以澄清需求并收集早期用户反馈。抛弃型原型在获取需求后被丢弃，而演化型原型则逐步完善为最终产品。
RAD combines prototyping with joint application design workshops and strict timeboxing. It accelerates development through reusable components and user involvement. In the exam, linking RAD to scenarios where time-to-market is critical and requirements are not fully known in advance demonstrates evaluative skill.
快速应用开发将原型设计与联合应用设计研讨会和严格的时间限制相结合。它通过可重用组件和用户参与来加速开发。在考试中，将RAD与对上市时间要求高且需求尚未完全明确的场景联系起来，能展示出评估技能。
12. Computer-Aided Software Engineering (CASE) Tools | 计算机辅助软件工程工具
CASE tools automate activities across the SDLC, including diagram creation, code generation, version control, and testing. Upper CASE supports analysis and design, while lower CASE aids implementation and maintenance. Examples include UML tools, integrated development environments (IDEs), and configuration management suites.
CASE工具可自动执行SDLC中的各类活动，包括图表创建、代码生成、版本控制和测试。上层CASE支持分析和设计，下层CASE辅助实施和维护。示例包括UML工具、集成开发环境（IDE）和配置管理套件。
Understanding the advantages, such as consistency and productivity gains, and disadvantages, such as initial cost and vendor lock-in, enables students to make informed recommendations. IB and AQA mark schemes reward the ability to relate tool use to specific project contexts.
理解其优势（如一致性和生产率提升）和劣势（如初始成本和供应商锁定），使学生能够提出有依据的建议。IB和AQA的评分方案奖励将工具使用与具体项目背景相联系的能力。
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课程辅导，国外大学本科硕士研究生博士课程论文辅导