本文介绍了SDLC的敏捷与螺旋模型的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我相信敏捷不过是Spiral Model的另一种实现。我一直是Spiral的大力支持者(螺旋模型是一种软件开发过程,结合了设计和阶段原型设计的要素,旨在结合自上而下和自下而上的概念的优势)自成立以来就已经看到很多项目在不知道它们在Spiral世界中运行的情况下实现了Spiral。自从敏捷开始流行的那一天起,螺旋的概念就开始被忽略了。我相信对于复杂的项目,螺旋仍然是最好的选择,但我想更好地了解敏捷和螺旋技术之间的异同。谁能解释他们的差异/相似之处?

I believe that Agile is nothing but another implementation of Spiral Model. I am a big supporter of Spiral (The spiral model is a software development process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts) since its beginnings and have seen that lot of projects implement Spiral without knowing that they are operating in a Spiral world. Since the day Agile started gaining popularity the concept of spiral started getting overlooked a little bit. I am sure that for complex projects spiral is still the best alternative but I would like to get a better understanding of the similarities and differences between Agile and Spiral techniques. Can anyone explain their differences/similarities?

推荐答案

敏捷。完全。

问题是螺旋形倾向于暗示预先大设计,即您计划许多螺旋形,每个螺旋形都有为了风险。但是,螺旋式不是敏捷-而是按照风险顺序递增执行。

The problem is that spiral tends to imply "big design up front" -- where you plan out many spirals, each in order of risk. Spiral, however, isn't Agile -- it's just incremental execution in order of risk.

敏捷添加的一个主要区别是不要过度规划可以做的事情还不知道。
敏捷螺旋式的,但是您每次只创建一个 增量的详细计划。

One big distinction that Agile adds is the "don't overplan things you can't know yet."Agile is spiral, but you create detailed plans for just one increment at a time.

敏捷也添加了很多其他东西。螺旋是一种非常技术性的方法。但是,敏捷认识到技术是人为创造的。 具有四个原则,这些原则超越了Boehm的简单风险管理方法。

Agile adds a lot of other things, also. Spiral is a very technical approach. Agile, however, recognizes that technology is built by people. The Agile Manifesto has four principles that are above and beyond the Boehm's simple risk management approach.

这篇关于SDLC的敏捷与螺旋模型的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-14 02:24