This is how to create traces
Requirements are the be all and end all of traceability in objectiF RPM. The traceability of all decisions helps you to ensure high stakeholder satisfaction levels – from the stakeholder goals phase through the requirements phase, all the way to the solution. Additionally, traceability is a prerequisite for successful audits and it supports the validation and verification of requirements. The transparency makes the path between requirements and tests much simpler and it makes the workload easier to estimate when you are performing maintenance.
But some agile teams still have a few reservations. They think to themselves: “Traceability – doesn’t that just mean that there will be more artifacts and more up-front activities, more “waste” and arduous work?” That’s not true with objectiF RPM. When you create relationships between requirements and the artifacts in the application lifecycle- whether in a UML/SysML diagram, in a backlog or directly in the description form for the requirements or artifacts – then you can create traces for your traceability. And you can do that without incurring any extra administrative costs. The relationships – whether you use a mouse to include them in the diagram or incorporate them into a form or backlog with a few clicks – are consistently saved in the objectiF RPM online repository. You can use them to navigate between artifacts if you want to figure out if the change will have an impact on the connected test cases. Or you could evaluate the relationships using queries. And if necessary you can generate documents containing a lot of information about the relationships between the artifacts. You will find document templates for this purpose in objectiF RPM. In this way your approach can be nimble yet traceable.
Find more information in the Lean Traceability Whitepaper >>