📚 Software Engineering Key Concepts | 软件工程考点精讲
Software engineering is a disciplined approach to the design, development, operation, and maintenance of software systems. For IB and CIE Computer Science students, understanding the key principles, methodologies, and lifecycle models is essential. This revision guide covers the most important topics, from process models and requirements engineering to testing, maintenance, and project management, providing a clear and structured review to help you master the syllabus.
软件工程是一种对软件系统进行设计、开发、运行和维护的规范化方法。对于 IB 和 CIE 计算机科学的学生来说，理解关键原则、方法论和生命周期模型至关重要。本考点精讲涵盖最重要的主题，从过程模型和需求工程到测试、维护和项目管理，提供清晰、结构化的复习，帮助你掌握教学大纲。
1. Software Engineering Fundamentals | 软件工程基础
Software engineering is the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software. It aims to produce high-quality software that meets user needs within budget and time constraints.
软件工程是将系统化、规范化、可量化的方法应用于软件的开发、运行和维护。其目标是在预算和时间限制内生产出满足用户需求的高质量软件。
Key objectives include maintainability, reliability, efficiency, and usability. Unlike simple programming, software engineering addresses complexity through abstraction, modularity, and the use of standardised processes.
主要目标包括可维护性、可靠性、效率和可用性。与简单的编程不同，软件工程通过抽象化、模块化和使用标准化过程来解决复杂性问题。
The software crisis of the 1960s highlighted the need for engineering principles: projects were often late, over budget, and delivered unreliable code. This led to the emergence of formal methodologies and the concept of the software development lifecycle.
20 世纪 60 年代的软件危机凸显了对工程原则的需求：项目经常延期、超预算，交付的代码也不可靠。这促使了正式方法论和软件开发生命周期概念的出现。
2. Software Development Lifecycle (SDLC) | 软件开发生命周期
The SDLC is a framework that defines the stages involved in creating software. The typical phases are: feasibility study, requirements analysis, design, implementation (coding), testing, deployment, and maintenance. Each phase produces deliverables that feed into the next stage.
软件开发生命周期是一个定义软件创建过程的框架。典型的阶段包括：可行性研究、需求分析、设计、实现（编码）、测试、部署和维护。每个阶段产生的交付物会输入到下一个阶段。
Different models organise these phases in various ways. The choice of model depends on project characteristics, such as clarity of requirements, schedule constraints, and risk factors. Students must be able to compare and contrast the main lifecycle models.
不同的模型以不同方式组织这些阶段。模型的选择取决于项目特征，例如需求的清晰度、进度限制和风险因素。学生必须能够比较和对比主要的生命周期模型。
3. Waterfall Model | 瀑布模型
The waterfall model is a linear sequential approach where each phase must be completed before the next begins. Phases flow downwards like a waterfall: requirements → design → implementation → testing → deployment → maintenance. Documentation is emphasised at every step.
瀑布模型是一种线性顺序方法，每个阶段必须完成后才能开始下一个阶段。阶段像瀑布一样向下流动：需求 → 设计 → 实现 → 测试 → 部署 → 维护。每一步都强调文档化。
Advantages include simplicity, easy management, and well-defined milestones. It works well when requirements are clearly understood and unlikely to change. However, its rigidity is a major drawback; going back to a previous phase is difficult and expensive.
优点包括简单、易于管理和明确的里程碑。当需求被清楚理解且不太可能发生变化时，它运作良好。然而，其僵化性是一个主要缺点；回退到上一个阶段既困难又昂贵。
In IB and CIE exams, you may be asked to evaluate the waterfall model for a given scenario. Remember that it is poorly suited for large, complex projects with evolving requirements, as real users only see the product at the end.
在 IB 和 CIE 考试中，可能会要求你针对特定场景评估瀑布模型。请记住，它不适合需求不断变化的大型复杂项目，因为真实用户只能在最后看到产品。
4. Iterative and Incremental Models | 迭代与增量模型
Iterative models develop software through repeated cycles (iterations) and in smaller portions (increments), allowing for feedback between cycles. The spiral model is a prominent example, incorporating risk analysis in each iteration loop.
迭代模型通过重复的循环（迭代）和较小的部分（增量）来开发软件，允许在循环之间进行反馈。螺旋模型是一个突出的例子，在每个迭代回路中都包含风险分析。
Incremental development delivers the product in successive builds, each adding functionality. The Rational Unified Process (RUP) uses four phases (inception, elaboration, construction, transition) and relies heavily on use-case driven iterations.
增量开发通过连续的构建交付产品，每个构建增加功能。统一过程（RUP）使用四个阶段（初始、细化、构建、移交），并高度依赖用例驱动的迭代。
These models are more flexible than waterfall and can accommodate changing requirements. They enable early user feedback and reduce risk, but project management is more complex and there is a danger of scope creep without strict control.
这些模型比瀑布模型更灵活，能适应需求变化。它们使早期用户反馈成为可能并降低风险，但项目管理更加复杂，且如果没有严格的控制，存在范围蔓延的危险。
5. Agile Methodologies | 敏捷方法论
Agile development values individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan. It emphasises adaptive planning and continuous improvement.
敏捷开发重视个体和交互胜过过程和工具，可工作的软件胜过全面的文档，客户合作胜过合同谈判，响应变化胜过遵循计划。它强调自适应规划和持续改进。
Scrum is a popular Agile framework using fixed-length sprints (typically 2-4 weeks), daily stand-up meetings, and roles such as product owner, scrum master, and development team. Work is managed through a product backlog and sprint backlogs.
Scrum 是一种流行的敏捷框架，使用固定长度的冲刺（通常 2-4 周）、每日站会以及产品负责人、Scrum Master 和开发团队等角色。工作通过产品待办列表和冲刺待办列表进行管理。
Extreme Programming (XP) focuses on technical practices like pair programming, test-driven development, continuous integration, and frequent releases. Kanban visualises workflow on a board, limiting work-in-progress to optimise flow.
极限编程（XP）专注于结对编程、测试驱动开发、持续集成和频繁发布等技术实践。看板将工作流程展示在看板上，限制进行中的工作以优化流动。
Agile suits small to medium teams working on projects with evolving or unclear requirements. However, it requires disciplined, experienced developers and close customer involvement, which may not always be feasible.
敏捷适合正在处理需求不断变化或不明确的项目的中小型团队。然而，它需要纪律严明、经验丰富的开发人员和密切的客户参与，这并不总是可行的。
6. Requirements Engineering | 需求工程
Requirements engineering involves eliciting, analysing, specifying, and validating what a system should do. Functional requirements describe specific behaviours or functions (e.g., ‘the system shall encrypt user passwords’). Non-functional requirements describe quality attributes (e.g., performance, security, usability).
需求工程涉及获取、分析、说明和验证系统应该做什么。功能需求描述具体的行为或功能（例如，“系统应加密用户密码”）。非功能需求描述质量属性（例如，性能、安全性、可用性）。
Techniques for gathering requirements include interviews, questionnaires, observation, and document analysis. The IEEE 830 standard suggests characteristics of a good Software Requirements Specification (SRS): correct, unambiguous, complete, consistent, verifiable, modifiable, and traceable.
收集需求的技术包括访谈、问卷调查、观察和文档分析。IEEE 830 标准提出了良好软件需求规格说明书的特征：正确、无歧义、完整、一致、可验证、可修改和可追踪。
Common challenges are ambiguous or missing requirements, conflicting stakeholder interests, and scope creep. Prototyping can help validate requirements by giving users an early visualisation of the system.
常见的挑战包括需求模糊或遗漏、利益相关者利益冲突以及范围蔓延。原型设计可以通过给用户提供系统的早期可视化来帮助验证需求。
7. Software Design Principles | 软件设计原则
Design translates requirements into a blueprint for implementation. Key principles include abstraction (hiding complex details), modularity (dividing software into separate components with clear interfaces), and encapsulation (bundling data and methods that operate on that data).
设计将需求转化为实现的蓝图。关键原则包括抽象（隐藏复杂细节）、模块化（将软件划分为具有清晰接口的独立组件）和封装（将数据及操作数据的方法绑定在一起）。
Cohesion and coupling are critical design metrics. High cohesion within a module (elements belong together logically) and low coupling between modules (modules depend on each other minimally) lead to more maintainable and reusable code.
内聚与耦合是关键的设计度量标准。模块内的高内聚（元素在逻辑上属于一起）和模块间的低耦合（模块之间依赖最小化）导致更可维护和更可重用的代码。
Design notations such as structure charts, UML class diagrams, and flowcharts are used to communicate architecture. The top-down design approach breaks down a system into smaller sub-systems, while bottom-up design starts with low-level components and integrates them.
结构图、UML 类图和流程图等设计符号用于传达架构。自顶向下设计方法将系统分解为较小的子系统，而自底向上设计从低级组件开始并将它们集成起来。
8. Testing Strategies and Levels | 测试策略与级别
Testing aims to find defects and ensure software meets its requirements. The main levels are: unit testing (individual components/modules), integration testing (interactions between modules), system testing (the complete, integrated system), and acceptance testing (by the customer to validate readiness).
测试旨在发现缺陷并确保软件满足其需求。主要级别包括：单元测试（单个组件/模块）、集成测试（模块之间的交互）、系统测试（完整的集成系统）和验收测试（由客户验证就绪状态）。
Testing approaches include black-box testing (testing without knowledge of internal code, based on specifications) and white-box testing (testing with knowledge of internal logic, using code coverage criteria). Alpha testing is done in-house by developers; beta testing is performed by a select group of real users.
测试方法包括黑盒测试（不了解内部代码，基于规格说明进行测试）和白盒测试（了解内部逻辑，使用代码覆盖率标准进行测试）。Alpha 测试由开发人员在内部进行；Beta 测试由一组精选的真实用户执行。
Test-driven development (TDD) writes tests before the functional code, promoting simple design and confidence. Important to remember: testing can only show the presence of bugs, not their absence.
测试驱动开发（TDD）先编写测试再编写功能代码，促进简单设计并增强信心。重要的一点是：测试只能证明缺陷存在，而不能证明不存在缺陷。
9. Software Maintenance and Evolution | 软件维护与演化
Maintenance is the process of modifying a software system after delivery. It has four categories: corrective (fixing bugs), adaptive (adjusting to environmental changes, e.g., new operating system), perfective (improving performance or adding features), and preventive (reducing future risks by restructuring code).
维护是软件交付后进行修改的过程。它有四类：纠正性维护（修复错误）、适应性维护（调整以应对环境变化，例如新操作系统）、完善性维护（提高性能或增加功能）和预防性维护（通过重构代码降低未来风险）。
Maintenance typically consumes 60–80% of total software lifecycle cost. Good design and documentation dramatically reduce maintenance effort. Legacy systems often pose challenges due to outdated technology, lack of documentation, and rigid architecture.
维护通常消耗软件总生命周期成本的 60–80%。良好的设计和文档能大幅减少维护工作。遗留系统常常因技术过时、缺少文档和僵化架构而带来挑战。
Refactoring is a key technique: it improves the internal structure of code without changing its external behaviour, making it easier to maintain and extend.
重构是一项关键技术：它在不改变代码外部行为的同时改善其内部结构，使其更易于维护和扩展。
10. Project Management and Tools | 项目管理与工具
Effective project management is crucial for delivering software on time and within budget. Key activities include planning, scheduling, risk management, resource allocation, and progress monitoring. Tools such as Gantt charts and PERT diagrams help visualise timelines and dependencies.
有效的项目管理对于按时和在预算内交付软件至关重要。关键活动包括计划、调度、风险管理、资源分配和进度监控。甘特图和 PERT 图等工具有助于可视化时间线和依赖关系。
Gantt charts show tasks as horizontal bars over a calendar, making it easy to see start/end dates and overlaps. PERT (Program Evaluation and Review Technique) charts use a network diagram to display task sequence and identify the critical path, where delays will affect the project end date.
甘特图将任务显示为日历上的水平条形，便于看到开始/结束日期和重叠。PERT（计划评估和审查技术）图使用网络图显示任务顺序并确定关键路径，该路径上的延迟会影响项目结束日期。
Version control systems (e.g., Git) are essential for team collaboration, allowing multiple developers to work concurrently, track changes, and revert to previous states. Configuration management ensures consistency across all project artefacts.
版本控制系统（例如 Git）对于团队协作至关重要，允许多个开发人员同时工作、跟踪更改并回退到先前状态。配置管理确保所有项目工件的整体一致性。
11. Software Quality and Standards | 软件质量与标准
Software quality encompasses multiple attributes: functional suitability, reliability, usability, efficiency, maintainability, and portability (ISO/IEC 25010 standard). Quality assurance (QA) activities are applied throughout the SDLC to prevent defects, while quality control (QC) focuses on detecting them.
软件质量涵盖多个属性：功能适用性、可靠性、可用性、效率、可维护性和可移植性（ISO/IEC 25010 标准）。质量保证活动贯穿整个软件开发生命周期以预防缺陷，而质量控制侧重于检测缺陷。
Reviews and inspections are static techniques for finding errors without executing code. Walkthroughs and formal technical reviews involve peers examining documents, design, or code to catch issues early, drastically reducing downstream costs.
评审和检查是无需执行代码就可发现错误的静态技术。走查和正式技术评审由同行检查文档、设计或代码以及早发现问题，从而大幅降低下游成本。
International standards like ISO 9001 provide frameworks for quality management systems, and the Capability Maturity Model Integration (CMMI) assesses process maturity from Level 1 (initial) to Level 5 (optimising). High maturity correlates with better predictability and quality.
ISO 9001 等国际标准为质量管理体系提供框架，能力成熟度模型集成（CMMI）将过程成熟度从 1 级（初始级）评估到 5 级（优化级）。高成熟度与更好的可预测性和质量相关。
12. Human-Computer Interaction and Ethical Issues | 人机交互与伦理问题
Usability ensures that a software product is easy to learn, efficient to use, and pleasant for the user. Principles of user-centred design include early focus on users, empirical measurement, and iterative design. Heuristics by Nielsen (e.g., visibility of system status, user control, error prevention) guide interface evaluation.
可用性确保软件产品易于学习、高效使用且让用户感到愉悦。以用户为中心的设计原则包括早期关注用户、基于经验的度量和迭代设计。Nielsen 的启发式原则（例如系统状态可见性、用户控制、错误预防）指导界面评估。
Ethical considerations in software engineering involve privacy, data protection, intellectual property, and the impact of software failures. Professional codes like the ACM/IEEE Code of Ethics require acting in the public interest, maintaining integrity, and respecting confidentiality.
软件工程中的伦理考量涉及隐私、数据保护、知识产权以及软件故障的影响。ACM/IEEE 伦理准则等专业规范要求为公众利益行事、保持诚信并尊重机密性。
Computer scientists must recognise the societal implications of systems they build, including bias in algorithms, accessibility for disabled users, and digital divides. Sustainability in software engineering also means designing systems that are energy-efficient and long-lasting.
计算机科学家必须认识到他们所构建系统的社会影响，包括算法中的偏见、残疾用户的可用性以及数字鸿沟。软件工程的可持续性还意味着设计节能且耐用的系统。
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