Refining our use cases to add traceability to the sow.
精练我们的用例以添加可跟踪性到sow。
Artifact traceability to points of accountability in the delivery chain.
针对交付链中重要点的工件可追踪性。
Traceability to requirements for clear understanding of what is being tested.
需求的可追溯性可以清楚地理解什么需要进行测试。
Our use cases were starting to stabilize, to the point where traceability to the SOW would be appropriate.
我们的用例开始稳定了，开始指明在对SOW合适的可跟踪的地点。
There should be traceability to standards (e. g. national, regional or international standards) used in the calibration.
应当有可追溯的校准标准(如国家标准、地区标准或国际标准等)。
It is believed traditionally that specified analysis methods should have a metrological traceability to primary method through reference materials.
习惯上人们认为，特定的分析方法应通过参考物质建立到基准方法的计量溯源性。
Good RM tools provide traceability between requirements; a really good one provides traceability to other tools and artifacts, such as designs and tests.
好的RM工具具有需求间的可追踪性；一个真正好的工具具有与其他工具和工件(如设计和测试)间的可追踪性。
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.
识别所有的需求是否已被开发以及得到测试覆盖的需求追踪性，对于确保交付产品的质量和完整性非常重要。
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.
当然，模型还包含了许多没有同步化的代码，这些代码提供了一个广阔的背景；例如用例，对需求的追踪性，以及其他关键的产品工件。
In addition to Acceleo, Obeo Designer also brings along Obeo Traceability to detect and correct all incoherence and synchronization problems between your application code and your models.
除了Acceleo,Obeo设计器也提供了Obeo可追溯功能，可以用来探测并修正所有你的应用代码和模型之间出现的不一致和同步问题。
Figure 9: the Use-Case Analysis model and its traceability links to the other model elements.
图9：用例分析模型，及其到其他模型元素的可追溯性链接。
The greater implication of the translation from diagram to code is traceability.
从图到代码的转换，其更重要的含义是可跟踪性。
Baselines and package names should be synchronized to support traceability.
基线和包的名字需要同步以支持可跟踪性。
This traceability enables organizations to document that all business goals are being addressed.
这种可追溯性使组织能够归档所有已经实现的业务目标。
Let's consider two methods for maintaining traceability of changes to requirements across multiple product releases.
让我们考虑一下跨多个产品发布版本来维护对需求变化的可追溯性的两种方法。
Leverage your requirements structure to support traceability.
利用您的需求结构来支持追溯性。
Also, you can use the traceability function to determine the impact of changes on requirements.
同样，您可以使用追溯功能确定变更对需求的影响。
Users then create traceability links from the model to the requirements, automatically providing traceability, impact analysis and coverage documentation.
接下来用户就可以根据模型创建对需求的跟踪链接，这种链接能自动提供跟踪、影响分析以及覆盖文档等功能。
Enforce the defined traceability strategy to a certain extent.
在一定程度上执行确定的追溯策略。
Full lifecycle traceability from requirements to test cases.
从需求到测试用例更完整的生命周期追溯性。
For Lesson 2, you create a UML project and an analysis model of use cases from those requirements and establish traceability back to the requirements.
对于课程2，您创建一个UML项目和一个来自那些请求的案例的分析模型，并建立追溯到请求的追溯性。
Being able to walk this traceability tree would be very interesting, because it goes from requirement to code.
能够浏览这些可追溯性树是非常有意思的事，因为它从请求开始一直到代码。
One straightforward approach for maintaining this type of traceability is to add appropriate metadata to both the requirements artifacts and the BRMS artifacts.
维护这种可跟踪性的一种简便方法是，在需求工件和BRMS 工件中添加适当的元数据。
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.
回溯到初始需求从而确保所有的需求都被执行和测试，这在任何一支管理良好、运作高效的软件开发团队中都处于核心地位。
Apply quality assurance to traceability as well.
对追溯性应用质量保证。
Explicit traceability requires you to manually establish a relationship between two requirement types.
明确的追溯要求您手动地建立两个需求类型之间的关系。
After producing all your test cases, you can set traceability from scenarios to test cases.
在产生了全部的测试用例以后，你可以设置从场景到测试用例的追踪。
You also create a design model further refining the use cases with collaborations and UML classes and establish traceability back to the use cases.
您还创建一个设计模型，进一步利用合作精选和UM l类来创建一个设计模型，并建立追溯到用例的追溯性。
Given that the ground rules to establish and maintain traceability are simple, it seems hard to understand why a lot of projects abandon traceability along the way.
已知建立并维护追溯关系的基本法则很简单，那么似乎很难理解的是，为什么大量项目一直放弃追溯。
Use cases also offer the opportunity to simplify requirements traceability and to insure more complete test coverage.
用例还提供了简化需求跟踪的机会，从而确保更完整的测试覆盖率。
应用推荐