需求的可追溯性可以清楚地理解什么需要进行测试。
Traceability to requirements for clear understanding of what is being tested.
一个软件构架确定了主要的组件和它们之间的交互作用，两个组件之间的依赖性以及这些组件对于需求的可追溯性。
An architecture identifies the major components and their interactions, the dependencies between components, and traceability from these components to the requirements that they realize.
需求可追溯性是两个需求之间的关系，这两种需求代表了工件之间的源、衍生或者附件。
Requirements traceability is a relationship between two requirements that implies the source, derivation, or dependencies between the artifacts.
产品可追溯性确保产品满足客户的需求。
Product traceability ensures a product satisfies customer requirements.
让我们考虑一下跨多个产品发布版本来维护对需求变化的可追溯性的两种方法。
Let's consider two methods for maintaining traceability of changes to requirements across multiple product releases.
当您在您的测试需求之间设置可追溯性时，您稍后在在这里将会使用RequisitePro工具一起工作。
You'll be working with the RequisitePro tool a little later here, when you set up traceability between your test requirements.
将RequisitePro与其他四个工具中的任何一个相集成，都可以让分析人员、架构师和开发人员维持从需求直接到模型和代码的可追溯性。
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.
这样的双向可追溯性有助于确定所有初始需求已完全实现，并且所有较低级别的需求可以追溯到一个有效的来源上。
Such bidirectional traceability helps determine that all source requirements have been completely addressed and that all lower level requirements can be traced to a valid source.
这样的双向可追溯性有助于确定所有初始需求已完全实现，并且所有较低级别的需求可以追溯到一个有效的来源上。
Such bidirectional traceability helps determine that all source requirements have been completely addressed and that all lower level requirements can be traced to a valid source.
应用推荐