Traceability is a team effort.
追溯是团队工作。
为什么我们想要追溯？
Figure 1: Traceability dimensions.
图1：追溯关系维度。
Traceability serves two key goals.
追溯有两个重要的目标。
Traceability and Auditability is key.
可跟踪性和可审核性是关键。
什么是可追溯性？
What is the benefit of having traceability?
拥有追溯关系的好处是什么？
What are the prerequisites for traceability?
用于追溯的必备条件是什么？
Software Development Plan traceability tree.
软件开发计划可追溯树。
Traceability and impact analysis capabilities
可追溯性和影响分析能力
Adjust and revisit your traceability strategy.
调整并重新访问您的追溯策略。
Apply quality assurance to traceability as well.
对追溯性应用质量保证。
This provides traceability linkage in this phase.
这提供了这个阶段的可追溯性链接。
In most cases, traceability is handled explicitly.
在大多数情况下，追溯关系被显式地处理。
In either case, full traceability is maintained.
无论是哪一种情况，都将维持全面的追踪。
This enables better traceability of the change sets.
这样使变更设置有更好的跟踪性。
Traceability queries, instructions, and examples follow.
追溯性请求，指令，以及跟随的例子。
Visualize and report on your traceability (see Figure 3).
可视化并报告您的追溯(参见图3)。
This makes Option 3 the most desirable traceability approach.
这使得选择3成为最令人期待的追溯方法。
Leverage your requirements structure to support traceability.
利用您的需求结构来支持追溯性。
The logging pattern provides service invocation traceability.
日志记录模式提供服务调用可跟踪性。
Excessive traceability must be supported by business value.
过多的跟踪性必须由业务价值支持。
Traceability is improved at a business policy and rule level.
可跟踪性在业务策略和规则层面上得到改进。
Traceability should never drive the way you document requirements.
追溯性不应该驱动您编制需求的方法。
Traceability and Auditability can be achieved in a unified manner.
可跟踪性和可审核可以以一种统一的方式实现。
A traceability solution has significant security requirements.
可跟踪性解决方案有严格的安全性需求。
Let's start with some of the theory behind requirements traceability.
让我们从一些需求追溯关系背后的理论开始。
Product traceability ensures a product satisfies customer requirements.
产品可追溯性确保产品满足客户的需求。
Traceability among information elements is either limited or non-existent.
信息要素之间的可追溯性是受限的，或不存在的。
Include establishing traceability as part of documenting the requirements.
包括将追溯性建立为需求编制的一部分。
应用推荐