blocks|key|1692106|text|定义会有所不同，所以我怀疑你能否得到这个问题的结论性答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1692107|尽管如此，我所看到的最明显的潜在差异是迭代与您的高层设计/体系结构之间的关系：|1692108|在迭代瀑布模型中，您可以在详细设计/建造/测试的多个阶段中更多地使用迭代来细化/细化总体设计的元素。理论上，您可以提前计划大部分迭代。|unordered-list-item|1692109|在一个真正的进化模型中，你不会有一个整体的设计--你只是在添加你已经构建的任何东西，它是基于一些关于下一步最有价值的工作的概念，通常是通过用户的强烈反馈得到的。对于未来的迭代，您不会有固定的计划(尽管您可能会保留一个优先级优先的待办事项或类似的东西)。|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|L|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|M|8|@]|9|@]|A|$]]]|I|$]]

Definitions will vary so I doubt you will get a conclusive answer to this question.

Having said that, the most obvious potential difference I see is how the iterations relate to your high level design / architecture:

<ul>
<li>In an iterative waterfall model, you might use the iterations more for refinement/elaboration of elements of the overall design in multiple phases of [detailed design / build / test]. In theory, you could plan most of the iterations in advance.</li>
<li>In a true evolutionary model you would not have an overall design - you'd just be adding to whatever you have already built based on some notion of what is most valuable to do next, typically gained through intensive user feedback. You wouldn't have a fixed plan for future iterations (although you might keep a prioritised backlog or something similar).</li>
</ul>

blocks|key|5428282|text|“进化设计”是一个通用术语，包括使用某种突变/选择机制(即更改-测试-拒绝/接受循环)的所有设计方法；“迭代瀑布”专门描述了迭代应用瀑布模型的开发过程。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5428283|一个非正式的单一开发过程，所有的开发都发生在一台机器上，根据需要进行临时更改，并在它们被认为“准备好”时部署，这当然是一种进化设计模型，但它不符合瀑布的定义，即使在其最轻松的解释中也是如此。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

"Evolutionary design" is a general term, covering all design methods that use some sort of mutation/selection mechanism (that is, change - test - reject / accept cycles); "Waterfall with iterations" specifically describes a development process that applies the Waterfall model iteratively.

An informal single-developer process where all development happens on one machine, changes are made ad-hoc as needed, and deployed whenever they are considered 'ready', is certainly an evolutionary design model, but it hardly fits the Waterfall definition, not even in its most relaxed interpretation.

blocks|key|1692160|text|根据我的经验，人们大多使用“带迭代的瀑布”作为一个嘲讽的术语来描述糟糕的或半心半意的敏捷实现，而不是作为一种实用的方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1692161|无论如何，我遇到了这篇文章，它对“迭代瀑布”这个术语有一个很好的解释。|offset|length|entityMap|0|LINK|mutability|MUTABLE|url|http://agile101.net/2009/09/08/the-difference-between-waterfall-iterative-waterfall-scrum-and-lean-in-pictures/^0|0|9|4|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]]|F|$G|$5|H|I|J|A|$K|L]]]]

From what I have experienced, people mostly use "waterfall with iterations' as a derisive term for poor or half-hearted agile implementations and not as a practical methodology.

Anyway I came across <a href="http://agile101.net/2009/09/08/the-difference-between-waterfall-iterative-waterfall-scrum-and-lean-in-pictures/" rel="nofollow">this article</a> which has a decent explanation of the term "Iterative Waterfall".

blocks|key|5428248|text|迭代瀑布还意味着简单地在里程碑中分解大型项目，并将每个里程碑称为“迭代”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5428249|当然，这样做是罪恶的，因为它消除了以前迭代到下一个迭代中的所有审查或反馈的可能性。然而，我看到了它的应用，在此之后，他们的传声机高声宣布，他们现在是敏捷这样做的!！|5428250|迭代瀑布的另一个定义是有连续的瀑布，其中下一个瀑布是从前一个瀑布开始的。同样，在从设计到交付的循环过程中，没有任何反馈，但只有在交付和设计之间才允许反馈。这个定义似乎与DPD提供的链接相匹配。|5428251|我个人对“瀑布”风格和“敏捷”风格过程的定义在于如何看待和分解项目。两者都涵盖了相同的阶段和过程，但以一种非常不同的方式处理它们。如果您将软件的生产看作是一个堆栈，它的顶部是初始空间，底层是部署和支持。|5428252|瀑布将打破软件的创建过程水平和遍历每一层的顺序。对于一个瀑布主义者(如果可以说是这样的话)，如果没有完全计算出上面的一层，就不可能进入下一层，这是不可思议的。典型的论点是，你永远不会在地基前建造房屋的屋顶，你会说一些类似于“两次测量但一次切割”的话。|5428253|另一方面，敏捷将垂直分解创建过程，产生一段时间后添加到产品中的功能片段。然而，对于每个切片，它们不会从上到下遍历堆栈，而是一次性处理。他们之所以能够做到这一点，是因为他们自愿地缩小了目标结果的范围。对他们来说，如果不先进行测试，看看这个想法是否有意义，那是不可想象的。每次迭代时，他们都会添加一些功能，并根据想法和系统的其他部分对其进行测试。|5428254|瀑布是植根于工程中的，目标是有形的现实生活产物，错误是不可容许的。他们将软件视为必须组装成结构的刚性钢和混凝土块。因此，他们往往过于谨慎，周密地计划每件事，把资源浪费在完美的祭坛上。要使瀑布工作，你需要非常强大的经验丰富的球员和对他们的完全信任，你需要在每一步的道路上格外细致地预见到可能的情况和预期。|5428255|敏捷植根于科学过程，在这个过程中，知识一次收集一点，并不断地测试。他们完全理解软件是可锻铸的，可以随意弯曲和成形。他们对待思想就像研究人员对待一个理论一样，也就是说，只要它与测试一致，它就能站得住脚。因此，他们将倾向于不断地重塑他们的系统，浪费资源，一次又一次地重新创建相同的东西，稍微扭曲一下以适应新的变量。对于敏捷工作，您需要持续评估您的系统作为一个整体，并把它与新的现实。测量和自动化是必不可少的，以便获得当前最精确的图像，从而可以将下一步作为通向理想路径的校正措施。即使是理想的路径也需要重新评估，以确保它确实指向理想的目标。|5428256|瀑布建造软件以持续不变，静态，设置在混凝土中.|5428257|敏捷成长软件，关心和照顾它到一个不断变化的世界。|5428258|诚然，软件在早期是可锻铸的，但是随着它的尺寸和年龄的增长，它的刚度也越来越大，抵抗变化的能力也越来越强。在我看来，没有灵丹妙药，往往有更多的宗教信仰，而不利于理性思考。说到这两个极端，敏捷似乎是考虑到软件的软。|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|12|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|13|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|14|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|15|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|16|8|@]|9|@]|A|$]]]|V|$]]

Iterative Waterfall could also mean to simple break down a large projects in milestones and call each milestone an "iteration".

To do this of course is sin since it removes all possibility of review or feedback from previous iterations into the next. Yet I have seen it applied after which their protractors proclaimed high and loud they were now Agile for doing so !!

Another definition of iterative waterfall is to have successive waterfalls where the next feeds from the previous. Again no feedback during the cycle itself from design to delivery but only between delivery and design is feedback allowed. This definition seems to match the link provided by DPD.

My personal definition of "Waterfall" style and "Agile" style processes lies in how the project is viewed and broken down. Both pretty much cover the same phases and though processes but tackle them in a much different way. If you view the production of a software as a stack with Inception at the top and deployment and support at the bottom. 

Waterfall will break down the software creation process horizontally and traverse each layer in sequence. For a waterfallist (if such thing can be said) proceeding to the next layer is impossible without having completely worked out the layer above, its just inconceivable. Typical argument would be that you never build the roof of a house before the foundation and will say things akin to "measure twice but cut once".

Agile on the other hand will break down the creation process vertically producing slices of functionality that get added to the product over time. with each slices however they do not proceed through the stack from top to bottom but tackle it all at once. They are able to do this because they have willingly reduced the scope of the target result. To them it is inconceivable to proceed without testing first to see if the idea makes sense. With each iterations they add slivers of functionality and test it against the idea and against the rest of the system.

Waterfall is rooted in engineering where the target is a tangible real life product and error is not admissible. They see software as rigid pieces of steel and concrete that must be assembled into a structure. Therefore they will tend to be over cautious planing everything minutely wasting resources on the altar of perfection. For Waterfall to work you need very strong experienced players and a complete trust in them, you need to be extra meticulous at every step of the way in foreseeing what could be and anticipating.

Agile is rooted in the scientific process where knowledge is gathered one bit at a time and tested continuously. They understand perfectly that software is a malleable and can be bent and shaped at will. They treat ideas as would a researcher treat a theory, that is it stands as long as it agrees with the tests. Therefore they will tend to continuously reshape their system wasting resources by recreating the same things over and over each time with a slight twist to fit the new variables. For agile to work you need to continuously evaluate your system as a whole and place it against the new reality. Measurements and automation are essential in order to gain the most accurate picture possible of the present such that the next step can be taken as a corrective measure towards the ideal path. Even the ideal path needs to be re-evaluated to make sure that it does indeed points towards the ideal target.

Waterfall Build software to last as-is, static, set in concrete.

Agile grow software, care and tend for it to an ever changing world.

True that software is malleable early on but as it gains size and age it also gains stiffness resisting changes more and more. In my opinion there is no silver bullet and there tends to be to much religious devotion at the detriment of rational reflection. That said of the two extremes Agile seems to be the one that takes into account the soft of software.

Does anyone know the difference between those two? 

They are both created by iterative approach - giving successive revision after each iteration. They both have the initial idea->analysis->(outline)design phases.

What is the difference between waterfall model with iterations and evolutionary software development model?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

有人知道这两者的区别吗？它们都是通过迭代方法创建的--在每次迭代之后进行连续的修订。它们都有最初的想法->分析->(大纲)设计阶段。

问带迭代的瀑布模型和进化的软件开发模型有什么区别？
EN

回答 4

Software Engineering用户

Software Engineering用户

Software Engineering用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问带迭代的瀑布模型和进化的软件开发模型有什么区别？EN

回答 4

Software Engineering用户

Software Engineering用户

Software Engineering用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问带迭代的瀑布模型和进化的软件开发模型有什么区别？
EN