Generate HTML for Entire Multi-Model Project

[SteveZ]

Howdy,

Is it possible to generate HTML for an entire multi-model project?  I'm really impressed by the HTML generation capability, but I've found that you can only generate one model at a time.

At the moment I have a project (.eap file) composed of multiple models (3 "industry" models, 1 "business" model, and 3 "system" models).  All of these are tied together by a high-level root "project" model that shows all of the other models as packages, so that you can see the relationships between the models and navigate to them by double clicking on the .  

I would like to generate HTML for the entire project so that the generated web page appears like the project file in EA (with all of the models listed in the left-hand pane, and with the "project" model listed as the top-most model).

Is it possible to generate HTML for an entire project?

Thanks much,

Steve

[smendonc]

You should be able to right click on the root and choose the html option.  This option sometimes is hidden under Documentation-->html report.

Stan.

[SteveZ]

You should be able to right click on the root and choose the html option.  This option sometimes is hidden under Documentation-->html report.

Stan.

Thanks for the reply. You are correct, this will generate HTML for the selected model ("root"), but I would like to generate HTML for the entire project, which would include all of the models ("roots") in the project.  I've found it useful to have multiple models (industry/business/system) to document the different levels of abstraction, and so I would like to generate it together as a single web page.

[Paul Lotz]

If I remember correctly you can create a new project and then add the packages that were roots in the first project as nonroot packages in the new project, but still in parallel to one another.  Then build the HTML for the new (single) top-level root.  I haven't tried this, but I think it would work.

[SteveZ]

If I remember correctly you can create a new project and then add the packages that were roots in the first project as nonroot packages in the new project, but still in parallel to one another.  Then build the HTML for the new (single) top-level root.  I haven't tried this, but I think it would work.

Thanks, I can give that a try.  However, it would be nice if models could be represented by EA models (business model, system model, etc.) and views could be represented by EA views (use case view, logical view, etc.).  It is unfortunate that models have to be demoted to views, and views have to be demoted to packages just to make HTML generation work.

[Paolo F Cantoni]

Well folks, in my view the whole view vs root vs project vs... is a chimera...

Don't get hung up on it.

They are there to help you get started and productive early and quickly.

Find the possibilities and limitations of EA and work within /around them to provide the modelling environment you need!  EA is flexible enough to do that.

For my own part, I've come to the view that there can only be one root: "Repository"  everything else is subordinate to that...  That way everything seems to work better.

My AU$0.05
Paolo