知识卡片

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

理赔项目分开交付的实得与未得

理解等级:高级

原书的理赔软件项目实际经历中,团队原想把客服和理赔员所有功能合成一套系统,结果一年仍无成果。重新梳理需求后,把部分只需方便访问的报表和查询做成独立小应用,在菜单层聚合,较快交付了几项有用能力。

但主应用后来仍再次陷入停滞,最终留下的只有这些分开交付的小应用。这个案例支持“先剥离低集成价值功能”,不证明剩余主系统也因此成功。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 原书第14章|Separate Ways · 查看原书依据

      It could have gone that way, but unfortunately the team slipped back into old habits. They paralyzed themselves again. In the end, their only legacy turned out to be those small applications that had gone their SEPARATE WAYS.

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第110章《Separate Ways》(源文件:_epub-src/0321125215_ch14lev1sec9.html;单元01) - 结论依据:原文记述独立小应用迅速交付,也明确主应用后续再次停滞、仅小应用留存。 - 原始内容:It could have gone that way, but unfortunately the team slipped back into old habits. They paralyzed themselves again. In the end, their only legacy turned out to be those small applications that had gone their SEPARATE WAYS .