BRACE Automotive is specialized in development and engineering of vehicle systems. For their software development process (based on powertrain ECU software development) and the accompanying toolchain an easy-to-use traceablity tool was necessary.
As PTC Integrity (former known as MKS) was already pre-selected as an application lifecycle management tool, the easiest solution seemed to be to use the PTC Integrity traceability tool. Unfortunately the reality was not as easy at all.
In PTC Integrity all toolchain elements can only be stored in two “tools”: Workflow & Documents” (WF&D) or “Sources” – not enough for the complexity of modern day development toolchains. Though PTC Integrity offers solutions for some tools such as Enterprise Architect, these are expensive and time intensive. For other tools, such as Autosar, there are no such solutions.
Furthermore it was difficult to reach the desired granularity of traceability to certain file types, such as excel, source files and other non-WF&D documents. Integrity allows only traces to source on a file level for example and not down to specific functions or other elements in the source code.
After careful consideration itemis’ YAKINDU Traceability was chosen as the preferred solution. The main reasons were the combination of completeness of traceability vs costs. While PTC’s offered solution would probably have been able to achieve a similar result on the main requirements, the costs of realization was a factor 2 higher.
Furthermore the ease of navigation through traceability trees, the visualization options and the flexibility of the reporting that YAKINDU Traceability offered were impressing. The non-intrusive nature of the tool means that the database does not get inflated, even though the amount of elements that are available for tracing is much higher than in other offered solutions. Connectors to PTC Integrity that allow to show all existing traces in Integrity seamlessly in YAKINDU Traceability were provided.
Thus the already existing relationship structure in Integrity was safeguarded. Furthermore the tool has a good usability: Users were able to work with it after just a short introduction.
In the previous part we had a short introduction to requirements traceability and took a look at how to create a requirements traceability matrix. Now it is time to see how we can harness the...Read more
During the software development process various partial results are generated, but it is not always easy to maintain an overview of them. This is however essential for monitoring progress, analysis...Read more