Product :::Model Management

The EA WebModeler model management subsystem manages information within the repository and exchanged with external modeling tools in conceptual models composed of repository knowledge items and their relationships. EA Webmodeler can manage unlimited Model Types and Models. A Model Type defines a kind of model that a user may want to work with, while a Model holds the elements that are part of a given model. Each model is of one type. Elements in the repository can be part of 0, 1 or more models.



Mappings, held on the Model Type and expressed in XML, translate repository types to visual representations and vice versa. An arbitrary number of mappings may be created: Thus repository content can be reflected in any desired notation and various notations can be semantically translated into equivalent repository content.

External modeling tools (e.g. Visio) and other products (e.g. PowerPoint, Ms Project) can use a provided API to request model information from EA Webmodeler. The information is returned as an XML document. The interaction is achieved over standard networking protocols, so requestors can be remote. External tools can render the information into visual models (e.g. as is done with an available Visio requestor package) or use it to construct other representations (e.g. a project plan, spreadsheet or presentation). Visual models can be saved back to the repository where layout, sizing and label information preserved.

It is equally easy to model in an external tool and submit the model to EA Webmodeler, where an appropriate mapping will allow relevant knowledge items and relationships to be created in the repository and linked to the appropriate model and model type. This can be achieved for content level models as well as meta models.

Models can be retrieved, modified in the external tool, and saved back to the repository as a new model or version of a model. Any new items/relationships created in the modification will be created in the repository. Items which remain unchanged will be shared between the models, eliminating redundancy. Naming conventions and filtering options allow retrieving desired models e.g. current vs future; by version number etc.

These capabilities, together with the inherent EA Webmodeler multi user and web based architecture, offer unequalled flexibility:

• Create models via web interfaces from distributed workstations
• Create models via external visual or other workstation tools
• Integrate models centrally in shared repository, under secure control
• Translate disparate or disjointed visual representations into consistent semantic models in the repository
• Render semantic models into required visual representations
• Feed the repository from other tools with dynamic information e.g.
  costs from ERP systems, progress from project management tools
• Retrieve repository content to drive other tools e.g. process models into a workflow product
• Perform the above on a distributed basis, from a variety of chosen tools, provided they support XML and scripti

We invite you to discover our exciting EA solution. Please complete the form below and a representative will contact you soon