知识卡片
模块划分应表达领域概念
在模型驱动设计中,模块不仅是组织代码的技术容器,也属于模型的一部分。划分模块时应看领域概念如何聚合、哪些概念之间需要较少依赖,使高内聚和低耦合服务于业务理解。若仅按技术层或文件便利性分组,模块名与边界可能无法帮助团队理解领域。这里提出判断方向,具体模块设计方法留待本章后续小节。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Chapter Five. A Model Expressed in Software · 查看原书依据
The ideas of high cohesion and low coupling, often thought of as technical metrics, can be applied to the concepts themselves. In a MODEL-DRIVEN DESIGN, MODULES are part of the model, and they should reflect concepts in the domain.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第34章《Chapter Five. A Model Expressed in Software》(源文件:_epub-src/0321125215_ch05.html)
- 结论依据:原文把模块明确列为模型构件,要求其反映领域概念,并将高内聚、低耦合从纯技术度量转为领域概念间的设计判断。
- 原始内容:The ideas of high cohesion and low coupling, often thought of as technical metrics, can be applied to the concepts themselves. In a MODEL-DRIVEN DESIGN , MODULES are part of the model, and they should reflect concepts in the domain.