知识卡片
强度距离与影响面
共变性的代价取决于强度、局部性与影响数量。强关联留在同一模块内可能合理,跨模块或跨团队传播时应尽量转换为弱形式。封装的目标是将紧密关联聚到内部、减少跨边界关联,而非让每个内部元素也彼此无关。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
- · 强度距离与影响面
原书出处 · 1 处
- Evolutionary Architecture Topologies · 查看原书依据
Developers must consider strength and locality together. Stronger forms of connascence found within the same module represent less code smell than the same connascence spread apart. Degree The degree of connascence relates to the size of its impact—does it impact a few classes or many? Lesser degrees of connascence damage codebases less. In other words, having high dynamic connascence isn’t terrible if you have only
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第05章《Evolutionary Architecture Topologies》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch05.html;段落定位:Developers must consider strength and locality together)
- 结论依据:原文对“强度距离与影响面”的定义或案例,支撑“共变性的代价取决于强度、局部性与影响数量”的归纳。据其上下文,强关联留在同一模块内可能合理,跨模块或跨团队传播时应尽量转换为弱形式。
- 原始内容:Developers must consider strength and locality together. Stronger forms of connascence found within the same module represent less code smell than the same connascence spread apart. Degree The degree of connascence relates to the size of its impact—does it impact a few classes or many? Lesser degrees of connascence damage codebases less. In other words, having high dynamic connascence isn’t terrible if you have only