Composite Use Case Reporting in RTF Documenter

[Mr. George S]

I have a package ("My Test Package")  with just a use case diagram.  The use cases and actors are in other packages.  My use case diagram called “My Test Diagram” has a composite use case.  Double clicking “A Composite Use Case” brings up “My supporting diagram”

When I run an RTF report at the package level My Test Package, the RTF pulls in the diagram “My Test Diagram”, the elements within and their associated attributes, i.e. Notes, Scenarios, Requirements, etc.  However, I do not get the diagram “My supporting diagram” nor its elements.

Can the RTF documenter report on the supporting diagram and elements when they are in a different package than where the RTF is run from, ie “My Test Package”

Thanks

[Anders B]

Hi George,

I suppose the diagram is not in a child package? In that case you'd just have to add "child packages" in the "sections" panel. Otherwise the section "Package -> Diagram -> Element" might do the trick - see page 21 in the Sparx tutorial on RTF generation:
http://www.sparxsystems.com/downloads/whitepapers/Working_with_the_RTF_generator.pdf

This should make the use case element show, since it's linked on your first diagram. Rendering the element like a standard element would probably show it's child diagram "My supporting diagram".

Greetings
Anders

[Mr. George S]

I received the following from SPARX

 
Thanks for passing this on.
 
The RTF reporting does support reporting Child Elements & Diagrams (Composite) when the report is run from the package containing it.
This requires the Element::Diagram and Element::ChildPackage - sections are both enabled.
 
It also supports reporting diagram Elements external to the package using the Package::Diagram::Element - section. This section when left blank does reproduce the details defined in Package::Element section,  but this does not support recursing Child Element or diagrams from this section.
 
I will pass this on as an issue for review, however there may have been reasoning for not supporting this 'recursion calling recursion'.
 
The Issue number is:10014603