知识卡片
航运项目显示迟发反馈会切断模型与实现的闭环
原书航运项目复盘:团队曾形成较深的核心模型与通用语言,但组织抵触迭代,内部可运行版本推出太晚。数据库性能问题暴露时,大家认为已无法再改基本模型,于是只优化代码,模型与实现渐行渐远。
项目后来仍替换了多个遗留系统并持续服务业务,且共同概念帮助团队集成;但各团队质量参差,模型驱动设计未成为共同文化。它是作者对具体项目的复盘,不表示“上线晚”总会产生同样结果。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Epilogues · 查看原书依据
A natural part of MODEL-DRIVEN DESIGN is the feedback from implementation problems to changes in the model, but by that time there was a perception that we were too far down the road to change the fundamental model.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第141章《Epilogues》(源文件:_epub-src/0321125215_art01lev1sec1.html)
- 结论依据:原文说明迟发布导致反馈晚、性能问题促使代码偏离模型,并记录系统仍提供业务价值的结果。
- 原始内容:But the company culture fiercely resisted iterative development, and we waited far too long to push out a working internal release. Therefore, problems were exposed at a late stage, when they were more risky and expensive to fix. At some point, we discovered specific aspects of the model were causing performance problems in the database. A natural part of MODEL-DRIVEN DESIGN is the feedback from implementation problems to changes in the model, but by that time there was a perception that we were too far down the road to change the fundamental model. Instead, changes were made to the code to make it more efficient, and its connection to the model was weakened. [...] But the loop was never closed between implementation and domain modeling. [...] Although reduced in scope, the project replaced several legacy systems. The whole was held together by a shared set of concepts, though most of the design was not very supple. It has itself largely fossilized into legacy now, years later, but it still serves the global business 24 hours a day.
- 转录说明:`[...]` 分别标出同段中略去的技术基础设施恢复经过,以及后续案例结果前的段落省略。