Table of Contents
For those used to working with the Poseidon for UML interface, many of the features will be familiar. However, this tool has been designed for a different purpose, namely to provide UML features when coding instead of having the design and analysis focus of Poseidon for UML. A different approach means some of the interfaces and procedures have changed, so keep this in mind when working with Apollo for Eclipse.
Apollo for Eclipse provides two distinct diagrams to view your code: the canonical package diagram and the non-canonical class diagram.
Canonical package diagrams present all of the elements and connections (e.g. classes, associations, etc.) that exist within the package. It is a complete view into the semantic data of the package in its entirety, which implies a 1-1 relationship between the views and the elements of the packages. That is, every element in the package and only elements from that package are displayed once.
As such, elements from other packages cannot be displayed in the canonical package diagram. Likewise, removing an element from a canonical package diagram actually deletes the element from the project completely.
Non-canonical class diagrams are new to version 2.0. The non-canonical diagrams do not attempt to capture the entire model (although they certainly may), and are therefore much more flexible. Any number of non-canonical class diagrams may be created in any package, including the top-level default package.
Any element from any package may be added to the non-canonical class diagram. Elements which do not belong to the package of the non-canonical diagram are displayed with a shortcut icon.
Just as in canonical package diagrams, deleting an element deletes it from the project completely. However, non-canonical class diagrams also offer the possibility to remove an element from a single diagram without deleting it from the project. This option is available through the context menu.