Traceability should never drive the way you document requirements.
追溯性不应该驱动您编制需求的方法。
Traceability to identify whether all requirements are developed and have test coverage is very important to ensure the quality and completeness of the product delivered.
识别所有的需求是否已被开发以及得到测试覆盖的需求追踪性，对于确保交付产品的质量和完整性非常重要。
Traceability is usually associated with requirements, but we can also benefit from tracking other types of artifacts and relationships.
可跟踪性经常与需求相关联，但是我们也可以通过跟踪其它的类型的产物和关联中受益。
Traceability of requirements through the software development lifecycle is one of the major issues faced by most development project teams.
在整个软件开发生命周期中实现需求的追踪性，是大多数开发项目团队所面临的主要问题之一。
Different projects require different requirements types and/or different relationships defined for traceability.
不同的项目需要不同的需求类型和/或为追溯定义的不同关系。
Traceability back to original requirements to ensure that all requirements have been implemented and tested is at the core of any well governed and efficient software development effort.
回溯到初始需求从而确保所有的需求都被执行和测试，这在任何一支管理良好、运作高效的软件开发团队中都处于核心地位。
Most software development managers would like to have a greater understanding of and better control over their project's requirements traceability functions.
大多数的软件开发管理员都想进一步了解及更好地控制项目的需求可追溯性功能。
The ability to capture such requirements in a single code module, improving traceability.
在单个代码模块中捕捉这样需求的能力，提升可追踪能力。
The following sections focus on the traceability of requirements in terms of the "Validation" traceability concept noted above.
以下部分根据上面提到的“确认”追溯概念介绍需求的追溯关系。
This provides key traceability between the requirements and their implementation dependency on external systems.
这可提供需求及其对外部系统的实现依赖关系间的关键可跟踪性。
Requirements traceability is a relationship between two requirements that implies the source, derivation, or dependencies between the artifacts.
需求可追溯性是两个需求之间的关系，这两种需求代表了工件之间的源、衍生或者附件。
Let's consider two methods for maintaining traceability of changes to requirements across multiple product releases.
让我们考虑一下跨多个产品发布版本来维护对需求变化的可追溯性的两种方法。
Product traceability ensures a product satisfies customer requirements.
产品可追溯性确保产品满足客户的需求。
There is limited traceability between requirements, design, and code and test requirements.
需求、设计以及代码和测试需求之间的可跟踪性非常有限。
In many companies, requirements coverage or requirements traceability is a big focus of the testing process.
在许多公司，需求覆盖或需求可溯性是测试过程的大焦点。
Use cases also offer the opportunity to simplify requirements traceability and to insure more complete test coverage.
用例还提供了简化需求跟踪的机会，从而确保更完整的测试覆盖率。
The latter are key to capturing design decisions and provide traceability for requirements derivation and allocation across system elements.
后者是记录设计决策和和提供需求来源和分配系统元素的追踪关系的关键。
Of course, the model also contains many things not synthesized in code that provide a wider context; such as use cases, traceability to requirements, and other key product artifacts.
当然，模型还包含了许多没有同步化的代码，这些代码提供了一个广阔的背景；例如用例，对需求的追踪性，以及其他关键的产品工件。
Define the business use cases and establish traceability relationships to the requirements (use-case models).
定义业务用例、建立到需求的跟踪关系(用例模型)。
These connections are required for users to create traceability between requirements in the current project and requirements in the external projects.
用户用这些链接点来创建当前项目中的需求和外部项目需求之间的链接点。
The tests relfect the traceability of the requirements because they execute specific code that implements the requirments.
测试反映了对需求的追踪，因为它们要执行特定代码以实现需求。
Users then create traceability links from the model to the requirements, automatically providing traceability, impact analysis and coverage documentation.
接下来用户就可以根据模型创建对需求的跟踪链接，这种链接能自动提供跟踪、影响分析以及覆盖文档等功能。
The RPX can also be used to help maintain traceability between requirements.
RPX也能够用来维护需求之间的可跟踪性。
These nonfunctional requirements are around service performance, service scalability, and traceability.
这些非功能需求与服务性能、服务可伸缩性和可跟踪性相关。
Traceability to requirements for clear understanding of what is being tested.
需求的可追溯性可以清楚地理解什么需要进行测试。
The logical traceability relationship between two requirements — represented by their identifiers — can be physically achieved in various different ways. The most common ones are.
两个需求之间的逻辑追溯关系——由它们的标识符表示——可以通过各种不同的方法来物理地实现。
The integration of RequisitePro with any of these four tools allows Analysts, Architects, and Developers to maintain traceability from requirements directly to models and code.
将RequisitePro与其他四个工具中的任何一个相集成，都可以让分析人员、架构师和开发人员维持从需求直接到模型和代码的可追溯性。
But often, well structured requirements documents support traceability more naturally. For example.
但常常，结构好的需求文档会更容易地支持追溯性。
You'll be working with the RequisitePro tool a little later here, when you set up traceability between your test requirements.
当您在您的测试需求之间设置可追溯性时，您稍后在在这里将会使用RequisitePro工具一起工作。
Full lifecycle traceability from requirements to test cases.
从需求到测试用例更完整的生命周期追溯性。
应用推荐