

It tells the application how to map a database data type to an UML data type. This data type mapping file is a user-definable XML file, however a library of options is pre-loaded. It displays all the tables in the “Working Table Selection” window.
TABLEPLUS DIAGRAM GENERATOR ISO
We cannot configure EA to apply an ISO 19100 profile (or any other chosen target profile) to the imported model automatically.Figure 1 is a class generated by EA based on a imported database schema.įigure 1: A class generated by EA’s “Import DB Schema” function For example: It stores the primary/foreign key information in an UML function which has “PK/FK” stereotype applied, and the name of the primary key is a random generated name. This profile doesn’t meet our requirement. The EA ( Enterprise Architect) will apply its own database profile to the imported model.Option 2: Develop a new Enterprise Architect Add-in function.Option 1: Use Enterprise Architect built in “Import DB schema from ODBC source” function.Convert database data type to the ISO19100 data type ( ISO19103 Conceptual Schema Language, ISO19107 Spatial Schema ).Automatically apply ISO19100 profile to the newly generated UML model.The association Target Role name is the foreign key column name. Convert foreign key relationships into UML class relationships: A foreign key column should be transform into an association owner end ( Target Role ), but not a class attribute.Keep all the database schema information in the UML model, including database name, schema name, and foreign key name.The target idiom is currently ISO19100, however this could be made configurable if required.

(Platform independence is necessary since we want to reference the content, not interact with the original database).

Transform database schema into UML model, using a platform-independent idiom.Access an existing database schema (particularly SQL Server, Oracle and PostgresSQL) into a.Automating the capture of this mapping is the subject of additional experimentation. The refactoring process can potentially create the mapping as a side effect. Mapping the implementation to a more general model.Creating a more powerful model through refactoring and reconciling one or more imported schemas.
TABLEPLUS DIAGRAM GENERATOR FULL
There is no intention to support full object-relational mapping paradigms here, but to allow an existing implementation to be faithfully transcribed into a UML model to support: This involves mapping to PI data types, and identifying implementation patterns such as foreign key constraints as relationships. This tool provides a means to load an existing Platform Specific Model (PSM) into a UML model, performing the basic generalisations required to create a Platform Independent Model.
