软件工程生命周期模型_软件生命周期模型比较| 软件工程

软件工程生命周期模型

软件生命周期模型 (Software Lifecycle Models)

There are five software lifecycle models that are commonly used while developing any software. These are as follows:

开发任何软件时，通常使用五个软件生命周期模型。这些如下：

The classical waterfall model

古典瀑布模型
The iterative waterfall model

迭代瀑布模型
The prototyping model

原型模型
The evolutionary model

进化模型
The spiral model

螺旋模型

Now, let us compare each of them based on their features, and list each of their pros and cons. Also, we will list the situations in which the particular model should be used and also the situations where these models must not be used.

现在，让我们根据它们的功能进行比较，并列出它们的优缺点。另外，我们将列出应使用特定模型的情况以及不得使用这些模型的情况。

各种软件生命周期模型的比较 (Comparisons of various software lifecycle models)

The comparison table of these models is as follows:

这些模型的比较表如下：

Software lifecycle Model	Features	Advantages	Disadvantages
Classical waterfall model	Has defined phases Follows all phases in the mentioned order The flow of phase execution cannot be broken Iteration is not allowed	Simple to use, understand and implement Managed work	No scope of risk management New features cannot be added or modified in the software after the development has begun. Error is detected at the end of every phase
Iterative lifecycle model	Enhanced classical waterfall model in which Iterations are allowed Most commonly used	Risk management is possible Updates and modification can be made in any phase Easy to understand and implement	Risks cannot be handled efficiently Developer's idle hours are too high
Prototyping model	The prototype of the model is made before the actual software User Interface usually is much more attractive in this model	It can be used where the user requirements are not defined. Takes user feedback from time to time User's satisfaction is a priority here	Is costly The communication that is required between the customer and the developer is not always possible to get Takes a lot of time to develop
Evolutionary model	Software is developed through different modules in an incremental manner This model deals with the different versions of the software Each version is an enhanced version of the previous one	Large projects can be developed efficiently through this model Every version is capable of to fully function the mentioned functionalities	Is suitable only for large projects Takes time to develop Module integration is difficult
Spiral model	The phases are divided in the form of loops Further, the loops are divided into four quadrants Each block of this model contains a set of activities that the software performs	Most versatile model Able to manage almost every type of risk Complex projects can be created using this model	Is complex to understand and implement Not suitable for ordinary software models Costly to develop Time consuming

软件生命周期模型	特征	优点	缺点
古典瀑布模型	已定义阶段遵循上述顺序的所有阶段阶段执行流程不可中断不允许迭代	易于使用，理解和实施管理工作	没有风险管理范围开发开始后，无法在软件中添加或修改新功能。在每个阶段结束时检测到错误
迭代生命周期模型	增强的经典瀑布模型，允许迭代最常用的	可以进行风险管理可以在任何阶段进行更新和修改易于理解和实施	风险无法有效处理开发人员的闲置时间太长
原型模型	模型的原型是在实际软件之前制作的在这种模式下，用户界面通常更具吸引力	可以在未定义用户要求的地方使用。不时获取用户反馈用户满意是这里的重中之重	昂贵客户与开发人员之间所需的交流并非总是可以得到的需要很多时间来开发
进化模型	通过不同的模块以增量方式开发软件该模型处理软件的不同版本每个版本都是前一个版本的增强版本	通过此模型可以有效地开发大型项目每个版本都能够完全发挥上述功能	仅适用于大型项目需要时间来发展模块集成困难
螺旋模型	阶段以循环形式划分此外，循环分为四个象限该模型的每个模块都包含软件执行的一组活动	最通用的型号能够管理几乎所有类型的风险可以使用此模型创建复杂的项目	难以理解和实施不适合普通软件模型开发成本高耗时的

翻译自: https://www.includehelp.com/basics/comparison-of-software-lifecycle-models-software-engineering.aspx

软件工程生命周期模型