知识卡片
知识级视角揭示员工类型中混入的薪酬概念
原书示例续篇中,团队把受限编辑的员工类型和政策归入知识级,把日常维护的员工归入操作级(图16.21)。这一视角使“员工类型关联退休计划或薪酬”这句通用语言中的缺口显现:模型里没有独立的“薪酬”对象,相关规则混在员工类型里。
团队据此抽出 Payroll 及小时工/月薪薪酬类别(图16.22–16.23)。知识级本身不是必须保留的结构;它此时的价值是让概念混杂可见。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第16章|Knowledge Level · 查看原书依据
But that was not really a statement in the UBIQUITOUS LANGUAGE. There was no "payroll" in the model. They had spoken in the language they wanted, rather than the one they had. The concept of payroll was implicit in the model, lumped together with Employee Type. It hadn't been so obvious before the KNOWLEDGE LEVEL was separated out, and the very elements in that key phrase all appeared in the same level together . . . except one.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第131章《Knowledge Level》(源文件:_epub-src/0321125215_ch16lev1sec4.html)
- 结论依据:原书第二段示例通过知识级分隔发现缺失的Payroll概念,随后重构;图16.21–16.23已目视核对。
- 原始内容:But that was not really a statement in the UBIQUITOUS LANGUAGE. There was no "payroll" in the model. They had spoken in the language they wanted, rather than the one they had. The concept of payroll was implicit in the model, lumped together with Employee Type. It hadn't been so obvious before the KNOWLEDGE LEVEL was separated out, and the very elements in that key phrase all appeared in the same level together . . . except one.
- 转录说明:原卡术语和标点前的多余空格来自 EPUB 强调标签边界,已按可读正文规范转录;句中的 `. . .` 是原书原有省略。