The implementation of these methods depends on the requirements of your application.
这些方法的实现依赖于您的应用程序的需求。
Implementation of Task 2 depends on your application requirements.
任务2的实现取决于您的应用程序需求。
The distribution of work shifts from requirements analysis to design to implementation, testing, and deployment as the phases progress.
随着阶段的过渡，工作的分布从需求分析逐渐转移到实现的设计、测试和部署。
In each iteration, you do some requirements, design, implementation, and testing of your application, thus producing a deliverable that is one step closer to the final solution.
在每次迭代中，你完成一些需求，设计，实现，和对你的应用程序的测试，因此产生了一个距最终方案更进一步的发布。
In each iteration you evolve the requirements, analysis, design, implementation, and test assets.
在每个迭代中，您演进需求、分析、设计、实现，及测试资产。
We will use the main disciplines of requirements, analysis and design, implementation, and test as our framework for comparison.
我们将会用需求，分析，设计，实施和测试等主要阶段作为我们比较的框架。
New requirements or constraints are discovered during implementation.
新需求或约束是在实现期间被发现的。
Support impact analysis of changes by identifying affected requirements, design, and implementation artifacts as well as their related tests.
支持变更的影响分析，确认出受影响的需求、设计，及实现工件，以及相关的测试。
This style of testing has dual purposes: testing your implementation, and building requirements design documentation as you test.
这种风格的测试具有双重作用：测试实现并在测试的同时构建需求设计文档。
It then becomes important to maintain reference links between the requirements and implementation artifacts.
因此，在需求工件和实现工件之间维护引用链接是很重要的。
The "Verification" traceability traces requirements, analysis and implementation work products to their respective tests.
“验证”追溯将需求、分析及实现的工作产品追溯到各自的测试。
Businesses with specific deployment domain and implementation domain requirements can adapt this transformation to suit their needs.
具有特定配置域和执行域需求的业务，能够适应这一转换来满足它们的需要。
You can generate requirements into code and trace the lifecycle, from requirements to design, implementation, and test.
您可以将需求整合到代码中，并追踪从需求到设计到执行到测试的整个生命周期。
Rather than having everybody doing requirements for three months, you will in each iteration do a little requirements, architecture, design, implementation, and testing.
与其让每个人做三个月的需求，不如您在每个迭代中做一点需求、架构、设计、实现，和测试。
They also had no means to measure rework and could not differentiate between requirements churn and implementation issues.
它们也没有办法度量返工，并且不能辨别需求波动和实现问题。
A review of security requirements and implementation is an important part of this stage of the assessment.
对安全需求和实现的检查是这一阶段评估的重要部分。
This typically includes identifying and documenting the architecturally significant aspects of the system, including requirements, design, implementation, and deployment views of the system.
这通常包括标识和说明系统在体系结构上的重要方面，包括系统需求、设计、实现和部署视图。
This need to keep requirements, design, and implementation in sync has always been a challenge, and is only exasperated in the context of GDD.
保持需求、设计和实现同步的这一需要已经成为一个挑战，并且只在GDD的环境系中触及。
As with any implementation, the requirements should be scoped before deciding on a strategy, followed by thorough testing.
对于任何实施，在决定策略前都要考虑需求，然后是彻底的测试。
This provides key traceability between the requirements and their implementation dependency on external systems.
这可提供需求及其对外部系统的实现依赖关系间的关键可跟踪性。
Each iteration includes requirements, analysis, design, implementation and testing activities.
每一个迭代都包括需求、分析、设计、实现和测试活动。
Once you have the business requirements (discussed in Part 2), the SLAs, and the OLAs, you can begin to come up with your implementation and deployment requirements.
一旦您拥有了业务需求(在第2部分讨论)、sla以及ola，您就可以开始您的实现和部署需求。
The fact that ASDI was evaluating this proof-of-concept system as a real-world system and finding so few flaws in our implementation of requirements was a strong victory for us.
ASDI的实际情况是将这个概念验证的系统当作真实世界的系统来评估，并且我们对需求的实现上只发现了少数的问题对我们来说是一个巨大的胜利。
An exception-toss error condition is really an implementation requirement (see below) and should be listed in the "Requirements" or "implementation notes" sections.
异常抛出错误条件实际上是实现需求(见以下部分)，应该在“需求”或“实现注意事项”部分中列出。
Implementation of some requirements before all others are described in full detail allows for gradual and more effective distribution of labor, resulting in improved efficiency and reduced costs.
一些需求的实现在其它需求详细描述之前实现，这允许渐进的更有效的分配人力，从而提高了工作效率，并降低了成本。
The type of implementation depends on the business and environmental requirements of the application.
这类实现依赖于应用程序的业务和环境要求。
Unless you have specific requirements that force a BMP implementation, CMP is the better choice.
除非确实有强制BMP实现的特定需求，否则CMP是更好的选择。
This implementation covers the requirements of most applications, which can save you time in developing most application-specific functions.
此实现涵盖大多数应用程序的需求，可以让您在开发大多数应用程序特定的功能时节省宝贵的时间。
However, the implementation varies according to different application requirements and environments.
然而，实现将随应用程序的需求和环境的不同而变化。
Over time, the OTMPS executives or owners will introduce new requirements on the OTMPS implementation.
那时，OTMPS执行者或所有者可能对otmps实现提出新的需求。
应用推荐