Domain-driven design: The Way to cope with software core complexity

Domain-driven design: The Way to cope with software core complexity

Author: Eric Evans
Translator: Chen Dafeng/Zhang zexin
Press: Tsinghua University Press
Publishing year: 2006-3-1
Page: 390
Pricing: 48.00
Frame loading: 185x260
ISBN: 9787302115762

Douban: http://book.douban.com/subject/1629512/
Dangdang: http://product.dangdang.com/product.aspx? Product_id = 9150450

 

Directory

Part I makes the domain model play a role
Chapter 2 Digest knowledge
1.1 factors for effective modeling
1.2 knowledge digestion
1.3 continuous learning
1.4 Design with rich knowledge
1.5 deep Model
Chapter 4 communication and language use
2.1 General Language
2.2 improve the model using dialogs
2.3 one team, one language
2.4 Documents and figures
2.4.1 written design documents
2.4.2 execution Basics
2.5 descriptive model
Chapter 4 bind models and Implementations
3.1 model-driven design
3.2 model creation and tool support
3.3 highlights: Why is model critical to users?
3.4 practical modeling personnel
Part II model-driven design building blocks
Chapter 2 Separation of fields
4.1 layered architecture
4.1.1 inter-layer connection
4.1.2 architecture framework
4.2 The model belongs to the Domain Layer
4.3 isolation of other types
Chapter 4 model description in Software
5.1 Association
5.2 entity (also called reference object)
5.2.1 entity modeling
5.2.2 Design Mark operation
5.3 Value Object
5.3.1 design value object
5.3.2 Design Association of included value objects
5.4 Service
5.4.1 service and separated domain layer
5.4.2 Granularity
5.4.3 Access Service
5.5 module (Package)
5.5.1 agile modules
5.5.2 infrastructure driver packaging defects
5.6 modeling paradigm
5.6.1 advantages of object paradigm
5.6.2 non-objects in the object world
5.6.3 use model-driven design in the hybrid paradigm
Chapter 1 lifecycle of a domain object
6.1 Aggregation
6.2 Factory
6.2.1 selection of factories and their application sites
6.2.2 only need to construct Functions
6.2.3 Interface Design
6.2.4 how to place the invariant Logic
6.2.5 physical factory and value object Factory
6.2.6 storage object Reconstruction
6.3 warehousing
6.3.1 query warehousing
6.3.2 understand the necessity of warehouse implementation
6.3.3 warehousing
6.3.4 work within the Framework
6.3.5 relationship with the factory
6.4 design objects for relational databases
Chapter 4 Language used: Extension example
7.1 Cargo Transportation System Overview
7.2 isolation: System Overview
7.3 object differentiation and Value Object
7.4 Association design in the transportation field
7.5 aggregation Boundary
7.6 select warehouse
7.7 scenario overview
7.7.1 application feature example: Changing the destination of a parcel
7.7.2 application feature example: duplicate business
7.8 create an object
7.8.1 cargo factory and constructor
7.8.2 Add a handling event
7.9 stop reconstruction: Another design of cargo Aggregation
7.10 module in the Transport Model
7.11 introduce new features: Quota check
7.11.1 connect two systems
7.11.2 improved model: Business Division
7.11.3 performance Adjustment
Conclusion 7.12
Part III reconstruction for deeper understanding
Chapter 2 breakthrough
8.1 breakthrough stories
8.1.1 unused Models
8.1.2 breakthrough
8.1.3 deeper Model
8.1.4 calm decision
8.1.5 results
8.2 time
8.3 focus on fundamentals
8.4 conclusion: a series of new understandings
Chapter 2 implicit concepts transformed into explicit concepts
......
Chapter 2 flexible design
Chapter 1 Application Analysis Mode
Chapter 2 link design patterns with models
Chapter 2 further understanding and Reconstruction
Part IV Strategic Design
Chapter 4 maintain model integrity
Chapter 2 Refining
Chapter 1 Large Scale Structure
Chapter 4 Strategic Design of Integrated Application
Chapter 2 Conclusion
Appendix A Model
Appendix B GLOSSARY
Appendix C references
Appendix D Relationship Diagram