知识卡片
业务词与设计缺席是概念线索
领域专家反复使用某个词,甚至纠正开发者的说法,而代码和模型没有它时,应追问该词指向的业务规则、关系和用途。它只是发现线索,不等于“名词必建对象”;需通过对话、场景和重构验证。原书假设货运案例中的 *Itinerary*(行程)原先只隐含在报表及数据库记录里,后来才被识别为订舱与操作支持共用的概念。参见[[行程对象统一订舱与操作接口]]。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第09章|Digging Out Concepts · 查看原书依据
Listen to the language the domain experts use. Are there terms that succinctly state something complicated? Are they correcting your word choice (perhaps diplomatically)? Do the puzzled looks on their faces go away when you use a particular phrase? These are hints of a concept that might benefit the model. This is not the old "nouns are objects" notion.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第69章《Digging Out Concepts》,Listen to Language(源文件:_epub-src/0321125215_ch09lev1sec1.html)
- 结论依据:原文将词汇缺席视为模型改进机会,同时否定机械的“名词即对象”规则。
- 原始内容:Listen to the language the domain experts use. Are there terms that succinctly state something complicated? Are they correcting your word choice (perhaps diplomatically)? Do the puzzled looks on their faces go away when you use a particular phrase? These are hints of a concept that might benefit the model. This is not the old "nouns are objects" notion.