In a development project, many roles are involved who work on different artifacts in different tools:
a formal object in one DOORS module may represent a customer requirement, while a formal object in a different DOORS module may represent a software test case.
With YAKINDU Traceability’s configurative approach, you can specify which engineering artifacts exist, where they reside and how they should be recognized. Furthermore, you can configure whether traceability links should be derived from existing relations or matching attributes of your engineering artifacts and/or if such links should be maintained manually by an engineer. You decide whether to link your tools in a specific context and/or to which extend you want to comply to process standards such as ISO26262, Automotive Spice, DOA178, EN 50128, etc.
YAKINDU Traceability really interacts with your tools. You can navigate between interrelated artifacts or analyze their dependencies with a simple mouse-click. Selections are propagated from engineering tools to YAKINDU Traceability and vice versa. As one of our customer explained to us: “This is real traceability”.
Traceability analysis is only reliable if consistent trace data is given. YAKINDU Traceability supports consistency in several ways:
Better than that, YAKINDU Traceability does not only reveal inconsistencies, it also provides wizards which make your data consistent again.
Traceability is not an end in itself. Instead “traceability supports coverage, consistency and impact analysis” (Automotive SPICE Process Assessment / Reference Model 3.0). As analysis is the purpose, it is supported heavily in YAKINDU Traceability:
You may want to export the traceability data into a relational database. YAKINDU Traceability even provides means to map these data into a pre-existing database scheme and thus is able to populate a custom database.