Date: Fri, 29 Mar 2024 16:15:08 +0100 (CET) Message-ID: <1525501561.2228.1711725308816@nm-docs> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2227_740413776.1711725308815" ------=_Part_2227_740413776.1711725308815 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Transformation engine itself is available in MagicDraw editions from Sta=
ndard and up.
However, only MagicDraw Architect and Enterprise editions bring any partic=
ular transformations. So for MagicDraw Standard and Professional edition us=
ers,
transformations are not available.
Plugins can bring additional transformations regardless of MagicDraw edi= tion. For example, users, who have the Cameo Data Modeler plugin, can use t= he transformation engine to run ER to SQL(Generic/ Oracle) transformations,= even if they do not have the MagicDraw Architect/Enterprise editions.
The Model Transformation Wizard enables running one of the predefined tr= ansformations. When using this wizard to run a chosen transformation, you h= ave to perform the following steps:
Each transformation converts the chosen model part into another model ac= cording to the rules of this transformation. Transformations are usually us= ed for converting models between different modeling domains, e.g., UML and = SQL.
All transformations follow a similar approach. They take a part of a mod=
el as the transformation source and copy it to the destination model, estab=
lishing traces between the transformation source and target elements. Then =
each transformation performs the specific model reorganizations, which are =
necessary for each
transformation type according to the transformation options specified by t=
he user in the transformation wizard. Transformation can also be performed =
in-place, i.e., the source model is not copied to the destination model, bu=
t transformation works directly on it instead.
Transformations also perform the so-called type remapping. During the tr=
ansformation between the different modeling domains, such as UML and SQL, i=
t is necessary to go through the data types used in the source model and ch=
ange the types from the source domain into the equivalent types in the targ=
et domain, for
example, changing String type usages in the UML model into the varchar typ=
e usages in the SQL model.