原书出处
Domain-Driven Design Tackling Complexity in the Heart of Software
123 原书第15章|Segregated Core
tillation document). Move related classes to a new MODULE, named for the concept that relates them.
Refactor code to sever data and functionality that are not directly expressions of the concept. Put the removed aspects into (possibly new) classes in other packages. Try to place them with conceptually related tasks, but don't waste too much time being perfect. Keep focused on scrubbing the CORE subdomain and making the references from it to other packages explicit and self-explanatory. Refactor the newly SEGREGATED CORE MODULE to make its relationships and interactions simpler and more communicative, and to minimize and clarify its relationships with other MODULES. (This becomes an ongoing refactoring objective.) Repeat with another CORE subdomain until the SEGREGATED CORE is complete.
The Costs of Creating a SEGREGATED CORE Segregating the CORE will sometimes make relationships with
原书定位详情
来源:a19c7933-4eda-4176-aebd-30fe7e1ad292
正文位置:extracted/Domain-Driven Design Tackling Complexity in the Heart of Software/_epub-src/0321125215_ch15lev1sec7.html
EPUB SHA-256:3e81897e8809ae8135b32e0563f9858b3020c5f5128531655f6d8e3a21c679ce