1·Overly-detailed design documentation.
过度详细的设计文档。
2·Don't forget to update that design documentation.
不要忘记更新设计文档。
3·Produce complete design documentation before starting to code
开始编写代码之前生成完整的设计文档
4·Begin by looking at your design documentation: Is it up to date?
从查看您的设计文档开始：它是否需要更新？
5·Architecture and design documentation for the LMS was created, specifically.
创建了LMS架构和设计文档，具体如下。
6·Engineering Department - Design documentation, nuclear engineering standards.
工程部-设计文件的编制和核工程标准。
7·Personnel approving design documentation shall be degree qualified in a relevant discipline.
设计文件核准人员，必须具有相关专业的学位。
8·This is based on SQL and VC prepared by the long-distance passenger booking system design documentation.
这个是基于SQL和VC编写的长途客运订票系统的设计文档。
9·You can always build design documentation that helps you do your job, but your focus should always be on delivering working code.
您通常可以构建有助于完成工作的设计文档，但您应该把重点一直放在交付工作代码上。
10·This style of testing has dual purposes: testing your implementation, and building requirements design documentation as you test.
这种风格的测试具有双重作用：测试实现并在测试的同时构建需求设计文档。