知识卡片

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

核心标记应落在主要模型载体

理解等级:高级

除了单独的提炼文档,也可在团队日常查看的主要模型载体中标出核心元素:UML图可用构造型,代码为主的团队可用注释或开发工具。目标是让开发者迅速辨认哪些元素属于核心、哪些不属于,而不是再建一套详尽说明。

这种标记投入小、维护负担低,但前提是模型切分足够细,能看出各部分贡献;它本身不会改变模型或代码结构。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 原书第15章|Highlighted Core · 查看原书依据

      The CORE DOMAIN is now clearly visible to those working with the model, with a fairly small effort and low maintenance, at least to the extent that the model is factored fine enough to distinguish the contributions of parts.

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第121章《Highlighted Core》(源文件:_epub-src/0321125215_ch15lev1sec5.html;单元03) - 结论依据:原文列举 UML 构造型、代码注释和工具标记,并要求开发者无需费力即可识别核心内外。 - 原始内容:This technique is not specific to object diagrams on paper. A team that uses UML diagrams extensively could use a "stereotype" to identify core elements. A team that uses the code as the sole repository of the model might use comments, maybe structured as Java Doc, or might use some tool in its development environment. The particular technique doesn't matter, as long as a developer can effortlessly see what is in and what is out of the CORE DOMAIN. [...] Flag the elements of the CORE DOMAIN within the primary repository of the model, without particularly trying to elucidate its role. Make it effortless for a developer to know what is in or out of the CORE. The CORE DOMAIN is now clearly visible to those working with the model, with a fairly small effort and low maintenance, at least to the extent that the model is factored fine enough to distinguish the contributions of parts. [...] Although the VISION STATEMENT and HIGHLIGHTED CORE inform and guide, they do not actually modify the model or the code itself. - 转录说明:两处 `[...]` 分别标明模式陈述前的过渡及后续过程工具段落的省略;“低维护”受模型切分足够细的条件限制。