Book a Demo

Author Topic: Bug? – single element RTF doc omits child info  (Read 2400 times)

erixon

  • EA Novice
  • *
  • Posts: 11
  • Karma: +0/-0
    • View Profile
Bug? – single element RTF doc omits child info
« on: September 21, 2006, 01:23:22 pm »
BACKGROUND INFO:
I am using EA version 6.1.790.

My Use Case View has the following general layout:

Package
-Use Case Diagram
--Use Case
-----Activity Diagram
----------Initial
----------Activity1
----------Activity 2
----------Activity 3
----------Final
--Use Case
-----Activity Diagram
----------Initial
----------Activity1
----------Activity 2
----------Activity 3
----------Final
--Use Case
-----Activity Diagram
----------Initial
----------Activity1
----------Activity 2
----------Activity 3
----------Final

Each Use Case element may have constraints, scenarios, requirements and files.
Each Activity element may also have some or all of these.

When I generate RTF documents from the Package level, my RTF templates recursively return all this information very nicely since they include the <<Child Elements>> section.


PROBLEM DESCRIPTION:
However, when I open the Use Case Diagram, select a single Use Case element, and generate RTF documentation, the information returned for the Use Case element is fine but the information for the child elements does not include scenarios, constraints, internal requirements or files.  It DOES include element name and notes, and external requirements though.

This occurs when using existing templates in EA as well as my own customized templates.

I have been unable to find any RTF help file or documentation that describes this behavior.  Is there something I am missing or is this a bug? This is a significant limitation in reporting capability as we need to be able to generate detailed documentation on either one or multiple use cases (i.e. single element or package).



Here is an example of the RTF template layout:

package >
element >
{Element.Name}
{Element.Notes}
requirement >
{ElemRequirement.Name}
< requirement
external requirements >
{ElemExtRequirement.Name}
< external requirements
constraint >
{ElemConstraint.Name}
< constraint
scenario >
{ElemScenario.Scenario}
< scenario
file >
{ElemFile.FilePath}
< file
child element >
< child element
< element
< package
« Last Edit: September 21, 2006, 01:24:00 pm by Erixon »