原书出处
Domain-Driven Design Tackling Complexity in the Heart of Software
131 原书第16章|Knowledge Level
n't put her finger on it: An Employee Type is assigned to either Retirement Plan or either payroll.
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.
Based on this insight, she refactored again to a model that does support that statement. The need f
原书定位详情
来源:a19c7933-4eda-4176-aebd-30fe7e1ad292
正文位置:extracted/Domain-Driven Design Tackling Complexity in the Heart of Software/_epub-src/0321125215_ch16lev1sec4.html
EPUB SHA-256:3e81897e8809ae8135b32e0563f9858b3020c5f5128531655f6d8e3a21c679ce