blocks|key|1115163|text|数据模型是一种只描述数据及其关系的设计模型。模型包含实体，但它们是根据它们拥有什么数据来描述的，而不是它们如何处理这些数据或它们的职责是什么。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1115164|另一方面，域模型是用于分析问题域的概念模型。它用具有关系、数据和行为的实体来描述领域。它将这些实体的职责描述为与理解问题域相关。|1115165|顺便说一句，关于UML的一个非常优秀且非常简短的介绍是：|1115166|UML+Distilled:+A+Brief+Guide+to+the+Standard+Object+Modeling+Language+|offset|length|1115167|entityMap|0|LINK|mutability|MUTABLE|url|https://rads.stackoverflow.com/amzn/click/com/0321193687^0|0|0|0|0|1Y|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@$H|V|I|W|1|X]]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

A datamodel is a design model that only describes data and it's relations. The model contains entities, but they are described in terms of what data they own not how they act on this data or what their responsibilities are.

An domain model on the other hand, is a conceptual model used in analysis of a problem domain. It describes the domain in terms of entities that have relations, data and behaviour. It describes the responsibilities of those entities as relevant for understanding the problem domain.

BTW an excelent and very short introduction to UML is:

<a href="https://rads.stackoverflow.com/amzn/click/com/0321193687" rel="nofollow noreferrer" rel="nofollow noreferrer">UML Distilled: A Brief Guide to the Standard Object Modeling Language </a>

blocks|key|3190703|text|数据模型侧重于DB模式定义，包括表、列和关系。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3190704|域模型专注于业务领域，包括概念(对象类)、行为(方法/逻辑)和关系。|3190705|在这两种情况下，基数都用于关系(例如，1:1，1:Many，0:Many，...)。|3190706|也就是说，理想情况下，您希望数据模型和域模型紧密相关，例如，一个有名字的人……还有一台MailingAddress+..。将具有NAME列和FK的PERSON表关联到MAILING_ADDR表条目。你必须决定逻辑寄宿在哪里-在软件系统中的对象中，还是通过过程、触发器等在数据库中。|3190707|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

A data model is focused on the DB schema definition, including tables, columns, and relationships.

A domain model is focused on the business domain, including concepts (classes of objects), behavior (methods/logic), and relationships.

In both cases, the cardinality is used for relationships (e.g. 1:1, 1:Many, 0:Many, ...).

That said, you would ideally like the data model and domain model to be closely related, i.e. a Person with name, ... and a MailingAddress, ... relates to a PERSON table with a NAME column and a FK to a MAILING_ADDR table entry. You have to decide where logic is hosted - in the objects in the software system vs. in the DB via procedures, triggers, and such.

blocks|key|1112620|text|我认为领域模型和数据模型现在与新的自上而下建模技术基本相同。我的意思是，您可以在类图中建模，并且只在图中添加数据库构造型。如果您使用我使用的工具，那么您的ejb3注释将立即与您的代码同步。下一步只需使用映射器来创建数据库。这项技术只适用于Java|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1112621|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I think that domain model and data model are now pretty much the same with new top down modelling technologies. I mean that you can model in a class diagram and only add database stereotypes in your diagram. If you use the tool that I use then your ejb3 annotation would be immediately synchronized with your code. The next step is only to use a mapper to create your database. This technology only works with Java

blocks|key|1861141|text|我认为在这里为后人提供一些清晰的东西是很重要的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1861142|数据模型是关于如何构造和表示信息的设计。所谓结构，我指的是像“第五范式”这样的关注点。通过表示，我指的是选择一种计算机序列化，例如整数、浮点或字符串。|offset|length|style|BOLD|1861143|术语领域模型实际上有两个合并的含义。|1861144|the+model+of+essential+characteristics+of+real+or+imaginary+in+.在这种模型中，类代表人类的概念化，实例是世界上的事物。例如，"+Person“类将具有包括你和我在内的实例，并且一个基本特征可能是每个人都有一个母亲。这种模型通常被称为概念本体或概念模型，其目的是提供关于世界上事物的所需信息的概念模型(+meaning.|1861145|A+model+of+required+information+)，通常考虑到某种系统。在这种模型中，类表示必须存储的关于世界上事物的信息。例如，"Person“类将具有表示有关您和我的必需信息的实例，例如名字、姓氏、出生日期、当前身高和当前体重。这些信息通常不包括所有的基本特征，比如我们的母亲，因为对于特定的系统来说，这些信息不是必需的。这种模型通常称为信息模型、概念性数据模型或操作本体。|unordered-list-item|1861146|1861147|UML和OWL语言都可以用于表示这两种领域模型中的任何一种。这两种模型都可以被认为是分析模型，因为它们都用于分析域。一个用于理解领域中的事物，另一个用于收集需求，以便为领域中的事物构建特定的软件或数据库系统。两者都是必要的，不幸的是，它们通常被混为一谈，以至于构建分析模型的人自己都对他们正在建模的东西感到困惑！|1861148|entityMap^0|0|0|4|0|2|4|0|D|P|13|O|0|0|A|B|K|W|B|57|2|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@$D|11|E|12|F|G]|$D|13|E|14|F|G]]|9|@]|A|$]]|$1|L|3|M|5|N|7|15|8|@$D|16|E|17|F|G]|$D|18|E|19|F|G]|$D|1A|E|1B|F|G]|$D|1C|E|1D|F|G]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1F|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|S|$]]

I think it's important to provide some clarity here for posterity. 

A data model is a design for how to structure and represent information. By structure, I mean concerns like "fifth normal form". By representation, I mean choosing a computer serialization, such as integer, floating point, or string.

The term domain model actually has two conflated meanings.

<ul>
<li>A model of essential characteristics of real or imaginary things in the world. In this kind of model, classes represent human conceptualizations and instances are things in the world. For example, a "Person" class would have instances including you and me, and an essential characteristic might be that every Person has a mother. This kind of model is often called an conceptual ontology or concept model and is intended to provide meaning.</li>
<li>A model of required information about things in the world, usually with some system in mind. In this kind of model, classes represent information that must be stored about things in the world. For example, a "Person" class would have instances representing required information about you and me, such as first name, last name, date of birth, current height, and current weight. This information often does not include all essential characteristics, such as our mothers, because, for the purposes of a particular system, that information is not required. This kind of model is often called an information model, conceptual data model, or operational ontology.</li>
</ul>

Both the UML and OWL languages can be used to represent either kind of domain model. Both can be considered analysis models, as they are used to analyze a domain. One is used to understand things in a domain, the other is used to gather requirements to build a particular software or database system for things in a domain. Both are necessary, and, unfortunately, they are usually conflated such that people building an analysis model are themselves confused about what they are modeling!

What is the difference between a domain model and a data model?

UML Domain Modeling

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

域模型和数据模型之间的区别是什么？

问UML领域建模
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问UML领域建模EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问UML领域建模
EN