Introducing Architecture Modeler

Use Architecture Modeler to add support for unsupported languages and frameworks to Enterprise Analyzer (EA). You can also use it to extend support for already supported languages and frameworks. Architecture Modeler's:

Based on your input,Architecture Modeler creates a plug-in that defines an extension, or add-on, to the EA metamodel. The add-on specifies the entity and relationship types of interest in the newly supported source files.

The plug-in also references a universal parser configuration file that defines the search patterns EA uses to extract entities and relationships from newly supported files. For text files, search patterns are mapped from regular expressions. For XML files, search patterns are mapped from XPath queries.

Here in schematic form are the tasks you perform in Architecture Modeler:

  1. Load an existing metamodel.
  2. Save the metamodel with the name of your extension.
  3. Add a sample source file of the type you want to support in EA.
  4. Define the entity types for the add-on.
  5. Define the relationship types for the add-on.
  6. Map search patterns for the entity and relationship instances you want the parser to extract.
  7. Export the model to EA.
  8. Reconfigure EA.

Before turning to these tasks, users who are new to EA may want to familiarize themselves with the concepts underlying the EA metamodel. Experienced users can skip straight to the tasks.

Note: Architecture Modeler currently supports the level-1, or application-level, metamodel only. Support for the level-2, or object-level, metamodel (Interactive Analysis) will be available in a future release.

Entity extension mode is currently not available for the following entities: EZT, CA7, JSP, JSX, NetronSPC, NetronSpec, TLD, TS, and WebConfig.

Important: If you are using Windows 7 or Windows 8, make sure you are running the Architecture Modeler with administrator rights. Otherwise some operations might fail.