知识卡片
场景追问促成知识消化
知识消化是把领域专家的经验变成团队可讨论、可运行的模型。原书 PCB 工具案例把[[领域建模需要持续协作]]落实为一条往返路径:
- 围绕一个具体功能画出对象交互,让专家纠正术语、连接关系和遗漏的业务规则。
- 暂时排除与该功能无关的细节,形成足以运行场景的初始模型。
- 用简短原型计算真实业务行为,再让专家根据结果指出模型的不足。
- 将新认识同时写回模型和代码。
这比让专家一次性列完软件功能更能暴露隐含知识;原型中的演示结果仍只是模型反馈,不能证明完整产品已经可用。
原书项目的后续结果:团队后来认定探针模拟的开发优先级低,放弃了该功能及专用模型部分;关键模型元素得以保留,早期探索还启动了共同学习、共享语言和实现反馈。这说明这次探索即使没有留下原型功能,仍有知识价值;不能由此推断所有原型都应被舍弃。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Chapter One. Crunching Knowledge · 查看原书依据
Even so, the early work was essential. Key model elements were retained, but more important, that work set in motion the process of knowledge crunching that made all subsequent work effective: the knowledge gained by team members, developers, and domain experts alike; the beginnings of a shared language; and the closing of a feedback loop through implementation.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第10章《Chapter One. Crunching Knowledge》及第13章《Continuous Learning》(源文件:_epub-src/0321125215_ch01.html;_epub-src/0321125215_ch01lev1sec3.html)
- 结论依据:第10项先记专家纠正术语与关系,团队缩小到探针模拟并用原型反馈改变模型与代码;第13项明确交代项目后来放弃该功能和部分模型,但保留关键元素并启动共同学习、语言及实现反馈。步骤依原书探索过程整理,后续结果仅属于原书这个项目。
- 原始内容:The concreteness of this prototype made clearer to the domain experts what the model meant and how it related to the functioning software. ... In fact, our team eventually discovered that the probe simulation was a low priority for development, and the feature was eventually dropped altogether. ... Even so, the early work was essential. Key model elements were retained, but more important, that work set in motion the process of knowledge crunching that made all subsequent work effective: the knowledge gained by team members, developers, and domain experts alike; the beginnings of a shared language; and the closing of a feedback loop through implementation.