MDD addresses the problems inherent in document-driven development in several ways.
MDD通过许多方法解决了文档驱动开发中固有的问题。
In fact, several large organizations seem to be moving away from MDD and back towards more traditional document-driven and code-centric approaches.
事实上，许多大型组织似乎离开MDD，而又回到较传统的文档驱动和以代码为中心的方法上去了。
If they have any relevant technical experience at all, it is most likely on projects that used traditional document-driven and code-centric ways of working.
如果他们有相关的技术经验，那么最可能的是关于使用传统的文档驱动及以代码为中心的工作方式的项目。
Studies reveal that using MDD practices can improve productivity by a factor of two to four, compared to traditional document-driven and code-centric development (see Resources).
研究显示，与传统的文档驱动和以代码为中心的开发相比(请参见参考资料)，使用MDD实践可以使工作效率提高两到四倍。
For the last year-and-a-half I've been working on the Spring Web services project, a product from the Spring portfolio focused on creating contract-first, document-driven Web services.
在刚过去的一年半中，我一直在从事SpringWebServices项目，这是SpringPortfolio中的一个产品，专注于创建契约优先、文档驱动的Web Services。
It is developed for documental database, and implements document-driven workflow management.
它面向文档型数据库，实现了文档驱动的工作流管理。
Note that I regard the three most common modeling approaches described above — White Board Sketching, UML by PowerPoint, and Disposable UML — as document-driven development approaches.
注意，我将上面介绍的三种最普遍的建模方法——白板草图、用PowerPoint的UML，和可任意处理的UML——看作文档驱动的开发方法。
In particular, most are still working within a fundamentally document-driven development paradigm that is inefficient and error-prone.
特别是，大多数仍旧工作于效率低且容易出错的文档驱动的开发范型中。
In particular, most are still working within a fundamentally document-driven development paradigm that is inefficient and error-prone.
特别是，大多数仍旧工作于效率低且容易出错的文档驱动的开发范型中。
应用推荐