Understanding Design Layers in erwin Data Modeling

Moving between conceptual, logical, and physical models appears straightforward, but maintaining alignment across these layers as systems scale presents challenges. This article focuses on building and maintaining consistency across these layers to ensure models hold up in practice.

Overview of Design Layers

Design layer modeling supports application development by creating separate conceptual, logical, and physical data models. Each layer serves a distinct purpose:

• Conceptual Model: This layer includes basic entities and serves as the foundation for further development.
• Logical Model: This layer captures business requirements and is often referred to as an attributed logical model.
• Physical Model: This layer represents the actual data implementations derived from the logical model.

Creating a Conceptual Model

To create a conceptual model, access the data modeling tool and select the conceptual model type. The process involves:

1. Navigate to the file menu and select "New" to create a conceptual model.
2. Utilize the Explorer pane to add object types such as annotations, entities, and relationships.
3. Define entities by dragging and dropping them into the diagram, naming them appropriately (e.g., "Customer" and "Order Item").

Deriving a Logical Model

Once the conceptual model is established, derive a logical model by following these steps:

1. Access the design layers and select "Derive New Model."
2. Change the name of the derived model to reflect its logical nature.
3. Add a new diagram to visualize the logical model, ensuring it retains the entities from the conceptual model.

Transitioning to a Physical Model

To transition from a logical model to a physical model, perform the following:

1. Select the target system (e.g., Azure Synapse Fabric Lake House) for the physical model.
2. Utilize data type standards to map logical data types to physical data types.
3. Create a new physical diagram and auto-populate it with the entities from the logical model.

Synchronization Across Models

Maintaining synchronization between models is crucial. This involves:

1. Adding new entities to the conceptual model and synchronizing them with the logical model.
2. Using the synchronization feature to compare and resolve differences between models.
3. Incorporating changes from the conceptual model into the logical model to ensure consistency.

Conclusion

By understanding and implementing design layers, data modelers can create structured, maintainable, and scalable data models. This approach allows for effective collaboration among teams and ensures that business requirements are accurately reflected in the data structures.

For further exploration, consider how active model templates can enhance the derivation process and governance within your data modeling practices.