知识卡片
扁平化可合并也可拆开
去除孤儿类有两种方向:把下级功能并回父节点,使父节点成为唯一叶组件;或把父节点源码按职责移入新叶组件,使父节点只保留领域含义。调查逻辑简单少变化,适合把模板并回;工单分配复杂且频繁改动,则保留分配、路由并拆出维护、完成和共享组件。选择依职责与变化方式,而非统一目录深度。
相关:[[叶节点界定组件]]。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 基于组件的分解模式 · 查看原书依据
Alternatively, flattening could also be applied by taking the source code in ss.survey and applying functional decomposition or domain-driven design to identify separate functional areas within the root namespace, thus forming components from those functional areas.
参考来源
- 位置:《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)
- 结论依据:原文的定义、比较或案例支持“去除孤儿类有两种方向:把下级功能并回父节点,使父节点成为唯一叶组件;或把父节点源码按职责移入新叶组件,使父节点只保留领域含义”;正文据此解释其用途与适用边界。
- 原始内容:Alternatively, flattening could also be applied by taking the source code in ss.survey and applying functional decomposition or domain-driven design to identify separate functional areas within the root namespace, thus forming components from those functional areas.