知识卡片
知识级把可配置规则从日常业务对象中分离
当实体的角色、关系或行为规则会随组织而变,知识级用一组普通领域对象描述并约束另一组日常业务对象。前者保存可由授权用户调整的类型和政策,后者承担具体业务操作。这样既能配置变化,又不必把所有变化分支塞进每个业务对象。
它描述的是领域模型内部的规则,不是程序语言的反射元对象;也不追求任意规则都能表达。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第16章|Knowledge Level · 查看原书依据
KNOWLEDGE LEVEL untangles things when we need to let some part of the model itself be plastic in the user's hands yet constrained by a broader set of rules. It addresses requirements for software with configurable behavior, in which the roles and relationships among ENTITIES must be changed at installation or even at runtime.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第131章《Knowledge Level》(源文件:_epub-src/0321125215_ch16lev1sec4.html)
- 结论依据:原文定义知识级并限定其领域用途;模式陈述要求将描述和约束基础模型的对象单独组成一组。
- 原始内容:K NOWLEDGE LEVEL untangles things when we need to let some part of the model itself be plastic in the user's hands yet constrained by a broader set of rules. It addresses requirements for software with configurable behavior, in which the roles and relationships among ENTITIES must be changed at installation or even at runtime.
- 转录说明:原 EPUB 以普通首字母加后续强调标签拼出 `KNOWLEDGE`;上行纯文本抽取后的 `K NOWLEDGE` 是标签边界。