为什么我们想要追溯？
什么是可追溯性？
What is the benefit of having traceability?
拥有追溯关系的好处是什么？
Figure 6: OR traceability of expectations
图6：期望的OR可溯性
What are the prerequisites for traceability?
用于追溯的必备条件是什么？
Software Development Plan traceability tree.
软件开发计划可追溯树。
In-depth traceability and coverage analysis.
深入的可跟踪性和覆盖率分析。
Apply quality assurance to traceability as well.
对追溯性应用质量保证。
In most cases, traceability is handled explicitly.
在大多数情况下，追溯关系被显式地处理。
In either case, full traceability is maintained.
无论是哪一种情况，都将维持全面的追踪。
Automated traceability, from requirements to design.
从需求到设计，提供了自动化的可跟踪性。
There is a lack of traceability between abstraction layers
抽象层之间缺乏可追溯性
Full audit, traceability, and detailed history of change.
完全审计，跟踪，以及变更的详细历史。
Full lifecycle traceability from requirements to test cases.
从需求到测试用例更完整的生命周期追溯性。
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.
过多的跟踪性必须由业务价值支持。
Now create traceability between these features and use cases.
现在你可以创建这些特性与用例之间的可追溯性。
Enforce the defined traceability strategy to a certain extent.
在一定程度上执行确定的追溯策略。
A traceability solution has significant security requirements.
可跟踪性解决方案有严格的安全性需求。
The systems link with each and provide traceability (Figure 2).
系统相互之间联系起来并提供了追踪性(图2)。
Establish correspondence and traceability between different models.
在不同模型之间建立通讯和可追溯性。
Given a context element, traceability offers these types of queries.
假定一个背景元素，追溯性提供这些查询类型。
Adopt a practice of versioning and traceability for the definitions.
采纳某种版本跟踪实践，实现定义的可追溯性。
Let's start with some of the theory behind requirements traceability.
让我们从一些需求追溯关系背后的理论开始。
Product traceability ensures a product satisfies customer requirements.
产品可追溯性确保产品满足客户的需求。
The second method is traceability into test cases, shown in Figure 14.
第二个方法是测试用例中的追踪，如图14所示。
Include establishing traceability as part of documenting the requirements.
包括将追溯性建立为需求编制的一部分。
Baselines and package names should be synchronized to support traceability.
基线和包的名字需要同步以支持可跟踪性。
应用推荐