知识卡片
共享功能检索需要人工判断
相同命名空间叶子名、多个组件共用类或继承结构,都是寻找重复领域功能的线索;例如多处使用SMTPConnection可能暗示分散的邮件通知。自动检查只能发现候选,不能证明语义相同;确认不是重复逻辑的calculate、validate等应进入排除清单,避免持续误报。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 基于组件的分解模式 · 查看原书依据
When a common ending namespace node name is found between two or more components, the architect is alerted and can analyze the functionality to determine if it is common domain logic. So that the same alert isn’t continuously sent as a “false positive,” an exclusion file can be used to store those namespaces that have common ending node names but are not deemed common domain logic (such as multiple namespaces ending in .calculate or .validate).
参考来源
- 位置:《Software Architecture: The Hard Parts》第5章《基于组件的分解模式》(来源项目:book-sources;源文件:extracted/Software Architecture The Hard Parts Modern Trade-Off Analyses for Distributed Architectures (Neal Ford, Mark Richards, Pramod Sadalage etc.)/_epub-src/OEBPS/ch05.xhtml)
- 结论依据:原文的定义、比较或案例支持“相同命名空间叶子名、多个组件共用类或继承结构,都是寻找重复领域功能的线索;例如多处使用SMTPConnection可能暗示分散的邮件通知”;正文据此解释其用途与适用边界。
- 原始内容:When a common ending namespace node name is found between two or more components, the architect is alerted and can analyze the functionality to determine if it is common domain logic. So that the same alert isn’t continuously sent as a “false positive,” an exclusion file can be used to store those namespaces that have common ending node names but are not deemed common domain logic (such as multiple namespaces ending in .calculate or .validate).