Requirements Hierarchy

[natvig]

I would like to see a feature where the requirements hierarchy (or any element hierarchy) optionally could be preserved when doing a model search.

This is useful if you wish to make a selection among requirements based on some attribute (tagged value) but need to keep the hierarchical nesting as well. (The result would be that requirements without match on attribute still should be selected if it owns an element with matching attribute.) Obviously, the resulting selection can then be used to create reports.

This is a feature that is available in other requirements management tools e.g. ReqPro/SoDA.

[thomaskilian]

Have you tried View/Hierarchy (note that displaying this window can slow down selecting an element)

[natvig]

Yes, I'm well aware of the Hierarchy tab which I use frequently.

However, it does not solve my problem with preserving the hierarchy and the parent elements when doing a search. My suggestion is therefore to add an option to the search function that allows the user to optionally select parent items for a matching element, also when the parent items does not match the search criteria. The function will e.g. allow nested requirements to print correctly (together with its parent) in a report where only a subset of the requirements are required.