领域类图和设计类图有什么区别? [英] What is the difference between a domain class diagram and a design class diagram?
问题描述
有人可以简要解释一下领域类图和设计类图之间的区别吗?
Can someone briefly explain the difference between a domain class diagram and a design class diagram?
我在 Yahoo答案上找到了解释， 但我觉得很混乱.
I found a explanation on Yahoo answers, but I find it quite confusing.
推荐答案
在数据库建模中，域模型被称为概念模型，而设计模型称为逻辑模型.
A domain model is called conceptual model in database modeling, while a design model is called logical model.
这些区别还用于模型驱动的开发中，在该模型中，我们继承了三种类型的模型:
These distinctions are also used in model-driven development, where we have a succession of three types of models:
- (独立于解决方案的) 领域模型 ，是在开发项目的系统分析或初始阶段，由领域/需求工程产生的；
- (与平台无关的) 设计模型 ，这是在阐述阶段系统设计活动产生的，通常基于领域模型；
- (特定于平台的) 实现模型 ，它可能是(例如JavaScript或Java EE) 类模型 ，SQL 表模型 或其他类型的 数据模型 .
- (solution-independent) domain models resulting from domain/requirements engineering in the system analysis, or inception, phase of a development project;
- (platform-independent) design models resulting from the system design activities in the elaboration phase and typically based on a domain model;
- (platform-specific) implementation models, which may be (e.g., JavaScript or Java EE) class models, SQL table models or other types of data models derived from an information design model.
尽管系统建模既包括信息建模也包括流程建模，但是您似乎只关心信息建模.在这里，我们可以将术语域类图"和设计类图"用于以UML类图的形式制成的概念信息模型和信息设计模型.
While system modeling includes both information and process modeling, you seem to be concerned with information modeling only. Here, we can use the terms "domain class diagram" and "design class diagram" for the conceptual information model and the information design model made in the form of UML class diagrams.
下图说明了概念模型与设计模型之间以及设计模型与实现模型之间的一对多关系:
The one-to-many relationships between conceptual models and design models, and between design models and implementation models are illustrated in the following Figure:
考虑到信息/类/数据建模，我们得到以下图片:
Considering information/class/data modeling we get the following picture:
作为说明从概念到设计到实现的推导链如何工作的示例，请考虑以下人员/人员概念/类模型:
As an example that illustrates how the derivation chain from concept via design to implementation works, consider the following model of a people/Person concept/class:
域模型是在软件工程项目的分析阶段生成的问题域的与解决方案无关的描述.术语概念模型"通常用作域模型"的同义词.域模型可能既包含对域状态结构的描述(在概念性信息模型中)，也包括对过程的描述(在概念性过程模型中).从某种意义上说，它们与解决任何系统设计选择或其他计算问题无关，它们是与解决方案无关或与计算无关"的.相反，他们专注于所考虑领域的主题专家的观点和语言.
Domain models are solution-independent descriptions of a problem domain produced in the analysis phase of a software engineering project. The term "conceptual model" is often used as a synonym of "domain model". A domain model may include both descriptions of the domain’s state structure (in conceptual information models) and descriptions of its processes (in conceptual process models). They are solution-independent, or ‘computation-independent’, in the sense that they are not concerned with making any system design choices or with other computational issues. Rather, they focus on the perspective and language of the subject matter experts for the domain under consideration.
在设计阶段，首先根据领域模型开发与平台无关的设计模型，作为给定软件工程问题的通用计算解决方案.同一域模型可以潜在地用于产生代表不同设计选择的许多(甚至根本上)不同的设计模型.然后，通过考虑许多实施问题，包括体系结构样式，要最大化的非功能质量标准(例如性能，适应性)和目标技术平台，从设计模型中得出一个或多个特定于平台的实施模型.
In the design phase, first a platform-independent design model, as a general computational solution to the given software engineering problem, is developed on the basis of the domain model. The same domain model can potentially be used to produce a number of (even radically) different design models representing different design choices. Then, by taking into consideration a number of implementation issues ranging from architectural styles, nonfunctional quality criteria to be maximized (e.g., performance, adaptability) and target technology platforms, one or more platform-specific implementation models are derived from the design model.
另请参阅开放获取书籍的各章信息建模和从信息设计模型中导出表模型.
See also the Open Access book chapters Information Modeling and Deriving a Table Model from an Information Design Model.
这篇关于领域类图和设计类图有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
