知识卡片
架构债产生非局部维护成本
架构债来自跨元素的设计关系,使修改和演进日益昂贵,比局部代码异味更难用单文件检查发现。不是所有违反原则都值得消除:为了性能或上市时机承受更高耦合可能是合理取舍。判断应结合源代码关系、版本共同变化和问题跟踪中的变更原因,避免把功能开发繁忙本身误称作坏债。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 管理架构债 · 查看原书依据
Architecture debt is typically more difficult to detect and more difficult to eradicate than code debt because it involves nonlocal concerns. The tools and methods that work well for discovering code debt—code inspections, code quality checkers, and so forth—typically do not work well for detecting architecture debt.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第23章《管理架构债》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch23.html)
- 结论依据:原文解释架构债来自跨元素的设计关系,使修改和演进日益昂贵,比局部代码异味更难用单文件检查发现;本章后续机制、例子与条件共同限定本卡,原书经验数字和前景不视为当前实测或现状。
- 原始内容:Architecture debt is typically more difficult to detect and more difficult to eradicate than code debt because it involves nonlocal concerns. The tools and methods that work well for discovering code debt—code inspections, code quality checkers, and so forth—typically do not work well for detecting architecture debt.