h模型,x模型,瀑布模型_瀑布模型的利与弊

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

What is Waterfall Model?

什么是瀑布模型？

Waterfall model is the classic Software Development Life Cycle method practiced in software development process. As the name "waterfall" describes, this development is flowing downwards steadily like waterfall, i.e., proceeds from one phase to another phase. This process is a sequential process or a linear process where in the output of one phase is input of another phase. So previous phase becomes important to be completed before we move to next phase.

瀑布模型是在软件开发过程中实践的经典软件开发生命周期方法。 正如“瀑布”一词所描述的，这种发展像瀑布一样稳定地向下流动，即从一个阶段发展到另一阶段。 该过程是顺序过程或线性过程，其中在一个相的输出中是另一相的输入。 因此，在进入下一阶段之前，必须完成上一阶段的工作。

Here is the diagram that describes all phases of waterfall model.

这是描述瀑布模型所有阶段的图。

Requirement Gathering and Analysis Phase: This is the first phase where requirements to produce a product are gathered and analyzed. This is the phase which involves customer. All information about the entire process are identified to be designed and delivered here.

需求收集和分析阶段：这是收集和分析生产产品的需求的第一个阶段。 这是涉及客户的阶段。 有关整个过程的所有信息都将在此处进行设计和交付。

Design Phase: The requirements from the earlier phase are documented and converted into technical design. Like what hardware, system software, technology, language are used etc. are specified.

设计阶段：记录早期阶段的需求并将其转换为技术设计。 就像指定了什么硬件，系统软件，技术，语言等。

Implement Phase:  Output from Design phase are used and implemented to achieve the goal. They are split in program units. These program units are developed independently and functionally tested. This is called Unit Testing.

实施阶段：设计阶段的输出用于实现目标。 它们分为程序单元。 这些程序单元是独立开发并经过功能测试的。 这称为单元测试。

Test Phase: Here all program units which are developed in implement phase are integrated and tested together to see end product has all desired functionalities required.

测试阶段：在这里，将在实施阶段开发的所有程序单元进行集成和测试，以查看最终产品具有所需的所有所需功能。

Deploy Phase: Once Test phase is successfully completed, it is deployed in customer environments and product is released.

部署阶段：成功完成测试阶段后，便会在客户环境中部署它并发布产品。

Maintenance Phase: If any changes are required in client environments then they are upgraded and released as patches to fix any issues that come up after deployment.

维护阶段：如果客户端环境中需要任何更改，则将它们升级并作为补丁发布，以解决部署后出现的所有问题。

Waterfall Model Pros:

瀑布模型的优点：

1. Simple, easy to understand and use.

1.简单，易于理解和使用。

2. All phases are clearly documented and understood well in the beginning of software development life cycle

2.在软件开发生命周期的开始阶段，所有阶段都被清楚地记录和很好地理解

3. Since each phase has to be completed before we move to next phase issues will be identified and corrected in initial phase itself.

3.由于在进入下一阶段之前必须完成每个阶段，因此将在初始阶段中识别并纠正问题。

4. Since requirements are well understood and analyzed in beginning of project customer involvement in later phases is minimized.

4.由于在项目开始时就可以很好地理解和分析需求，因此可以将客户在后期阶段的参与降至最低。

5. High Visibility - The output of each stage gives more visibility on where we stand on progress of development.

5.高度可见性-每个阶段的输出使我们对开发进度的立场更具可见性。

6. This approach has control over deadline as work is distributed to teams in each stage.

6.这种方法可以控制截止日期，因为工作分配到每个阶段的团队。

Waterfall Model cons:

瀑布模型的缺点：

1. Not Flexible. Because this is a rigid model, Requirements cannot be changed throughout the cycle.

1.不灵活。 由于这是一个严格的模型，因此无法在整个周期内更改需求。

2. With rapid change in technology day by day we cannot have control to change the hardware and system requirements. Since system and hardware requirements are set up by customers in the beginning.

2.随着技术的日新月异，我们无法控制更改硬件和系统要求。 由于系统和硬件要求是一开始由客户设置的。

3. Small change in one phase leads to big change in each phase, as these phases are dependent on one another and eventually more time is consumed

3.一个阶段的小变化会导致每个阶段的大变化，因为这些阶段相互依赖，最终会消耗更多的时间

4. If assumptions about implementations are wrong then estimated time for each phases exceeds and fails to meet deadline.

4.如果关于实施的假设是错误的，则每个阶段的估计时间将超过且未能达到期限。

5. Resource idle time might increase as they have to be idle until previous stage is completely done. Therefore it is expensive.

5.资源闲置时间可能会增加，因为它们必须闲置，直到上一步完成为止。 因此，它是昂贵的。

6. Difficult to see the progress within phases.

6.难以分阶段看到进度。

7. Challenges, major issues, bottlenecks are identified in last stages in integration testing. So no visibility of these in the beginning and high risk.

7.在集成测试的最后阶段确定了挑战，主要问题和瓶颈。 因此，这些在开始时就没有可见性，而且风险很高。

8. Product/Software deliverables are at the end of cycle.

8.产品/软件可交付成果在周期结束时。

When to Choose waterfall Approach?

什么时候选择瀑布方式？

1. Choose this approach for small projects.

1.对于小型项目，请选择此方法。

2. This method is best suited for products which has stable definition.

2.此方法最适合分辨率稳定的产品。

3. This is best approach when the requirements are very well known and are not fluctuating.

3.当需求众所周知并且没有波动时，这是最佳方法。

4. Use this approach when Process has clear objectives and solutions.

4.当流程具有明确的目标和解决方案时，请使用此方法。

5. Use when you want to conserve the resources

5.当您想节省资源时使用

翻译自: https://www.experts-exchange.com/articles/17441/Waterfall-Model-pros-and-cons.html

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