h模型,x模型,瀑布模型_古典瀑布模型

h模型,x模型,瀑布模型

The classical waterfall model is one of the oldest software lifecycle models that were developed to provide a systematic approach to the developers for developing any software. It can be said that all the other software lifecycle models were derived from this classical waterfall model just by adding some additional features and omitting some.

经典瀑布模型是最古老的软件生命周期模型之一，旨在为开发人员提供系统的方法来开发任何软件。 可以说，所有其他软件生命周期模型都是通过添加一些附加功能并省略一些功能而从此经典瀑布模型派生而来的。

The name waterfall itself defines the characteristics of the model. As a waterfall flows only downwards and cannot flow back, in the same way, the phases in the waterfall model are followed one after the other in the same sequence as mentioned. And after completing a phase and entering into another phase, we cannot go back to the previous phase.

瀑布本身定义了模型的特征。 由于瀑布仅向下流动而不能倒流，因此，以相同的方式， 瀑布模型中的各个阶段按照上述相同顺序依次进行。 在完成一个阶段并进入另一个阶段之后，我们无法返回上一个阶段。

The different phases that are included in the classical waterfall model are:

经典瀑布模型包含的不同阶段是：

• Feasibility study

  可行性研究

• Requirement analysis and specification

  需求分析和规范

• Design

  设计

• Coding and unit testing

  编码和单元测试

• Integration and system testing

  集成和系统测试

• Maintenance

  保养

An overview of these phases of the classical waterfall model can be made from the following diagram:

可以从下图概述经典瀑布模型的这些阶段 ：

Each of the phases of this model is executed one after the other. You cannot break the flow and you cannot go back to the previous phase as stated earlier.

此模型的每个阶段都一个接一个地执行。 您不能中断流程，也不能返回到前面所述的上一个阶段。

This means that if you are in the design phase, then you cannot conduct the requirement analysis and specification study for the software. That has already been earlier and now there is no scope left for making any kind of changes in the software requirements according to the classical waterfall model. All that needs to be completed before getting onto the design phase.

这意味着，如果您处于设计阶段，则无法进行软件的需求分析和规格研究。 那已经很早了，现在没有根据经典瀑布模型对软件需求进行任何形式更改的余地。 在进入设计阶段之前，所有需要完成的工作。

We can also relate this model with our many days to day activities that must be performed in a particular order. This can be well understood with the following example:

我们还可以将此模型与必须按特定顺序执行的许多日常活动联系起来。 通过以下示例可以很好地理解这一点：

Suppose you want to make a dish in a couple of hours. Then your feasibility phase and requirement analysis phase starts in the initial phase of making the dish itself. First, you need to decide what you will be making. That is your feasibility study. Now let’s say your requirements include chopping board, vegetables, flour, spices, oil, etc. You need to list them up before going to the market itself. That’s your requirements and specification phase. Now you prepare everything up and assemble in the utensil. That’s the designing part. And the cooking and tasting part becomes your coding and testing part. Final plating of the dish in the integration part and then you finally present your dish in front of the customers. After that, adding any sort of extra spices or re-heating the dish in some cases can be thought as of your maintenance part.

假设您要在几个小时内做一道菜。 然后，您的可行性阶段和需求分析阶段将从制作盘子本身的初始阶段开始。 首先，您需要决定要做什么。 那是你的可行性研究。 现在，假设您的需求包括砧板，蔬菜，面粉，香料，油等。您需要先列出它们，然后才能进入市场。 那就是您的需求和规范阶段。 现在您准备好所有东西并组装在器具中。 那是设计的部分。 烹饪和品尝部分成为您的编码和测试部分。 在集成部分对盘子进行最后的电镀，然后您最终将盘子展示给客户。 之后，在您的维护部分，可以考虑添加任何种类的额外香料或在某些情况下重新加热餐具。

So you see, if you skip any of the phase-in between or break the flow of these phases, then you will not be able to present your final dish in front of the customers on time.

因此，您会看到，如果您跳过这些阶段之间的任何阶段或中断这些阶段的流程，那么您将无法按时在客户面前展示您的最终菜肴。

翻译自: https://www.includehelp.com/basics/the-classical-waterfall-model.aspx

h模型,x模型,瀑布模型