也许您正使用瀑布开发方法，或者您已经采用Agile。
Perhaps you are using waterfall development methods, or perhaps you've adopted Agile.
尽管瀑布开发方法的缺点受到了广泛的批评，但是它仍然非常流行。
Notorious weaknesses in the waterfall development method have been widely criticized, yet the method still remains very popular.
使用瀑布开发方法将会产生大量部分完成的工作，因为大量的时间会花在改善需求和设计之上。
Using the waterfall development approach leads to lots of partially done work, because a lot of time is spent upfront in elaborating requirements and in design.
瀑布开发过程的设计是同时交付所期望的所有能力 ——一种开发中到大型复杂系统的无效方法8 。
Waterfall development processes are designed to deliver all desired capability at the same time — an ineffective approach for developing medium-to-large complex systems 8 .
如果你的项目主要是网络的重新设计或者是一个只有少许软件开发的服务器固化的项目，用传统的瀑布方法也许会更好。
If your project is mainly a network redesign or a server consolidation project with very little software development, you might be better sticking with a traditional waterfall approach.
RMC支持基于不同开发方法的过程，并可用于定义不同的生命周期模型，例如瀑布，递增，或迭代生命周期模型。
RMC supports processes based on different development approaches and can be used to define different lifecycle models such as waterfall, incremental, or iterative lifecycles.
瀑布式开发方法可以很好地工作。
因此，随后的开发方法不是典型的“瀑布”方案，在瀑布方案中，收集需求之后进行分析和设计，并进行系统的实现。
Hence, the development approach that is followed is not the classic "waterfall" scenario, where requirements gathering is followed by analysis and design, leading to the implementation of the system.
然而，使用瀑布型开发方法的执行与想象是相反的：很多设计团队把在阶段1之后的修改设计视为他们的最初设计或者需求过程的失败。
However, that runs counter to the thinking behind the waterfall approach: Many design teams would view modifying the design after Stage 1 as a failure of their initial design or requirements process.
请记住，需要对项目活动进行迭代；传统的瀑布式系统开发方法的风险经常要高得多，特别对于大型的复杂项目更是如此。
Keep in mind that the project activities need to be iterative; the traditional waterfall approach to system development is prone to much higher risk, especially for large and complex projects.
虽然一个改进的瀑布型开发方法并不排除反馈的使用，但是它并没有促进、支持和鼓励反馈的使用。
And although a modified waterfall approach does not preclude the use of feedback, it does not facilitate, accommodate, or encourage it.
顺序开发(例如瀑布开发模式)的问题是，它强制设计人员采用深度优先而非广度优先方法。
The problem with sequential development (for example, waterfall) is that it forces designers to take a depth-first rather than a breadth-first approach.
以及这些对于预算意味着什么？可以对敏捷开发作出这些重要的评估，但是这种思考方式与您在瀑布式方法中的思考方式不同。
These important types of assessments can be made with agile development, but it’s a different way of thinking than you might be used to with waterfall methodologies.
最后，想要最小化风险就不要使用一个典型瀑布型方法来驱动开发项目。
And finally, the desire to minimize risk does not typically drive a waterfall project.
与ASDI唯一棘手的问题是他们最初预期项目应该严格的按照瀑布型的开发方法进行。
The only tricky issue with ASDI had been their initial perception that the project should be undertaken according to a strict waterfall-type approach.
当我们将项目开发从瀑布法转到RUP方法时，有许多支持项目和子项目也在同时进行。
On all of our projects that were going from waterfall to RUP, there were a number of supporting projects and subprojects going on concurrently.
避免瀑布式开发方法。
相反，工作在瀑布型开发方法中的开发人员典型的被限制在狭窄的技术专长上，并且仅仅有机会从事设计、编码或者测试之一方面的工作。
In contrast, those working on waterfall projects are typically confined to narrow specialties and have only one shot at design, coding, or testing.
实际上，多数的开发团队使用了改进的瀑布型开发方法，他们将项目分解成为两个或者更多的部分，有时这些部分被称为阶段或者是时期。
In practice, most teams use a modified waterfall approach, breaking the project down into two or more parts, sometimes called phases or stages.
瀑布式方法是其中第一个这样被定义的系统开发过程。
The Waterfall methodology was one of the first such defined system development processes.
迭代软件开发项目的评估活动与瀑布方法的主要不同之处是。
The key differences in estimation activities on an iterative software development project versus one governed by a waterfall approach are.
下面的图片使用瀑布式方法、螺旋型方法或迭代过程中的任何一种方法来描述当前开发环境。
The following graph demonstrates the current development environment, using any of the Waterfall, Spiral or Iterative processes.
后来，美国国防部意识到瀑布方法是行不通的，并最终于1994年发布了取代DOD-STD - 2167的标准MIL - STD - 498，支持迭代式开发。
Eventually, the DOD realized that the Waterfall method was not working and in 1994 replaced DOD-STD-2167 with MIL-STD-498, which supports iterative development.
长治市科技计划网上申报系统的开发方法是以“瀑布模型”框架为主，以“原型法”为辅而研制的新系统。
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.
系统采用了基于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.
顺序开发（例如瀑布开发模式）的问题是，它强制设计人员采用深度优先而非广度优先方法。
The problem with sequential development (for example, waterfall) is that it forces designers to take a depth-first rather than a breadth -first approach.
顺序开发（例如瀑布开发模式）的问题是，它强制设计人员采用深度优先而非广度优先方法。
The problem with sequential development (for example, waterfall) is that it forces designers to take a depth-first rather than a breadth -first approach.
应用推荐