知识卡片
图示聚焦关键概念
模型图适合帮助团队讨论关键对象及其关系,三到五个对象的简图可以随思想实验改动。试图用 UML 画出全部实现对象,会淹没关键概念,却仍难说明对象的含义、职责和约束。应选取理解设计所需的局部图,配合自然语言解释;实现细节由代码承载。图是沟通模型的工具,不等于模型本身。参见 [[共同语言贯穿交付媒介]]。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第02章|Documents and Diagrams · 查看原书依据
In other words, a UML diagram cannot convey two of the most important aspects of a model: the meaning of the concepts it represents, and what the objects are meant to do.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第20章《原书第02章|Documents and Diagrams》(源文件:_epub-src/0321125215_ch02lev1sec4.html)
- 结论依据:原文建议用三到五个核心对象的简图支撑讨论,同时指出完整对象图信息过载,却无法表达概念含义和对象职责,最终要求选择性图示并以文字、代码补足。
- 原始内容:Sketch a diagram of three to five objects central to the issue at hand, and everyone can stay focused. ... In other words, a UML diagram cannot convey two of the most important aspects of a model: the meaning of the concepts it represents, and what the objects are meant to do. ... Always remember that the model is not the diagram .