知识卡片
范式选择要兼顾团队与工具
选择建模范式,除了看它能否表达领域概念,还要看团队和领域专家能否理解、实现工具是否成熟、能否与现有技术集成。范式太难掌握,共同语言会失去依托;工具和实践不成熟,团队可能被迫把资源投入基础设施研发。原书写作时以面向对象范式为多数项目的稳妥起点,这是当时的生态判断,不意味着所有领域都适合对象模型。参见[[建模范式支撑模型直译]]。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第05章|Modeling Paradigms · 查看原书依据
If a modeling paradigm is too esoteric, not enough developers will master it, and they will use it badly. If the nontechnical members of the team can't grasp at least the rudiments of the paradigm, they will not understand the model, and the UBIQUITOUS LANGUAGE will be lost.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第42章《原书第05章|Modeling Paradigms》(源文件:_epub-src/0321125215_ch05lev1sec6.html)
- 结论依据:原文把可理解性、工具与基础设施成熟度、集成和人才实践列为对象范式占优的原因,同时承认数学或全局逻辑领域可能不适配对象。
- 原始内容:If a modeling paradigm is too esoteric, not enough developers will master it, and they will use it badly. If the nontechnical members of the team can't grasp at least the rudiments of the paradigm, they will not understand the model, and the UBIQUITOUS LANGUAGE will be lost. ... Without mature infrastructure and tool support, a project can get sidetracked into technological R&D, delaying and diverting resources away from application development and introducing technical risks.