Skip to end of metadata
Go to start of metadata
This page describes the installation and use of Sparx Enterprise Architect for OOI CI.

Sparx Enterprise Architect (Ultimate Edition) is the architecture and design tool for the OOI CI and the entire OOI program. It is used for official OOI configuration controlled specification drawings, for interface relevant use cases and for other UML diagramming purposes.

Installation and Set Up

We are using EA version 8.X, which is backwards compatible with the previously used 7.5.X. We are also using the DoDAF extensions and profile.

There are multiple floating licenses available. The client requires MS Windows.

See here:

Examples are provided.

Using Enterprise Architect in OOI CI

Working with the Model

Get a recent copy of an EAP file for an architecture model as described in EA Installation and connect it to a SVN (subversion) version control server location.

In order to edit the model, lock a part of the model (Package Control > Check Out...) and make your edits. Finish quickly and merge changes back to the server (Package Control > Check In...)


We apply these conventions for OOI CI models:

Trouble Shooting

It is possible to encounter errors. Some hints to deal with errors are listed here:

HTML Documentation Export

HTML Documentation is created for OOI CI milestones and architecture baselines, as well as for intermediate versions during design phases. OOI CI Architecture exports can be found here: OOI CI Architecture Export

EA supports linking to the unique identifiers of diagrams and model elements.


Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jun 04, 2012

    Maurice Manning says:

    MMeisinger 12Aug2011: Linking to permanent identifiers for EA diagrams: See ht...

    MMeisinger 12Aug2011:
    Linking to permanent identifiers for EA diagrams:


    The way to do this is like this:

    You get the GUID of a diagram by going to EA, clicking the diagram or element in the tree view and select Copy Reference > Copy Node GUID from the context menu.

    Paste the GUID as last part of a link as above and remove the curly braces (note that the index.htm MUST be all lower case).

    So what can and will change is the base URL:
    will be replaced by

    Obviously, we want to manage the release part of the URL. I suggest for all R2 diagrams and elements

    This may be an alias for more specific exports, such as

    Ideally, the same GUID should be found in all exports, as soon as the respective element was created. We will keep important old exports (LCO, LCA etc versions) around.