Book a Demo
Prev Next

Using Controlled Packages

A Controlled Package is a Package configured to save and load in Native/XMI format to a named file. Native formats are Enterprise Architect-specific file formats while XMI is UML compliant, with Enterprise Architect extensions to support diagrams and additional model elements. Controlled Packages are a useful means of 'externalizing' parts of an Enterprise Architect model.

When configured to use XML, the output can be loaded into any XML viewer, or used by any XML-based tool to perform manipulations and extracts, such as document or code generators.

Controlled Packages appear in the Browser window with a small colored rectangle to the left of the Package icon, as shown for the CIM Package:

An example for Reporting the  Deletion of Cross Package References in Enterprise Architect.

Using Controlled Packages you can support:

  • Widely distributed development by having team members submit Packages in Native/XMI format for import into a central Enterprise Architect repository
  • Version Control, by writing model elements in XML text files suitable for Version Control using standard Version Control software
    Using XMI this way, you can manually connect to third-party Version Control software outside the Enterprise Architect environment; Enterprise Architect internally supports the configuration of Version Control through SCC and CVS
  • Import and export of model elements between different models
    For example, a Class library can be re-used in many models and kept up to date in target models using Controlled Packages, reloading Packages as required when new versions of the Class model become available

Notes

  • If you are importing an XMI 1.1 file that was previously exported with a UML_EA.DTD (Data Type Definition) file, the UML_EA.DTD file must be present in the directory into which the XMI file is being written; an error occurs if the UML_EA.DTD file is absent
  • When you select to apply a DTD during an XMI 1.1 export, the UML_EA.DTD file is written to the output directory into which the XML files are written (unless the UML_EA.DTD file is already present in the directory); no error is generated if the UML_EA.DTD file is not present in this directory during the XMI export

Learn more