服务模型的重构是无法避免的，并且在敏捷软件开发中，我们鼓励进行持续重构。
The refactoring of the service model cannot be avoided, and as in agile software development, we encourage such continuous refactoring.
作为敏捷开发的身体力行者，我强烈建议你只对有长期价值的模型使用建模工具。
As a practitioner of agile development, I highly recommend that you use a modeling tool only for models that have long-term value.
因为我们采用了服务模型，我们准备将敏捷软件开发扩展到SOA级别！
As we have the service model, we are ready to extend agile software development to the SOA level!
对于敏捷开发，开发人员团队在一定的时间期限内完成大量力所能及的事情，该时间期限支持基于时间的支付模型。
With agile development, a team of developers does as much as they can in a certain time frame, which supports a time-based payment model.
服务模型成为SOA中进行敏捷开发的基本工具，因为没有该工具，就很难控制服务重构。
The model of services becomes an essential tool for agile development in a SOA, because without it, it is very hard to control service refactoring.
敏捷模型的一个关键特征是开发过程应该演进。
One key characteristic of the agile model was that the development process was expected to evolve.
如果客户习惯于以固定价格的模型购买开发工作，或者具有正式的指导原则，则采用敏捷开发流程对客户来说是非常大——甚至不可能——的更改。
If the customer is used to buying development with a fixed price model, or has formal guidelines, it can be quite a big-or even impossible-change for the customer.
为了帮助开发人员将精益和敏捷实践应用到大型项目之中，在自己的书和博客上，Leffingwell已经研究出了一系列模型和元模型。
In both his book and blog, Leffingwell has developed a set of models and meta-models to assist developers in the application of Lean and Agile practices to large scale projects.
另外，像敏捷及scrum之类的更新一点的开发模型，假设“持续性构建”—早期运行及经常运行的构建——是标准的开发程序。
In addition, newer development models such as agile and scrum, assume that "continuous builds" - builds that are run early and often — are the standard development procedure.
另外，像敏捷及scrum之类的更新一点的开发模型，假设“持续性构建”—早期运行及经常运行的构建——是标准的开发程序。
In addition, newer development models such as agile and scrum, assume that "continuous builds" - builds that are run early and often — are the standard development procedure.
应用推荐