HOPEX Data Governance > Data Architecture and Tools > Synchronizing logical and physical models > "Logical to Physical" Synchronization Rules
"Logical to Physical" Synchronization Rules
 
Logical > physical synchronization: the application and logical data areas
Logical to Physical Synchronization: the Entities (or Classes)
General rule
Sub-entity
Abstract entity
Realized entity
Logical to Physical Synchronization: the Associations
Constraint associations (multiplicities: 0,1 or 1,1)
Constraint associations (multiplicities: 0,1 and 0,1)
Deadlocks
Non-constraint association
Association class
Logical to Physical Synchronization: the Parts (UML)
Example 1: None / *
Example 2: Aggregation / *
Example 3: Composition / 0..1
The following rules are applied for transforming class diagrams into relational formalism.