Mappings between ER/Studio BA and ER/Studio DA

Go Up to Conceptual Model Export to ER/Studio DA

Exporting to ER/Studio DA is based on a pre-defined mapping to create the appropriate ER constructs from the Conceptual Model. The table below outlines the Entity mappings. There is also a section that covers the Attribute Optionality mapping and Attribute Datatypes mapping.

ER/Studio BA Object	ER/Studio DA Object
Subject Area	Submodel
Diagram	Submodel Diagram
Subject Area Name	Sub-Model Name
Nested Subject Area	Nested Sub-Model
Business Entity	Entity (Data)
Business Entity Name	Entity name and Table name
Business Entity Description	Entity Definition
Business Attribute	Attribute inside the entity
Business Attribute Name	Attribute Name and Default Column Name
Business Elements	Domain
Binding between Business Element and Business Attribute	Bounded Domain
Relationships	Relationships
Interaction	No mapped in ER/Studio DA
Inheritance (Business Entities)	Supertype/Subtype
Inheritance (Subject Area)	Nested Submodels

Bound Business Elements

If a Business Attribute is bound to a Business Element, the attribute is mapped to the Domain. The Attribute definition is mapped to that from the domain.

ER/Studio BA	ER/Studio DA
Business Element	Domain
Business Element Name	Domain Name, Attribute Name, Column Name
Business Element Datatype	Domain Datatype
Business Element Description	Domain Definition. Definition of bound attributes

Relationships

In ER/Studio DA, relationship directions will be drawn in same direction as in ER/Studio BA. Relationships between business entities are exported as relationships between logical entities. The following are rules for each relationship type:

ER/Studio BA	ER/Studio DA
Relationship Name	Business Name
Relationship Description	Relationship Definition
Verb phrase	Verb Phrase (for Many to One relationships, Inverse Verb Phrase)
Inverse verb phrase	Inverse Verb Phrase (for Many to One relationships, Verb Phrase)
Type: Generic	Non-specific
Type: Many to Many	Non-specific
Type: One to Many, Mandatory	Non-identifying with the end point at the child. Existence = Mandatory, Cardinality = One to Zero or More
Type: One to Many, Optional	Non-identifying with the end point at the child. Existence = Optional, Cardinality = Zero or One to Zero or More
Type: Many to One, Mandatory	Non-identifying with the begin point at the child.(reversed parent-child relationship and verb, inverse verb phrases). Existence = Mandatory, Cardinality = One to Zero or More
Type: Many to One, Optional	Non-identifying with the begin point at the child.(reversed parent-child relationship and verb, inverse verb phrases). Existence = Optional, Cardinality = Zero or One to Zero or More

Note: Optional/Mandatory relationship settings are carried over to ER/Studio DA. If no optional/mandatory setting exists, you have the option to define what the default treatment is (i.e., export a non-specified optionality as either optional or mandatory). The default is that a non-specified relationship will be set to mandatory.

Attribute Optionality and Datatypes

The first table lists the Attribute Optionality mapping.

ER/Studio BA	ER/Studio DA
Mandatory	Allow Nulls = No
Optional	Allow Nulls = Yes
Unspecified	Allow Nulls = Yes

This table displays the Attribute Datatypes mappings.

ER/Studio BA	ER/Studio DA
Binary	BINARY(10)
Boolean	BIT
BLOB/Image	IMAGE / LONG
Char	CHAR(10)
CLOB/Large Text	LONG
Decimal	DECIMAL(8, 2)
Date	DATE
Integer	INTEGER
None	CHAR(10)
Timestamp	TIMESTAMP/DATE
Varchar	TEXT
XML	XML(ER 7.1 and above) or VARCHAR(10) (ER 7.0)