← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 1971.o.1.b.1.a.2.a.3

大型结构是跨模块的概念规则而非代码包

理解等级:高级

卫星仿真项目里的“层”不是一个个代码模块,而是约束模块、对象边界及相互关系的整体概念规则。大型结构一般也如此:用跨设计的角色、关系或规则,解释局部元素在整体中的位置,并协调不同开发者的判断。

因此它可跨多个限界上下文,也未必能完整画成 UML 或直接对应代码构件。图16.1列举系统隐喻、责任层、知识层次等后续模式;本章引言只提出全局组织原则,尚未逐一验证各模式的适用性。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第127章《Chapter Sixteen. Large-Scale Structure》(源文件:_epub-src/0321125215_ch16.html;单元01–02) - 结论依据:原文明确项目层次不属于代码产物,并定义大型结构为全系统规则与角色关系;图16.1列出后续模式。 - 原始内容:These layers were not MODULES or any other artifact in the code. They were an overarching set of rules that constrained the boundaries and relationships of any particular MODULE or object throughout the design, even at interfaces with other systems. [...] A "large-scale structure" is a language that lets you discuss and understand the system in broad strokes. A set of high-level concepts or rules, or both, establishes a pattern of design for an entire system. This organizing principle can guide design as well as aid understanding. It helps coordinate independent work because there is a shared concept of the big picture: how the roles of various parts shape the whole. [...] Structure may be confined to one BOUNDED CONTEXT but will usually span more than one, providing the conceptual organization to hold together all the teams and subsystems involved in the project. [...] You can't represent most large-scale structures in UML, and you don't need to. - 转录说明:`[...]` 分隔案例、定义及后续边界段落;图16.1中的模式名称已另经原图目视核对。