文章目录
题目
- 软件工程的定义
- 解释导致 software crisis 本质原因、表现，述说克服软件危机的方法
- 软件生命周期
- SWEBoK 的 15 个知识域（An Overview of the SWEBOK Guide 请中文翻译其名称与简短说明）
- 简单解释 CMMI 的五个级别。例如：Level 1 - Initial：无序，自发生产模式。
- 用自己语言简述 SWEBok 或 CMMI （约200字）
软件工程的定义
“the systematic application of scientific and technological knowledge, methods, and experience to the design, implementation, testing, and documentation of software”—The Bureau of Labor Statistics—IEEE Systems and software engineering - Vocabulary
“The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software”—IEEE Standard Glossary of Software Engineering Terminology
可以理解为，软件工程是系统地将科学技术知识，方法和经验应用于软件的设计，实施，测试和记录；或者说，应用系统，规范，可量化的方法来开发，运行和维护软件。软件工程是指导计算机软件开发和维护的一门工程学科。采用工程化的方法来开发和维护软件，把经过实践考验而证明正确的工程管理技术和当前能够得到的最好的技术方法结合起来，以经济地开发出高质量的软件并有效的维护它。
解释导致 software crisis 本质原因、表现，述说克服软件危机的方法
本质原因
The major cause of the software crisis is that the machines have become several orders of magnitude more powerful! To put it quite bluntly: as long as there were no machines, programming was no problem at all; when we had a few weak computers, programming became a mild problem, and now we have gigantic computers, programming has become an equally gigantic problem.
— Edsger Dijkstra, The Humble Programmer (EWD340), Communications of the ACM
因此其本质原因是，落后的软件生产方式无法满足迅速增长的计算机软件需求，从而导致软件开发与维护过程中出现一系列严重问题。
表现：
-
软件开发进度难以预测
-
软件开发成本难以控制
-
用户对产品功能难以满足
-
软件产品质量无法保证
-
软件产品难以维护
-
软件缺少适当的文档资料
解决方法：
- 充分吸收和借鉴人类长期以来从事各种工程项目中积累的行之有效的有效原理、概念、技术与方法，特别是吸取几十年来人类从事计算机硬件研究和开发的经验教训。在开发软件的过程中努力作到良好的组织，严格的管理，相互友好的协作。
- 推广在实践中总结出来的开发软件的成功的技术和方法，并研究更好、更有效的技术和方法，尽快克服在计算机系统早期发展阶段形成的一些错误概念和作法。
- 根据不同的应用领域，开发更好的软件工具并使用这些工具。将软件开发各个阶段使用的软件工具集合成一个整体，形成一个很好的软件开发支环环境。
软件生命周期
软件的生命周期，亦称软件的生存周期。软件开发项目中，有几种常见的生命周期模型，如瀑布模型、增量模型，螺旋模型、原型开发、倒V模型等。它是按开发软件的规模和复杂程度，从时间上把软件开发的整个过程（从计划开发开始到软件报废为止的整个历史阶段）进行分解，形成相对独立的几个阶段，每个阶段又分解成几个具体的任务，然后按规定顺序依次完成各阶段的任务并规定一套标准的文档作为各个阶段的开发成果，最后生产出高质量的软件。
-
问题的定义及规划：
确定软件开发总的目标；给出软件的功能，性能，可靠性以及借口等方面的设想；研究完成该项目的可行性探讨问题的解决方法；对可供使用的资源成本可取得的效益和开发的进度进行估计 -
需求分析：
对开发的软件进行详细的定义，由用户和用户共同探讨决定，那些需求可以满足，并给予确切的描述，写出软件需求说明书。软件研发的类型不同，需求的来源也不不同。 -
软件设计：
是整个软件工程的核心，需要完成软件设计说明书，分为概要设计（HLD）:在设计阶段把各项需求转换为相应的体系结构，每一步是功能明确的模块。详细设计（LLD）：对每一个模块要完成的任务进行具体的描述。 -
程序编码：
此阶段是将软件设计的结果转换成计算机可运行的程序代码。在程序编码中必须要制定统一，符合标准的编写规范。以保证程序的可读性，易维护性，提高程序的运行效率。 -
软件测试：
在软件设计完成后要经过严密的测试，以发现软件在整个设计过程中存在的问题并加以纠正。整个测试过程分单元测试、集成测试以及系统测试三个阶段进行。测试的方法主要有白盒测试和黑盒测试两种。在测试过程中需要建立详细的测试计划并严格按照测试计划进行测试，以减少测试的随意性。 -
运行维护：
软件维护是软件生命周期中持续时间最长的阶段。在软件开发完成并投入使用后，由于多方面的原因，软件不能继续适应用户的要求。要延续软件的使用寿命，就必须对软件进行维护。软件的维护包括纠错性维护和改进性维护两个方面。
软件生命周期模型
为了使规模大、结构复杂和管理复杂的软件开发变的容易控制和管理，人们把整个软件生命周期划分为若干阶段，使得每个阶段有明确的任务，整理出软件生命周期模型。软件生命周期模型是指人们为开发更好的软件而归纳总结的软件生命周期的典型实践参考。有几种常见的生命周期模型，如瀑布模型、增量模型，螺旋模型、原型开发、倒V模型等。
SWEBoK 的 15 个知识域
注意：以下出现的KA均为Knowledge Areas
软件需求
The Software Requirements KA is concerned with the elicitation, negotiation, analysis, specification, and validation of software requirements. It is widely acknowledged within the software industry that software engineering projects are critically vulnerable when these activities are performed poorly. Software requirements express the needs and constraints placed on a software product that contribute to the solution of some real-world problems.
软件要求KA关注软件需求的启发，协商，分析，规范和验证。在软件行业中，人们普遍认为，当这些活动表现不佳时，软件工程项目非常容易受到攻击。软件需求表达了对软件产品的需求和限制，这些需求和约束有助于解决一些现实问题。
软件设计
Design is defined as both the process of defining the architecture, components, interfaces, and other characteristics of a system or component and the result of [that] process (IEEE 1991). The Software Design KA covers the design process and the resulting product. The software design process is the software engineering life cycle activity in which software requirements are analyzed in order to produce a description of the software’s internal structure and its behavior that will serve as the basis for its construction. A software design (the result) must describe the software architecture – that is, how software is decomposed and organized into components and the interfaces between those components. It must also describes the components at a level of detail that enables their construction.
设计是软件工程最核心的内容。设计既是“过程”，也是这个过程的“结果”。软件设计由软件体系结构设计、软件详细设计两种活动组成。它涉及软件体系结构、构件、接口、以及系统或构件的其它特征，还涉及软件设计质量分析和评估、软件设计的符号、软件设计策略和方法等。
软件构造
Software construction refers to the detailed creation of working software through a combination of detailed design, coding, unit testing, integration testing, debugging, and verification. The Software Construction KA includes topics related to the development of software programs that will satisfy their requirements and design constraints. This KA covers software construction fundamentals; managing software construction; construction technologies; practical considerations; and software construction tools.
软件构建是指通过结合详细设计，编码，单元测试，集成测试，调试和验证来详细创建工作软件。软件构建KA包括与满足其要求和设计约束的软件程序开发相关的主题。该KA涵盖了软件构建基础; 管理软件建设; 建筑技术; 实际考虑; 和软件构建工具。
软件测试
Testing is an activity performed to evaluate product quality and to improve it by identifying defects. Software testing involves dynamic verification of the behavior of a program against expected behavior on a finite set of test cases. These test cases are selected from the (usually very large) execution domain. The Software Testing KA includes the fundamentals of software testing; testing techniques; human-computer user interface testing and evaluation; test-related measures; and practical considerations.
测试是软件生存周期的重要部分，涉及测试的标准、测试技术、测试度量和测试过程。测试不再是编码完成后才开始的活动，测试的目的是标识缺陷和问题，改善产品质量。软件测试应该围绕整个开发和维护过程。测试在需求阶段就应该开始，测试计划和规程必须系统，并随着开发的进展不断求精。正确的软件工程质量观是预防，避免缺陷和问题比改正好。代码生成前的主要测试手段是静态技术（检查），代码生成后采用动态技术（执行代码）。测试的重点是动态技术，从程序无限的执行域中选择一个有限的测试用例集，动态地验证程序是否达到预期行为。
软件维护
Software maintenance involves enhancing existing capabilities, adapting software to operate in new and modified operating environments, and correcting defects. These categories are referred to as perfective, adaptive, and corrective software maintenance. The Software Maintenance KA includes fundamentals of software maintenance (nature of and need for maintenance, categories of maintenance, maintenance costs); key issues in software maintenance (technical issues, management issues, maintenance cost estimation, measurement of software maintenance); the maintenance process; software maintenance techniques (program comprehension, re-engineering, reverse engineering, refactoring, software retirement); disaster recovery techniques, and software maintenance tools.
软件产品交付后，需要改正软件的缺陷、提高软件性能或其他属性、使软件产品适应新的环境。软件维护是软件进化的继续。软件维护要支持系统快速地、便捷地满足新的需求。基于服务的软件维护越来越受到重视。软件维护是软件生存周期的组成部分。然而，历史上维护从未受到重视。情况有了改变，软件组织力图使软件运营时间更长，软件维护成为令人关注的焦点。
软件配置管理
The configuration of a system is the functional and/or physical characteristics of hardware, firmware, software, or a combination of these. It can also be considered as a collection of specific versions of hardware, firmware, or software items combined according to specific build procedures to serve a particular purpose. Software configuration management (SCM) is thus the discipline of identifying the configuration of a system at distinct points in time for the purposes of systematically controlling changes to the configuration, as well as maintaining the integrity and traceability of the configuration throughout the software life cycle. The Software Configuration Management KA covers management of the SCM process; software configuration identification, control, status accounting, auditing; software release management and delivery; and software configuration management tools.
为了系统的控制配置变更，维护整个系统生命周期中配置的一致性和可追踪性，必须按时间管理软件的不同配置，包括配置管理过程的管理、软件配置鉴别、配置管理控制、配置管理状态记录、配置管理审计、软件发布和交付管理等。
软件工程管理
Software engineering management involves planning, coordinating, measuring, reporting, and controlling a project or program to ensure that development and maintenance of the software is systematic, disciplined, and quantified. The Software Engineering Management KA covers initiation and scope definition (determining and negotiating requirements, feasibility analysis, and review and revision of requirements); software project planning (process planning, estimation of effort, cost, and schedule, resource allocation, risk analysis, planning for quality); software project enactment (measuring, reporting, and controlling; acquisition and supplier contract management); product acceptance; review and analysis of project performance; project closure; and software management tools.
软件工程管理涉及计划、协调、度量、监控、控制和报告，以确保软件的开发和维护是系统化的，规范化的和量化的。软件工程管理KA涵盖了启动和范围定义（确定和协商要求，可行性分析以及要求的审查和修订）; 软件项目计划（过程计划，工作量估算，成本和进度，资源分配，风险分析，质量计划）; 软件项目制定（计量，报告和控制;收购和供应商合同管理）; 产品验收; 审查和分析项目绩效; 项目结束; 和软件管理工具。
软件工程过程
The Software Engineering KA is concerned with definition, implementation, assessment, measurement, management, and improvement of software life cycle processes. Topics covered include process implementation and change (process infrastructure, models for process implementation and change, and software process management); process definition (software life cycle models and processes, notations for process definition, process adaptation, and process automation); process assessment models and methods; measurement (process measurement, products measurement, measurement techniques, and quality of measurement results); and software process tools.
软件工程KA关注软件生命周期过程的定义，实施，评估，测量，管理和改进。涵盖的主题包括流程实施和变更（流程基础架构，流程实施和变更模型以及软件流程管理）; 流程定义（软件生命周期模型和流程，流程定义，流程适应和流程自动化的符号）; 过程评估模型和方法; 测量（过程测量，产品测量，测量技术和测量结果的质量）; 和软件处理工具。
软件工程模型和方法
The Software Engineering Models and Methods KA addresses methods that encompass multiple life cycle stages; methods specific to particular life cycle stages are covered by other KAs. Topics covered include modeling (principles and properties of software engineering models; syntax vs. semantics vs. invariants; preconditions, post-conditions, and invariants); types of models (information, structural, and behavioral models); analysis (analyzing for correctness, completeness, consistency, quality and interactions; traceability; and tradeoff analysis); and software development methods (heuristic methods, formal methods, prototyping methods, and agile methods).
软件开发工具是以计算机为基础的，用于辅助软件生存周期过程。通常，工具是为特定的软件工程方法设计的，以减少手工操作的负担、使软件工程更加系统化。软件工具的种类很多，从支持个人到整个生存周期。软件工具分为：需求工具、设计工具、构造工具、测试工具、维护工具、配置管理工具、工程管理工具、工程过程工具、软件质量工具等。
软件工程方法支持软件工程活动，使软件开发更加系统，并能获得成功。软件开发方法不断发展。当前，软件工程方法分为：①启发式方法，包括结构化方法、面向数据方法、面向对象方法和特定域方法；②基于数学的形式化方法；③用软件工程多种途径实现的原型方法，原型方法帮助确定软件需求、软件体系结构，用户界面等。
软件质量
Software quality is a pervasive software life cycle concern that is addressed in many of the SWEBOK V3 KAs. In addition, the Software Quality KA includes fundamentals of software quality (software engineering cultures, software quality characteristics, the value and cost of software quality, and software quality improvement); software quality management processes (software quality assurance, verification and validation, reviews and audits); and practical considerations (defect characterization, software quality measurement, and software quality tools).
软件质量贯穿整个软件生存周期，涉及软件质量需求、软件质量度量、软件属性检测、软件质量管理技术和过程等。
SWEBOK还把软件工程相关学科列为知识域，它们是软件工程发展不可或缺的部分。相关学科知识域包括计算机工程、计算机科学、数学、管理学、项目管理、质量管理、系统工程学和软件人类工程学八个领域。
软件工程专业实践
Software engineering professional practice is concerned with the knowledge, skills, and attitudes that software engineers must possess to practice software engineering in a professional, responsible, and ethical manner. The Software Engineering Professional Practice KA covers professionalism (professional conduct, professional societies, software engineering standards, employment contracts, and legal issues); codes of ethics; group dynamics (working in teams, cognitive problem complexity, interacting with stakeholders, dealing with uncertainty and ambiguity, dealing with multicultural environments); and communication skills.
软件工程专业实践是指软件工程师必须具备的知识、技能和态度，以便以专业、负责任和合乎道德的方式实践软件工程。软件工程专业实践KA涵盖专业性（专业行为，专业协会，软件工程标准，雇佣合同和法律问题）; 道德准则; 小组动态（团队合作，认知问题复杂性，与利益相关者互动，处理不确定性和模糊性，处理多元文化环境）; 和沟通技巧。
软件工程经济学
The Software Engineering Economics KA is concerned with making decisions within the business context to align technical decisions with the business goals of an organization. Topics covered include fundamentals of software engineering economics (proposals, cash flow, the time-value of money, planning horizons, inflation, depreciation, replacement and retirement decisions); not for-profit decision-making (cost-benefit analysis, optimization analysis); estimation, economic risk and uncertainty (estimation techniques, decisions under risk and uncertainty); and multiple attribute decision making (value and measurement scales, compensatory and non-compensatory techniques).
软件工程经济学KA关注的是在业务上下文中做出决策，使技术决策与组织的业务目标保持一致。涵盖的主题包括软件工程经济学的基本原理(建议、现金流、金钱的时间价值、规划范围、通货膨胀、折旧、替换和退休决定);非营利性决策(成本效益分析、优化分析);评估、经济风险与不确定性(评估技术、风险与不确定性下的决策);多属性决策(价值和度量尺度、补偿和非补偿技术)。
计算基础
The Computing Foundations KA covers fundamental topics that provide the computing background necessary for the practice of software engineering. Topics covered include problem solving techniques, abstraction, algorithms and complexity, programming fundamentals, the basics of parallel and distributed computing, computer organization, operating systems, and network communication.
计算基础KA涵盖了为软件工程实践提供必要的计算背景的基本主题。主题包括问题解决技术、抽象、算法和复杂性、编程基础、并行和分布式计算基础、计算机组织、操作系统和网络通信。
数学基础
The Mathematical Foundations KA covers fundamental topics that provide the mathematical background necessary for the practice of software engineering. Topics covered include sets, relations, and functions; basic propositional and predicate logic; proof techniques; graphs and trees; discrete probability; grammars and finite state machines; and number theory.
数学基础KA涵盖了提供软件工程实践所必需的数学背景的基础主题。涵盖的主题包括集合，关系和功能; 基本命题和谓词逻辑; 证明技术; 图形和树木; 离散概率; 语法和有限状态机; 和数论。
工程基础
The Engineering Foundations KA covers fundamental topics that provide the engineering background necessary for the practice of software engineering. Topics covered include empirical methods and experimental techniques; statistical analysis; measurements and metrics; engineering design; simulation and modeling; and root cause analysis.
工程基础KA涵盖了提供软件工程实践所必需的工程背景的基础主题。涵盖的主题包括经验方法和实验技术; 统计分析; 测量和指标; 工程设计; 仿真与建模; 和根本原因分析。
简单解释 CMMI 的五个级别
Level 1 - Initial：无序，自发生产模式
Level 2 Managed 程序用于描述项目特征，并且通常具有反应性
Level 3 Defined 程序用于描述组织特征，并且通常具有积极主动性
Level 4 - Quantitatively Managed：量化管理，良好地控制并测量进程
Level 5 - Optimizing：优化过程，聚焦于连续的进程优化
内容来自Wikipedia
简述 SWEBok 或 CMMI
SWEBok定义了受到了良好本科训练并且从事软件行业满四年的工程师所应具备的知识体系，为软件工程职业建立了合适的准则和规范集。它将软件工程学科的本体知识分为十个知识域（SWEBok2004），十个知识域可分为两类过程，一是开发与维护过程，包括软件需求，软件设计等，二是支持和组织过程，包括软件配置管理，软件工程管理等。这个知识体系的目的不在于知识本身，知识早已存在，而在于在表征软件工程学科特点的核心知识子集上达成世界性的共识，为软件工程规定教育要求、划分职业类别，确定开发任务等提供一致的见解。
1万+
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
