Reporting on multiple models

[Rouven]

Hello everyone,

I have a single EAP file with multiple models (--> root nodes) contained within, each representing a logically different aspect. In addition I have e.g. an overview diagram that points to the different models, as well as elements from one model referring to elements from another model.
With Enterprise Architect this is not a problem and up to now I also thought of these different models as just a higher level of packages.

Unfortunately, trying to create an HTML documentation, I noticed that it seems to be impossible to create one documentation containing all the different models. Is there a workaround other than pushing everything down by one level?

Thanks for you suggestions,
cheers, Rouven

[qwerty]

What about creating a top level static HTML that links the single HTML root for each project?

q.

[Rouven]

I thought about such a post-merger too, but that leaves two problems:

• table of contents (left side navigation) incorrect
• links between models can still not be followed because EA seems to generate links based on filenames created during generation, not based on GUIDs...

[Paolo F Cantoni]

I thought about such a post-merger two, but that leaves two problems:

• table of contents (left side navigation) incorrect
• links between models can still not be followed because EA seems to generate links based on filenames created during generation, not based on GUIDs...

You, too, can submit a feature request/bug report on this non-reproducibility of output.

However, there is a mechanism whereby you can call into the HTML from outside supplying the GUID of the diagram you want opened.

I can't recall the syntax, but this may be of help.

Paolo

[Luis J. Lobo]

What about creating a "Virtual Document" (Model Document) of your desired packages and generate it as HTML report?

This functionality was introduced in v9.x

See: http://www.sparxsystems.com/enterprise_architect_user_guide/9.3/reporting/master_documents_and_model_doc.html

Regards,

Luis.

[Rouven]

Hi,

that might actually be a helpful hint. So far I had only seen information on the model documents being used as RTF documentation. I will give this approach a try, although I am afraid it may not accept root-level models just like diagrams don't. We'll see.

Thanks! Regards, Rouven

[Rouven]

Hi again,

so your solution could work in theory, but does not fully solve my problem. I have packages of the same name in the different root level models, e.g. a Revision History.
Since I can not drag & drop the root model into the model document, I would have to do so with the contained packages. That in turn means that the documentation contains the packages without the information on the containing model, which unfortunately is not helpful...

However, thanks for the hint, maybe it helps others!