Mapping Between the Conceptual and Object-Oriented Submodel

Innovator resolves the tension between the application view and data management by means of a mapping and transfer mechanism which converts the structures of these data and object submodels into each other.

Motivation for Mapping Between ER and UML Models

You can use mapping between an ER and a UML model (and vice versa) if the necessary requirements have been configured. Changes to the model configuration may require maintenance of this mapping configuration.

The applicable submodels of the same Innovator model are referred to when talking about ER and UML models below.

Object-oriented modeling is a basic technique in application development. However, corporate data is usually not managed in object-oriented database systems, but in relational database management systems (RDBMS).

The structure of the data does not focus on application-specific requirements, but represents an organization-wide data model that contains all the data relevant to the organization and the relationships between this data. Applications must be based on this data model and extend it in a way compliant with the model.

The connections between elements of data and object models are stored in references; these can be traversed between the submodels in both directions at any time.

The configurations are made available as XML files (\$INODIR\java\M2M_OOER\configuration\Innovator.Model.Configuration\Mapping\Mapping.ER2OO or ...\MappingOO2ER).

You can customize the OO2ER.FORWARD and OO2ER.REVERSE configuration descriptions to suit your needs. You must already have experience with meta model elements and model configuration in Innovator (stereotypes, templates and content configuration in particular) to be able to do this.

Import via the configuration loader evaluates configuration descriptions and creates the corresponding, model-compliant configuration and model elements required in the model.

Note

Reload the configuration descriptions once you have changed the model configuration (new stereotypes) in order to maintain configuration prerequisites for references.

Once the configuration is completed, the mapping can be found under Extras>Map Model>Mapping.

ER-OO Mapping

Mapping Options

Mapping supports the following mapping options from the conceptual model to the UML model:

  • Entities to classes
  • Entity attributes to attributes of classes
  • Semantic data types to type classes
  • Relationships to associations, aggregations or compositions
  • Categories to generalizations
  • Duplication of ER diagrams to class diagrams

OO-ER Mapping

Mapping Options

Mapping supports the following mapping options from the object-oriented UML model to the conceptual model:

  • Classes to entities
  • Attributes of classes to entity attributes
  • Associations, aggregations or compositions to relationships
  • Generalizations to categories
  • Attribute types to semantic data types
  • Duplication of class diagrams to entity diagrams

Mapping Elements in the Mapping Editor

Proceed in the same way as mapping between the database schema and the conceptual model when mapping elements.