原书出处
Domain-Driven Design Tackling Complexity in the Heart of Software
76 原书第10章|Conceptual Contours
elationships in the current model and code, or does it echo some contour of the underlying domain?"
Find the conceptually meaningful unit of functionality, and the resulting design will be both flexible and understandable. For example, if an "addition" of two objects has a coherent meaning in the domain, then implement methods at that level. Don't break the add() into two steps. Don't proceed to the next step within the same operation.
On a slightly larger scale, each object should be a single complete concept, a "WHOLE VALUE."[1] [1
原书定位详情
来源:a19c7933-4eda-4176-aebd-30fe7e1ad292
正文位置:extracted/Domain-Driven Design Tackling Complexity in the Heart of Software/_epub-src/0321125215_ch10lev1sec4.html
EPUB SHA-256:3e81897e8809ae8135b32e0563f9858b3020c5f5128531655f6d8e3a21c679ce