However, because it was created under the presumption that it would be thrown away, it bypassed requirements reviews, design reviews, code reviews, and unit testing.
然而，由于它是在假设会被抛弃的情况下建立的，它会迂回于需求评审，设计评审，代码评审和单元测试之间。
The limitations often come from the existing code base or from customer requirements.
限制通常来自于现有的代码库或来自于客户需求。
It is foolish to think that one type of requirement will satisfy every stakeholder or that it will be easy to keep requirements synchronized with the code.
认为一种类型的需求可以满足每个涉众，或者认为可以很容易地使代码和需求保持同步是很愚蠢的。
Using other tools requires the developer to understand the tooling requirements when they start to write code.
如果使用其他工具，在开始编写代码之前，开发者需要先理解工具要求。
Often, once customers move an application from development to deployment, they start to consider the long-term support requirements for the underlying code (including the application server).
通常，一旦客户将应用程序从开发转至部署，他们就开始考虑基础代码（包括应用服务器）的长期支持需求。
The ability to capture such requirements in a single code module, improving traceability.
在单个代码模块中捕捉这样需求的能力，提升可追踪能力。
They are fully connected and traceable throughout all the lifecycle artifacts, including requirements, test cases, and code.
在整个生命周期的工件中，它们是完全连接且可追溯的，包括需求、测试案例，和代码。
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.
同样，有业务价值的变更也可能因为对现有的需求、设计、编码和测试影响过大而得不偿失。
We'll be writing less code tomorrow when the requirements change again.
明天，当需求再次改变的时候，我们将书写更少的代码。
You can generate requirements into code and trace the lifecycle, from requirements to design, implementation, and test.
您可以将需求整合到代码中，并追踪从需求到设计到执行到测试的整个生命周期。
The generated code may not always meet exact implementation requirements.
所生成的代码不会总是精确满足实现需求。
Architecture management presents opportunities that can improve the way we design and develop software and in the way we manage change across requirements, design, and code.
架构管理提供了改进设计和开发软件方法和用这种方法管理需求、设计和代码的变更的机会。
In software development, often requirements are seen as inventory, what about the code?
在软件开发中，需求经常被视为库存，那么，代码呢？
The domain expert will edit domain requirements that are then transformed into code.
领域专家会编辑领域需求，这些领域需求接着会转化为代码。
The tests relfect the traceability of the requirements because they execute specific code that implements the requirments.
测试反映了对需求的追踪，因为它们要执行特定代码以实现需求。
Given that the requirements of your code do not change, you should not find the need to change code significantly.
假定您的代码要求不变，您将不会明显地发现更改代码的需要。
Technology doesn't require fanciful wish lists of requirements; it just requires code.
技术并不需要想像的需求列表，仅仅需要代码而已。
Pay attention to how clients and domain experts communicate their requirements and focus on capturing those requirements with executable code.
留意观察客户和领域专家如何沟通他们的需求，并且专注于使用可执行的代码来捕捉这些需求。
This means that artifacts for review (requirements, design, code, software assets) can be assigned electronically to a reviewer, and their comments captured and implemented in a simple fashion.
这意味着评审的工件（需求，设计，代码，软件资源）可以分配给评审员，而他们的评论会按照简单的方式被获取和实施。
Requirements management tools, source code management, and version control software have had good support for multiple users for years.
需求管理工具、源代码管理和版本控制软件对多用户的支持已经有很多年了。
The Engineering stage is characterized by much churn regarding all aspects of the project, such as plans, requirements, architecture, and code.
工程阶段表现为项目所有方面的混合，例如：计划、需求、体系结构和代码。
There is limited traceability between requirements, design, and code and test requirements.
需求、设计以及代码和测试需求之间的可跟踪性非常有限。
Bridging the gap between requirements and code with a design model is critical; it catches mistakes and faulty assumptions long before development and testing.
使用设计模型来连接在需求和代码之间的鸿沟是重要的；设计模型可以在开发和测试之前很久捕获错误和有问题的假设。
Configurability gives us the ability to adapt a component to different requirements without changing the code base (writing code).
可配置性为我们提供在不更改代码库(编写代码)的情况下使组件适应不同需求的能力。
If they understand the requirements, design, and code, they can turn that understanding into crafty tests.
如果他们能够理解需求、设计和代码，他们就可以根据他们的理解设计出巧妙的测试用例。
We can read the requirements specification and the code and do a very good job of ensuring that the implementation is correct.
我们可以阅读需求规约和代码，并能够很好地保证实现是正确的。
Make a list of requirements for an iteration, and write only the code that supports those requirements.
列出迭代的需求清单，只编写支持这些需求的代码。
In addition, by tracing from high-level to low-level requirements and on to design, code, and test, you can easily see the impact of a requirements change.
此外，从高层次向低层次追踪需求，追到设计、编码、测试，你很容易看到需求变更的影响。
Agile projects require true generalists as testers: people who have requirements -, design -, and code-understanding skills.
敏捷项目需要真正的多面手来担当测试人员：拥有能读懂需求、设计和代码的技能的人。
Requirements for generating AWS code.
生成aws代码的要求。
应用推荐