Logical model and domain model

I am not a database guy. My understanding of data modeling is not extensive. From this limited understanding, the logical data model is an abstraction of the physical data model that does not contain anything specific to a particular product / storage environment. Logical data modeling, apparently, is associated with the involvement of business experts in their process, and therefore it seems to me that he hedges the world of the world model.

I thought the logical data model was more concerned with data, while the domain model was more concerned about the problem area. The logical model that considers normalization, the domain model is smaller. I'm just embarrassed here, so it would be very helpful if someone could clearly explain the differences between them.

Many thanks!

+6
database architecture database-design data-modeling domain-driven-design
source share
4 answers

See this thread , which covers the same issue.

There are significant matches between the domain model and the logical data model for the same problem space. People often use the "Domain Model" as short for "Object-Oriented Domain Model." In this case, the biggest difference is the behavior. The OO domain model describes data, relationships, and behavior; the logical data model does not cover behavior.

Despite the differences in approach, they have a common goal: to describe the concepts in the problem area and their relationship.

+5
source share

As indicated by another shave, the logical model focuses only on the data, in particular on how the data is related. Boards are just as effective as tools, the only thing that is really lacking in the first example (below) is the labels on the joints between the tables.

alt text (Logical data model - board)

alt text (Logical data model with a tool)

In addition to data, domain models include processes and events (as stated in sfinnie). Target audience and attention are focused on the development / code level (as Nathan Hughes pointed out).

If you want to draw domain models in UML, you must use the Class Diagram :

alt text (Domain Model)

+4
source share

It looks like you have a nice pen. There is always some overlap of domains, and there are always differences of opinion regarding what belongs. I would say don’t get hung up on the specifics, because, as you know, in the center of attention of each domain you are cool.

0
source share

The logical model and the physical model are the terms used by the guys in the database, the logical model is the ideal of how different entities are related, the physical model takes into account real-world compromises, such as denormalization. A domain model is a term used by application developers when they talk about creating an object model that contains data controlled by the application, as well as methods that contain business logic.

0
source share

All Articles