知识卡片
重写与重构按组件决策
重写与原地重构不是全系统一次性二选一。逐组件比较业务关键性、变化频率、技术寿命、增长机会和实施成本,再决定保留、改造或重建;成熟旧代码可能含有长期验证过的规则。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
原书出处
参考来源
- 位置:《Principles of Software Architecture Modernization》第5章《Assessments》(源文件:`_epub-src/OPS/ch05.xhtml`,归一化正文 [20962:25173))
- 结论依据:原文提出重构可行性维度,包括业务关键性、变化率、EOL、增长与技术投入,并说明通常部分重写、部分重构。
- 原始内容:To judge whether a refactor is possible, here are some dimensions you can take into account: Criticality : How important is this system or service for business differentiation and continuity? If it is not important, is it worth rewriting? Rate of business change : How often is the business requesting changes or new features to this component: low, medium, or high frequency?