← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 1971.o.1.c.1.e

把隐含概念显化为模型构件

理解等级:中级

领域讨论或现有设计常暗示某个重要概念,却没有在模型中清楚表示。原书把“识别线索→用对象或关系显化→反复调整职责、关联和名称”视为走向深模型的起点;显化时可以先粗糙表达,再随理解修订。第67章的金融 Transaction 是书中实例,但不是每个缺失概念都必须建成实体;也可能需要关系或其他模型构件。突破有时立刻出现,更多时候发生在多轮细化之后。参见[[反复出现的业务词可能揭示缺失概念]]。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Chapter Nine. Making Implicit Concepts Explicit · 查看原书依据

      Many transformations of domain models and the corresponding code happen when developers recognize a concept that has been hinted at in discussion or present implicitly in the design, and they then represent it explicitly in the model with one or more objects or relationships. Occasionally, this transformation of a formerly implicit concept into an explicit one is a breakthrough that leads to a deep model.

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第68章《Chapter Nine. Making Implicit Concepts Explicit》(源文件:_epub-src/0321125215_ch09.html) - 结论依据:原文将讨论与设计中的隐含概念显化为对象或关系,作为后续多轮职责、关联和名称调整的起点。 - 原始内容:Many transformations of domain models and the corresponding code happen when developers recognize a concept that has been hinted at in discussion or present implicitly in the design, and they then represent it explicitly in the model with one or more objects or relationships. Occasionally, this transformation of a formerly implicit concept into an explicit one is a breakthrough that leads to a deep model.