知识卡片
分析模式要连同实现后果读
借用分析模式时,还要读它为何如此划分、曾遇到哪些实现问题,以及部署与长期维护会受什么影响。只抽出概念图而丢掉这些上下文,容易把“领域分析”与“可工作的设计”割裂,也难判断模式是否适用于当前系统。
原书引用 Fowler 会计规则案例,说明某些模型选择允许在运行中新增规则实例而无需重编译;这是所引案例的设计能力,不能推断所有分析模式都有热更新特性。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Chapter Eleven. Applying Analysis Patterns · 查看原书依据
Analysis patterns at their best can carry that kind of experience from other projects, combining model insights with extensive discussions of design directions and implementation consequences. To discuss model ideas out of that context makes them harder to apply and risks opening the deadly divide between analysis and design, which is antithetical to MODEL-DRIVEN DESIGN.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第83章《Chapter Eleven. Applying Analysis Patterns》(源文件:_epub-src/0321125215_ch11.html;单元01)
- 结论依据:原文强调好的分析模式携带跨项目的模型、设计方向与实现后果经验;脱离上下文会造成分析和设计割裂。
- 原始内容:Analysis patterns at their best can carry that kind of experience from other projects, combining model insights with extensive discussions of design directions and implementation consequences. To discuss model ideas out of that context makes them harder to apply and risks opening the deadly divide between analysis and design, which is antithetical to MODEL-DRIVEN DESIGN .