知识卡片
优先级结合业务影响与成本
按业务影响和实施成本对每个组件分类:低价值的考虑退役或暂缓,高价值低成本的优先改进,高价值高成本的规划重写或分期改造。评估要站在全组织视角,防止单团队优化替代业务优先级。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
原书出处
参考来源
- 位置:《Principles of Software Architecture Modernization》第5章《Assessments》(源文件:`_epub-src/OPS/ch05.xhtml`,归一化正文 [67116:71337))
- 结论依据:原文以业务影响与投入矩阵区分退役、速赢重构和高投入重写,并要求从整体公司而非局部团队判断。
- 原始内容:Fast decommission: Components with low business impact and low effort to migrate. You would still decommission or ignore these systems given their low business value; sure you could consider refactoring or even a rewrite, but if the business value is low, what’s the point? Compared with the bottom right, our systems require less effort, so you might be able to afford it.