Enable the filtering of Traces using DocFactory syntax
The ability to break out traces based on a pre-defined attribute. For example, let's say I have a user defined attribute set up that captures the type of requirement - use case, business requirement, business rule, functional, non-functional.
Within my project, I have a use case that traces from a Business requirement, and traces to business rules, functional requirements and non- functional requirements. Currently, when I produce a doc factory export using my SRS template, I can only filter on the trace type i.e. Trace From or Trace To. What I would like to be able to do is for a specific business requirement, filter on the user defined attribute mentioned above to list the traced to use case, under which I would like to be able to display the traced to Business rules in one section (or heading) then display the traced to functionals in one section (heading) and the traced to non-functional in one section (heading).
I have currently worked around this by using the caliber Datamart facility and created my own custom views, reports and exports.
This item is in the backlog but is not on our current roadmap. We recognize the value of this capability and this will be considered as we work on traceability improvements in the product.
Phil Arnold commented
Any update on this Archie Roboostoff?
Alicia, I effectively built my own access database from a datamart export and figured out how to link requirements and then arrange them in to views. You would think this would be pretty easy to do in Caliber wouldn't you? Oh no...
Alicia Gordon commented
Phil, I have the same problem and I have been looking for a work around. If you could provide some insight and point me in the right direction, it would be much appreciated. Thanks! Alicia