这样做可以缩短设计、编码和测试周期，并简化维护问题。
Doing so shortens the design, coding, and testing cycle as well as simplifies maintenance issues.
与技术团队成员沟通，以将确定的要求转换为能进行编码和测试的技术规范。
Communication with the technical team members to transform the established requirements into technical specifications that can be coded and tested to.
在危机中，项目一般会取消有计划性的程序，转而去编码和测试。
During a crisis, projects typically abondon planned procedures, and refert to coding and testing.
设计、编码和测试三者之间的鸿沟将不再存在，这样可以促进你对整个环境更好地理解。
The long gaps between the design, coding, and testing phases are gone, thus making for a much better learning environment.
同样，有业务价值的变更也可能因为对现有的需求、设计、编码和测试影响过大而得不偿失。
Similarly, changes that do have business value but would also have great impact on existing requirements, designs, code, and tests may not be worth the effort.
实际上，为了在提供合理性能的同时保留初始的查询语义，我们需要反复地设计、编码和测试。
Indeed, preserving our original query semantics while providing for reasonable performance often required iterative design, coding, and testing.
持续交付的目标，不是要让修正补丁更易于处理，而是要制定出编码和测试的标准，消除对修正补丁的需要。
The goal of continuous delivery is not to make hot fixes easier to handle. The goal is to develop coding and testing standards that eliminate the need for hot fixes.
解决这个问题共花费了我们大约5天时间，再加上他们的开发人员编码和测试成功的新方法又用了10到20天时间。
The total time spent on the problem was approximately five days of our time, plus another 10 to 20 days for their developers to code and test the successful new approach.
因此，让我再简化一下我们要讨论的问题，我们假定我们已经在设计、编码和测试这三者之间取得了合理的平衡。
However, let's again simplify our problem and assume we have reached a reasonable balance of design versus code and test time.
为了决定用PSP支持RUP的时机，我们给那些在整个过程中承担部分任务：设计，编码和测试活动的角色定义了“PSP工具箱”。
To address the opportunity to support the RUP with the PSP, we defined "PSP Toolboxes" for workers whose tasks are part of both processes: those who do design, code, and test activities.
您可以很容易地将这个非常简单的应用程序扩展为一个非常复杂的应用程序，但它们的编码、测试和调试的过程却是相似的。
This very simple application could be easily extended to become a very sophisticated and complex one, though the process to code, test and debug it would be similar.
一个开发者团队会在工作中使用大量的工具来编码、测试、部署、设定工作优先级和交流。
A team of developers typically use a lot of tools in their work for coding, testing, deploying, prioritizing work, and communicating.
软件开发生命周期的设计和编码阶段，为单元测试的质量检验关提供了一个机会。
The design and coding phase of your software development lifecycle offers an opportunity for a quality gate designed around unit testing.
如果能将它们解耦，会更加易于编码、测试和维护。
If you can decouple them, you can more easily code, test, and maintain them.
软件QA团队花时间进行调查研究、测试设计、编码、分解、调试、执行和分析。
A software QA team typically spends time performing research and investigation, test design, coding, refactoring, debugging, execution, and analysis.
XP体现了短迭代、成对编程和编码前测试等概念。
XP encompasses concepts such as short iterations, pair programming, and test before coding.
IDE提供了语法的完整性检查、修正了小错误并提供了增量编译以便更快地完成编码、编译、部署和测试这样的周期。
The ide gives him syntax completion, fixes trivial errors, and provides incremental compilation for a quicker cycle between coding, compiling, deploying, and testing.
测试、编码、迭代，和量度。
需要使开发团队避免对子系统进行修改，他们需要在SDLC的编码和单元测试阶段依赖这些子系统。
The need to insulate development teams from changes that occur to subsystems that they depend on during the code and unit test phase of the SDLC.
Jython会是一个非常方便的补充，对于快速检查和构造原型、测试以及处理那些比较适合使用其方法的编码任务是很有用的。
Jython can be a very handy supplement, useful for quick inspection and prototyping, testing, and for handling a selection of coding tasks for which its approach is better suited.
架构之外的生命周期阶段——需求；编码；测试；未来技术；工具和技术的选择。
Life-cycle phases other than architecture - Requirements, Coding, Testing, Future technologies, Tools and technology selection.
在一边的任务是需求（Requirements，R）、设计（Design，D）、编码（Code，C）和测试（Test，T）。
The roles down the side are Requirements (R), Design (D), Code (C), and Test (T).
比如，假设一个Base-4编码的MPEG要对内嵌的校验和进行测试。
For example, imagine a Base-64-encoded MPEG that's tested against an embedded check sum.
因此，我所测试的目标是Perl的Unicode (utf - 8编码)的读取、解释和处理能力。
Therefore, the tests I ran target Perl's Unicode (in the UTF-8 encoding) reading, interpreting, and manipulating abilities.
敏捷的开发周期允许系统测试团队扮演实际的客户，从应用程序设计到系统测试应用程序的编码和单元测试。
The agile development cycle allowed the system test team to act like a real customer, from the application design right through coding and unit testing of the system test application.
对可用功能的交流是至关重要的，因为每个迭代中只有三个星期是执行系统测试应用程序的设计、编码，和单元测试的。
The communication of available functionality was critical since there were only three weeks per iteration to perform system test application design, code, and unit test.
这样做从开发速度上说感觉好像不错，但却只是一个幻象；因为它将有风险和消耗实践的编码工作推到了最后——包括合并、集成与测试等工作。
It gives a nice feeling of speed but can be an illusion since it pushes the risky and time consuming bits to the end - merging and integrating and testing.
由于它们依赖于要进行编码的测试用例、隐藏的接口和多种需要在不同环境中测试的工具，所以这些工具的使用对开发人员常常是有限制的。
Because of their dependence on coded test cases, cryptic interfaces, and the variety of tools necessary to test in different environments, the use of these tools is often limited to developers.
由于它们依赖于要进行编码的测试用例、隐藏的接口和多种需要在不同环境中测试的工具，所以这些工具的使用对开发人员常常是有限制的。
Because of their dependence on coded test cases, cryptic interfaces, and the variety of tools necessary to test in different environments, the use of these tools is often limited to developers.
应用推荐