Latest revision as of 06:49, 4 April 2025

Transforming a Fact Model to allow artifact generation (XML, SQL, etc) requires a set of operations. The transformation settings dialog allows users to configure these steps. Model transformation for automatically updated diagrams (UML, etc) do not require any specific setting. These are presented in diagrams which only require a simple refresh.

For physical artifacts, the IG-file needs to be transformed into a so-called IGG-file. This can be done in the background or explicitly by clicking the appropriate menu item. Types of artifacts, or implementation preferences, may require different transformation settings. These may be managed by storing them in a so-called profile.

Explicit calling of Transform creates a snapshot of the current model before transformation starts, and when successful add the IGG file to the project.

Before

Derive data types. Once enabled the label datatypes are derived from the population, if not yet set.
Clear population. Erases all example population.
Clear entity schema. Erase schema names from otft's before transformation starts. If name clashes occur, the schema is prefixed to the name.
Transitional
Temporal
Art. Key
Localize

Well-formedness

Allow validation warnings
Show only errors and warnings

Project Files

Overwrite known IGG Files
Warn before saving IG file
Copy Active Diagrams

Transformations

Group. Grouping roles together. Selecting proposal merely checks the options and performs no real grouping. Performing a step-by-step enables you to manually go through the grouping process. Derived subtypes enables grouping for subtypes which are marked as "derivable".
Lexicalize. This step of lexicalizing makes sure every role is played by a label type. This is a requirement for database script generation.
Reduce. If the population is already present under different fact types, we may reduce the fact types which contain duplicate or obsolete storage for them.

Namings

Naming Conventions
Column Names. Database column names can be chosen by different naming algorithms. They vary from the full conceptual path down to numbered label types. Depending on your preferences you may choose any of them. They all create unique names, see also: Column Names.
Column Fix Type Names

Options

Automatic primary key
Assume wide UC
Assume wide TC

After

DBMS types

Diagrams

Show subsets
Hide labeltypes
Show primary UC

@@ Line 1: / Line 1: @@
-Model transformations may be required for certain artifact generations. The dialog to set how to transform the model is displayed here.
+Transforming a Fact Model to allow artifact generation (XML, SQL, etc) requires a set of operations. The transformation settings dialog allows users to configure these steps. Model transformation for automatically updated diagrams (UML, etc) do not require any specific setting. These are presented in diagrams which only require a simple refresh.
+For physical artifacts, the IG-file needs to be transformed into a so-called IGG-file. This can be done in the ''background'' or explicitly by clicking the appropriate menu item. Types of artifacts, or implementation preferences, may require different transformation settings. These may be managed by storing them in a so-called ''profile''.
+Explicit calling of Transform creates a snapshot of the current model before transformation starts, and when successful add the IGG file to the project.
 [[File:GlrOptions12.png]]

Difference between revisions of "Modeler:14/GlrOptions"