知识卡片

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

核心提炼文档可触发协商与通知

理解等级:高级

若一次模型变更会改动核心提炼文档,就说明它可能改变了核心元素、关系或核心边界。原书建议这类变更先与团队协商,完成后及时让全员知晓并更新文档。

只涉及核心外部或未写入文档的细节,可按日常集成处理,让开发者保持自主。这个区分是概念影响的沟通信号:通用组件改动可能影响大量代码,却不一定改变核心领域含义。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第121章《Highlighted Core》(源文件:_epub-src/0321125215_ch15lev1sec5.html;单元03) - 结论依据:原文把“是否影响核心提炼文档”作为咨询与同步的触发条件,并区分代码波及面与核心概念变更。 - 原始内容:Changes to widely used generic elements may require a lot of code updating, but they still shouldn't create the conceptual shift that CORE changes do. [...] Use the distillation document as a guide. When developers realize that the distillation document itself requires change to stay in sync with their code or model change, then consultation is called for. Either they are fundamentally changing the CORE DOMAIN elements or relationships, or they are changing the boundaries of the CORE, including or excluding something different. Dissemination of the model change to the whole team is necessary by whatever communication channels the team uses, including distribution of a new version of the distillation document. [...] Changes outside the CORE or to details not included in the distillation document can be integrated without consultation or notification and will be encountered by other members in the course of their work. Then the developers have the full autonomy that XP suggests. - 转录说明:两处 `[...]` 分别标明通用元素判断后的段落转换,以及团队协商触发规则的中间重述段落省略;原 EPUB 强调标签边界造成的术语前空格已规范转录。