Table

The physical table is an implementation within a relational database and is linked via a trace to the logical data model.
Physical tables are converted to table structures in (relational databases). That is why columns and associations are worked out for these tables. Multiple types of constraints or rules can be added to the tables, columns and associations. Think of primary and foreign keys, check constraints and the like.

Package	Physical data model viewpoints
Author	Bert Dingemans
Alias	--
Stereotypes	table

Attributes

Name	Type	Cardinality	Description
Optional Column	sql_variant	1 - 1	--
Required Column	sql_variant	1 - 1	--

Mappings

Name	Source	Source attribute	Target	Target attribute
Optionele Eigenschap	Table	Optional Column	Logical entity	Optionele Eigenschap
Verplichte Eigenschap	Table	Required Column	Logical entity	Verplichte Eigenschap

Diagrams

Primary Physical data model viewpoint

The physical data model consists of physical table entities, properties and associations. This is modeled according to the rules of the platform (usually the relational database) and can therefore be worked out in detail in accordance with the rules of the platform.
If desired, a detailed viewpoint can be developed for this purpose. This also applies to physical models for XML schemes and the like.

Diagram in repository

Secundary trace viewpoint

This is an extension of the primary viewpoint which describes a link between the layers. This trace viewpoint is relevant in the situation where the model is used to generate program code based on classes and tables.

In that situation you would like to have lookups and a trace between the logical and physical data modeling.