知识卡片
交接后的深模型可被继承也可被更深模型替换
原书工具软件案例:初始团队交接时留下测试集、提炼文档和通用语言,后续团队借此理解组合能力。新需求出现后,继任者发现原模型局限,并凭累积的领域知识大幅改写模型。
作者把这种替换视为设计继续服务用户的表现:深模型帮助团队看清问题,柔性设计让改动成为可能。衡量交接成功不应要求原始设计永不改变。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Epilogues · 查看原书依据
The success of a design is not necessarily marked by its stasis. Take a system people depend on, make it opaque, and it will live forever as untouchable legacy. A deep model allows clear vision that can yield new insight, while a supple design facilitates ongoing change. The model they came up with was deeper, better aligned with the real concerns of the users. Their design solved real problems.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第141章《Epilogues》(源文件:_epub-src/0321125215_art01lev1sec1.html)
- 结论依据:原文记录交接材料、通用语言延续及继任团队因新洞察改造设计的过程。
- 原始内容:The success of a design is not necessarily marked by its stasis. Take a system people depend on, make it opaque, and it will live forever as untouchable legacy. A deep model allows clear vision that can yield new insight, while a supple design facilitates ongoing change. The model they came up with was deeper, better aligned with the real concerns of the users. Their design solved real problems.