What is the best way to separate software requirements?

[Mallacoda]

We have a workflow that imports all system requirements from DOORS in EA.
Only a subset of these requirements is related to software.

I want to find a way that allows me to run a compliance matrix on just the software requirements against Use Cases, Software Architecture and Software Design.

Is the best option to create a requirement stereotype of "software" and then filter that way in the matrix?

I had hoped to avoid that approach as we already stereotype requirements by source category, and using multiple stereotypes is clunky, doesn't display in the browser, and isn't supported by eaDocX addin.

Tags aren't displayed in the browser at all - so hard to see which ones are which - and I can't see a way to filter the matrix using tags anyway.

Moving all the software requirements to a separate package means that the structure would go out of sync with DOORS so that filtering option isn't viable.

What's the best approach here?

[Geert Bellekens]

You can also use a search to set as source/target of your matrix. In a search you can filter on tags, or subtypes, or something like that.

Geert