然后将目标作为新的输入来添加、删除或转换为可实现的需求，并在框架中重复执行验证和风险缓解过程。
Then you add, delete, and change goals as new inputs into implementable requirements, and repeat the validation and risk mitigation processes in the framework.
高级技术将帮助他们按照一种最大化用例可理解性的方式来结构化他们的需求，并在用例编写方面减少重复。
The advanced techniques will help them structure their requirements in a way that maximizes understandability of their use cases, and reduces repetition in use-case writing.
接下来是迭代计划、执行和结束，根据项目的需求，这些步骤可能会重复多次。最后是迭代后计划和发布。
Then we have an iteration plan, execution, and wrap-up which may be repeated over and again depending on the requirement of the project (followed by a post-iteration plan and finally a release).
当通过重复地应用模式和转换以确定最佳匹配来验证解决方案满足非功能需求时，该方法是有价值的。
This approach is valuable when verifying that the solution meets nonfunctional requirements, where you repeatedly apply patterns and transformations to identify the best match.
这将引入对聚合的需求，并且在这种情况需要使用嵌套聚合。因为批处理请求消息是以分店为基础重复的，然后以订单为基础重复。
This introduces the need for aggregation, and in this case nested aggregation, because the batch request message is repeated on an outlet basis and then repeated on an order basis.
没有哪个资源可以包含所有一切，但这里所列的全体站点能够防止您做重复的工作，或者甚至能够防止您完全放弃需求。
No single resource covers the entire universe, but collectively the sites I list here can save you from reinvention, or even giving up on a need altogether.
因为用户关心这些未捕获的需求，所以他们通常会促使门户开发团队对门户进行许多重复修改。
Because the users care about these non-captured requirements, they will usually force the portal development team to make many iterations of changes to the portal.
项目团队会重复地评审和更新评价过程，以交付项目的需求基线。
The project team will also review and update the assessment iteratively to deliver the requirements baseline for the project.
COE对创建服务和需要使用这些服务的团队进行协调，以确保满足相关的需求，并避免重复工作。
The COE coordinates the teams that are creating and requiring services, to make sure needs are being met and to avoid duplicate effort.
COE对创建服务和需要使用这些服务的团队进行协调，以确保满足相关需求，并避免重复工作。
The COE coordinates the teams that are creating and requiring services to make sure needs are being met and to avoid duplicating efforts.
以实现为中心的方法包括对实现方法的重复增强，它基于技术需求，且在大部分情况下基于变化的业务需求。
The implementation-centric approach consists of the repeated enhancement of implementation artifacts based on technical requirements and, in many cases, on changing business requirements.
重复上述的步骤以联系其他的需求类型，例如BUS(业务用户事例)与SUS(系统用户事例)等等。
Repeat these steps to associate other requirement types, such as BUS (Business User Stories) and SUS (System User Stories), etc.
团队仍然履行一个需求周期，以将CWN 细化为 BR和SR、划分优先级、ROM、LOE 和初步规模估计、添加新需求，以及重复地循环。
The team still went through a requirements cycle of refining CWNs to BRs and SRs, prioritizing, ROM, LOE, and low-level sizings, adding new requirements, and circling around repeatedly.
如果您有想要定义的多个项目，重复以上的步骤直到所有想要的需求和需求类型都导入到RationalRequirementsComposer中。
If you have multiple projects that you want to define, repeat the previous step until all desired requirements and requirement types are imported to Rational requirements Composer.
我们把大众市场（mass market）与质量和需求等同起来，而事实上，它只不过代表了千篇一律的重复性、狂轰乱炸的广告效应以及泛泛而肤浅的诉求。
We equate mass market with quality and demand, when in fact it often just represents familiarity, savvy advertising, and broad if somewhat shallow appeal.
MDA的可重复的实践集是适合当今迭代开的发需求的，因为MDA提高了开发过程和要交付的解决方案本身的可预见性。
MDA's repeatable set of practices is well-suited to today's iterative development requirements, because MDA enhances predictability of the development process and the delivered solution itself.
否则，只能是一个错误，当所有需求都满足之后，确保用户名不和数据库中现有的用户名重复，如果是重复了，也是返回一个错误。
Otherwise, you'll simply get an error. When all the requirements are met, make sure that the user name does not already exist in the database.
为了满足所有位置的团队成员的需求，自动化的同步为重复的缺陷和变更跟踪信息提供最新的访问，以使整个团队保持同步。
To address team members at all locations, automatic synchronization provides up-to-date access to replicated defect and change tracking information so the entire team stays in synch.
在本系列文章接下来的部分中，我们将会创建能够满足这些需求的服务规格和执行，能够满足的需求支持未来的重复使用和业务敏捷性。
In follow-on articles in this series, we'll create service specifications and implementations that fulfill those requirements with an architecture that enables future reuse and business agility.
在那之后，在每一周结束的时候，他们都要重复这一过程，并且必须添加新的功能，基于客户需求的优先级完成功能特性。
After that, at the end of each one-week iteration, the teams must demonstrate additional, completely functional features, based upon the customer's priorities.
需求：在一个可重复活动的包装上生产一个工作产品。
Requirement: Produce a work product at the wrap-up of a repeatable activity.
RationalRequisitePro帮助团队管理他们的需求与用例，提高追踪性，降低重复劳动量，并提高软件的质量。
Rational RequisitePro helps teams manage their requirements and use cases, improve traceability, reduce rework, and increase software quality.
未来可能需要已存在的需求、缺陷记录、测试计划以及测试用例，或者需要继续处理，或者需要在Rational QualityManager中重复使用。
Existing requirements, defect records, test plans, and test cases might be required in the future, either for ongoing work or reuse in Rational Quality Manager.
消除了重复和对缺乏定义的概念的说明也是UML2.0另一个重要的需求。
Removing overlapping and the clarification of poorly defined concepts was another important requirement for UML 2.0. The three major areas affected by this requirement were.
通常由该小组定期开会决定任何新需求的优先级和指派(对于系统的发布或者对于在现有开发成果中的重复)。
This group meets regularly to decide on the priority and assignment (either to releases of your system or to iterations within your existing development efforts) of any new requirements.
这些可引起标价错误，造成重复广告宣传所引起的畸形的需求。
These may result in wrong pricing, creation of distorted patterns of demand by repetitive advertising.
在3个实验中探讨了任务需求对基于位置的返回抑制和基于颜色的重复劣势效应的影响。
The effects of task demands on spatial based IOR and color based repetition disadvantage effect were explored in 3 experiments.
如果同一需求重复出现，成功人士会学会尽可能快速地处理。
If a need arises repeatedly, the most successful people learn how to solve it as quickly as they can.
如果同一需求重复出现，成功人士会学会尽可能快速地处理。
If a need arises repeatedly, the most successful people learn how to solve it as quickly as they can.
应用推荐