概念类图和详细类图有什么区别? [英] What is the difference between Conceptual Class Diagram and Detailed Class Diagram?

问题描述

谁能简单解释一下概念类图和详细类图之间的区别?

解决方案

虽然概念类图"表达了一个概念(领域)模型，但不清楚是什么您(或您的教授)的意思是详细类图":它可以指(独立于语言/平台的)设计模型或实现模型 类似于 C++ 类模型或 Java 类模型.

另见我对

作为说明从概念到设计到实现的派生链如何工作的示例，请考虑以下人员/人员概念/类的模型:

域模型是在软件工程项目的分析阶段产生的问题域的独立于解决方案的描述.术语概念模型"通常用作领域模型"的同义词.域模型可能包括域状态结构的描述(在概念信息模型中)和其过程的描述(在概念过程模型中).它们是独立于解决方案或独立于计算"的，因为它们不关心做出任何系统设计选择或其他计算问题.相反，他们专注于所考虑领域的主题专家的观点和语言.

在设计阶段，首先在领域模型的基础上开发一个平台无关的设计模型，作为给定软件工程问题的通用计算解决方案.相同的领域模型可以潜在地用于产生代表不同设计选择的许多(甚至根本上)不同的设计模型.然后，通过考虑一系列实现问题，从架构风格、要最大化的非功能质量标准(例如，性能、适应性)和目标技术平台，从设计模型中导出一个或多个平台特定的实现模型.

Can someone briefly explain the difference between a Conceptual Class Diagram and a Detailed Class Diagram?

解决方案

While a "Conceptual Class Diagram" expresses a conceptual (domain) model, it's not clear what you (or your professor) mean(s) with "Detailed Class Diagram": it could refer to a (language-/platform-independent) design model or to an implementation model like a C++ class model or a Java class model.

See also my answer to this related SO question.

The one-to-many relationships between conceptual models and design models, and between design models and implementation models are illustrated in the following Figure:

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.

这篇关于概念类图和详细类图有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！