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实践可以使工作效率提高两到四倍。
Studies reveal that productivity can improve by a factor of two to four 1 using full-scale "2 MDD practices, compared to traditional document-driven and code-centric development."
研究表明，与传统的文档驱动及以代码为中心的开发相比，利用全面的2mdd实践，可以提高生产力两到四倍1。
MDD addresses the problems inherent in document-driven development in several ways.
MDD通过许多方法解决了文档驱动开发中固有的问题。
In particular, most are still working within a fundamentally document-driven development paradigm that is inefficient and error-prone.
特别是，大多数仍旧工作于效率低且容易出错的文档驱动的开发范型中。
Conventional software testing approaches follow the same document-driven approach that was applied to software development.
传统软件测试方法遵循相同的、应用于软件开发的文档驱动方法。
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——看作文档驱动的开发方法。
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——看作文档驱动的开发方法。
应用推荐