第2章为什么瀑布模型会失效？
图1：软件开发生命周期的瀑布模型。
那意味着您在前面做完了所有的需求，正如瀑布模型。
That means you've done all of your requirements up front, just like in a waterfall model.
如果您极端地追求重叠迭代技术，那么您会沿着瀑布模型。
If you pursue the technique of overlapping iterations to the extreme, you will end up at the waterfall model.
通常认为是它论证了瀑布模型，但它实际上刚好相反。
This paper is often cited as if it validates the Waterfall model, but it actually does the opposite.
然而，很多挣值管理的实现都遵循瀑布模型：需求分析、设计、开发、测试和发布。
However, many implementations of EVM follow waterfall models of requirements, design, development, test, release.
本文分析了快速原型方法和面向对象技术相对于传统的瀑布模型的优势。
This paper analyses fast prototype method and object-oriented technology's advantage relative to traditional waterfall model.
由于瀑布模型的特点(文档是主体)，很多的问题在最后才会暴露出来。
Due to the waterfall model features (document is main body), a lot of problems in the final will be exposed.
项目通常是从分析设计开始，即使在开发团队不使用瀑布模型变体的情况下也是这样。
A project usually begins with analysis design, even if the development team isn't using a waterfall variant.
一个单一化的螺旋模型可以被看作每个阶段前都带有风险分析的瀑布模型。
A simplified spiral model is as a waterfall model with each phase preceded by risk analysis.
他的工作解释了如何开发增量的系统、按照风险排列优先级、以及反对使用传统的序列的瀑布模型。
This work explained how to develop systems in small increments, prioritized according to risk, as opposed to using the more traditional sequential, single-pass, waterfall model.
系统采用了基于B/S的三层体系结构，利用瀑布模型即生命周期方法学进行软件开发。
The proposed system design is based on B / S of the three-tier architecture, using waterfall model that is the life cycle methodology developed.
定义一个严格的序列，比如在瀑布模型中，与在并行工作中定义一个半排序的迭代序列是基本相同的。
Defining a strict sequence, as in a waterfall model, is just as much a process as defining a semi-ordered sequence of iterations in parallel work.
这还是敏捷、迭代的方法的宗旨，表现出就风险、成本、质量，和效率而言，在瀑布模型上的重大改善。
It is also a tenet of an agile, iterative methodology, representing a significant improvement over waterfall in terms of risk, cost, quality, and efficiency.
然而，危害已经造成了，由于先入为主形成的习惯，瀑布模型思想已经根深蒂固、积习难改。
However, the damage was done, and a strong mindset with a bias toward Waterfall development had become ingrained.
本文是论题的第一部分，以瀑布模型和快速原型模型为中心。其它模型将在第二部分中讨论。
The first part focuses on waterfall model and rapid prototyping model, and others will be dealt with in the second part.
在1985年，几乎所有明确定义了软件开发生命周期(SDLC)的项目都采用了瀑布模型，如图1所示。
In 1985, almost all projects with a well-defined Software Development Lifecycle (SDLC) used the waterfall model, shown in Figure 1.
瀑布模型经常被认为是更具预见性的，但是不幸的是，这种预见性往往只有在项目的后期阶段才会变成可能。
Waterfall is often touted as being more predictable, but unfortunately the prospect of achieving the predicted result often fails to emerge until the late stages of the project.
从多年尝试瀑布模型的经验中我们得出，我们很少能够事先预知所有的事，试图在一开始就做对是不完美的。
As we know from attempting to use waterfall methodologies for years, we rarely know everything up-front, and our attempts to get it right at first are imperfect.
详细叙述软件生存周期为传统的瀑布模型的软件开发过程的阶段划分、阶段产品和阶段评审内容。
The phase division, phase products and phase review contents for the software exploitation of the traditional cataract model in the software life-cycle are presented in detail.
长治市科技计划网上申报系统的开发方法是以“瀑布模型”框架为主，以“原型法”为辅而研制的新系统。
The online declaration system of sci-tech plan of Changzhi City takes waterfall model as main framework and takes prototyping method to research the system functional modules.
传统的软件工程方法如瀑布模型，存在以下问题1：需求或设计中的错误往往只有到了项目后期才能够被发现。
Traditional software engineering has some disadvantages such as follows 1: defects exist in the requirement and designing only can be found in the late of the project.
他仔细地看了一下像WinstonRoyce这样人的想法如何被误解了，以及Royce后来是如何由于将瀑布模型强行用于产业界而受到了不公正的惩罚。
He looked carefully at how the ideas of people like Winston Royce were misunderstood and how Royce was later unfairly chastised for foisting the waterfall model on the industry.
例如，瀑布，递增，或是迭代模型可以用相同的重叠方法内容建立。
For example, waterfall, incremental, or iterative models can be created with the same overlapping method content.
第一个迭代是过渡的，通常着重于交付在瀑布开发模型下开发了几个月的代码。
The first iteration was a transitional one, mostly focused on delivering code that had been under the waterfall development model for multiple months.
我们甚至可以看到一些产品维护团队在类似瀑布过程模型中使用看板系统。
Now we even see some product maintenance teams utilizing Kanban systems in a waterfall-like process model.
当然是。此处给出的模型是现实世界中维护项目的混合，从瀑布方法提升为敏捷方法。
The model given here is an amalgam of real-world maintenance projects that have shifted from waterfall methodologies to Agile.
在这里，看板系统被用于带有流程的传统瀑布开发模型。
Here, a Kanban system is used in a traditional waterfall development model but with a flow.
这里表现的是产品生命周期里稳定的“持续(sustaining)”阶段，处在带有流程的瀑布状态转换模型的管理之下。
What's happening here is a stable "sustaining" phase in a product's lifecycle, managed in a waterfall state transition model with a flow.
这里表现的是产品生命周期里稳定的“持续(sustaining)”阶段，处在带有流程的瀑布状态转换模型的管理之下。
What's happening here is a stable "sustaining" phase in a product's lifecycle, managed in a waterfall state transition model with a flow.
应用推荐