RTF Report / related elements

[webrod]

Hi,

I am building my own documentation to document "requirements".

For each requirement, I want to see;
+ the "name" field
+ the "notes" field
+ the list of all the use cases associated to this requirement (I just need the name of each use case).

So I checked the "Element -> connector -> target -> element" when designing my report to include linked elements.
And I added the tag to display the name of the use case in the connector>target>element section.

In the "document -> options" dialog box, I have selected everything to be excluded except "requirements" and "use cases" to be sure that I get only requirements and uses cases elements.

Now I generate my documentation.
I get all the requirement =>OK
For each requirement, I get the list of uses cases => OK
BUT... I get ALL the elements associated to the requirements, not only the use cases!!
Let's say that I have associated a "component" to a requirement in the design phase, it is also displayed in the list!!

So my question is:
+ is there a way to restrict the list of element to a sub set of elements type (only requirements and uses cases)?
It works with first-level elements but not with associated elements.

thanks you very much for your help  
rod

[Luis J. Lobo]

It's impossible, by the moment, filter by link type or source/target element type. Relations are all documented.

[Dermot]

In answer to your query - the report generator basicaly works on one level of elements and its connectors.  There is currently no filtering of connectors available. So using the connectors to set Use Case elements will give all elements connected to a Requirement.

There are alternatives to this - see the reports:
 Project | Documentation  | Implementation details &
 Project | Documentation  | Dependancy details

Also in the RTF report generator you can run the report on the Use Case element set -  and in the template set up the Section: Element::External Requirements - to show all realized Reuirements associated with each use case.

The reply to http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1216134520 also gives another alternative using Virtual Documents.