Home > Store

Domain-Driven Design: Tackling Complexity in the Heart of Software

Domain-Driven Design: Tackling Complexity in the Heart of Software

eBook (Watermarked)

  • Your Price: $47.99
  • List Price: $59.99
  • Includes EPUB, MOBI, and PDF
  • About eBook Formats
  • This eBook includes the following formats, accessible from your Account page after purchase:

    ePub EPUB The open industry format known for its reflowable content and usability on supported mobile devices.

    MOBI MOBI The eBook format compatible with the Amazon Kindle and Amazon Kindle applications.

    Adobe Reader PDF The popular standard, used most often with the free Adobe® Reader® software.

    This eBook requires no passwords or activation to read. We customize your eBook by discreetly watermarking it with your name, making it uniquely yours.

Also available in other formats.

Register your product to gain access to bonus material or receive a coupon.

Description

  • Copyright 2012
  • Edition: 1st
  • eBook (Watermarked)
  • ISBN-10: 0-13-305296-6
  • ISBN-13: 978-0-13-305296-1

“Eric Evans has written a fantastic book on how you can make the design of your software match your mental model of the problem domain you are addressing.

“His book is very compatible with XP. It is not about drawing pictures of a domain; it is about how you think of it, the language you use to talk about it, and how you organize your software to reflect your improving understanding of it. Eric thinks that learning about your problem domain is as likely to happen at the end of your project as at the beginning, and so refactoring is a big part of his technique.

“The book is a fun read. Eric has lots of interesting stories, and he has a way with words. I see this book as essential reading for software developers—it is a future classic.”

Ralph Johnson, author of Design Patterns

“If you don’t think you are getting value from your investment in object-oriented programming, this book will tell you what you’ve forgotten to do.

“Eric Evans convincingly argues for the importance of domain modeling as the central focus of development and provides a solid framework and set of techniques for accomplishing it. This is timeless wisdom, and will hold up long after the methodologies du jour have gone out of fashion.”

Dave Collins, author of Designing Object-Oriented User Interfaces

“Eric weaves real-world experience modeling—and building—business applications into a practical, useful book. Written from the perspective of a trusted practitioner, Eric’s descriptions of ubiquitous language, the benefits of sharing models with users, object life-cycle management, logical and physical application structuring, and the process and results of deep refactoring are major contributions to our field.”

Luke Hohmann, author of Beyond Software Architecture

“This book belongs on the shelf of every thoughtful software developer.”

Kent Beck

“What Eric has managed to capture is a part of the design process that experienced object designers have always used, but that we have been singularly unsuccessful as a group in conveying to the rest of the industry. We've given away bits and pieces of this knowledge...but we've never organized and systematized the principles of building domain logic. This book is important.”

Kyle Brown, author of Enterprise Java™ Programming with IBM® WebSphere®

The software development community widely acknowledges that domain modeling is central to software design. Through domain models, software developers are able to express rich functionality and translate it into a software implementation that truly serves the needs of its users. But despite its obvious importance, there are few practical resources that explain how to incorporate effective domain modeling into the software development process.

Domain-Driven Design fills that need. This is not a book about specific technologies. It offers readers a systematic approach to domain-driven design, presenting an extensive set of design best practices, experience-based techniques, and fundamental principles that facilitate the development of software projects facing complex domains. Intertwining design and development practice, this book incorporates numerous examples based on actual projects to illustrate the application of domain-driven design to real-world software development.

Readers learn how to use a domain model to make a complex development effort more focused and dynamic. A core of best practices and standard patterns provides a common language for the development team. A shift in emphasis—refactoring not just the code but the model underlying the code—in combination with the frequent iterations of Agile development leads to deeper insight into domains and enhanced communication between domain expert and programmer. Domain-Driven Design then builds on this foundation, and addresses modeling and design for complex systems and larger organizations.Specific topics covered include:

  • Getting all team members to speak the same language
  • Connecting model and implementation more deeply
  • Sharpening key distinctions in a model
  • Managing the lifecycle of a domain object
  • Writing domain code that is safe to combine in elaborate ways
  • Making complex code obvious and predictable
  • Formulating a domain vision statement
  • Distilling the core of a complex domain
  • Digging out implicit concepts needed in the model
  • Applying analysis patterns
  • Relating design patterns to the model
  • Maintaining model integrity in a large system
  • Dealing with coexisting models on the same project
  • Organizing systems with large-scale structures
  • Recognizing and responding to modeling breakthroughs

With this book in hand, object-oriented developers, system analysts, and designers will have the guidance they need to organize and focus their work, create rich and useful domain models, and leverage those models into quality, long-lasting software implementations.

Sample Content

Table of Contents



Foreword.


Preface.


Acknowledgments.

I. PUTTING THE DOMAIN MODEL TO WORK.

1. Crunching Knowledge.

Ingredients of Effective Modeling.

Knowledge Crunching.

Continuous Learning.

Knowledge-Rich Design.

Deep Models.

2. Communication and the Use of Language.

UBIQUITOUS LANGUAGE.

Modeling Out Loud.

One Team, One Language.

Documents and Diagrams.

Written Design Documents.

Executable Bedrock.

Explanatory Models.

3. Binding Model and Implementation.

MODEL-DRIVEN DESIGN.

Modeling Paradigms and Tool Support.

Letting the Bones Show: Why Models Matter to Users.

HANDS-ON MODELERS.

II. THE BUILDING BLOCKS OF A MODEL-DRIVEN DESIGN.

4. Isolating the Domain.

LAYERED ARCHITECTURE.

Relating the Layers.

Architectural Frameworks.

The Domain Layer Is Where the Model Lives.

THE SMART UI “ANTI-PATTERN”

Other Kinds of Isolation.

5. A Model Expressed in Software.

Associations.

ENTITIES (A.K.A. REFERENCE OBJECTS).

Modeling ENTITIES.

Designing the Identity Operation.

VALUE OBJECTS.

Designing VALUE OBJECTS.

Designing Associations That Involve VALUE OBJECTS.

SERVICES.

SERVICES and the Isolated Domain Layer.

Granularity.

Access to SERVICES.

MODULES (A.K.A. PACKAGES).

Agile MODULES.

The Pitfalls of Infrastructure-Driven Packaging.

Modeling Paradigms.

Why the Object Paradigm Predominates.

Nonobjects in an Object World.

Sticking with MODEL-DRIVEN DESIGN When Mixing Paradigms.

6. The Life Cycle of a Domain Object.

AGGREGATES.

FACTORIES.

Choosing FACTORIES and Their Sites.

When a Constructor Is All You Need.

Designing the Interface.

Where Does Invariant Logic Go?

ENTITY FACTORIES Versus VALUE OBJECT FACTORIES.

Reconstituting Stored Objects.

REPOSITORIES.

Querying a REPOSITORY.

Client Code Ignores REPOSITORY Implementation; Developers Do Not.

Implementing a REPOSITORY.

Working Within Your Frameworks.

The Relationship with FACTORIES.

Designing Objects for Relational Databases.

7. Using the Language: An Extended Example.

Introducing the Cargo Shipping System.

Isolating the Domain: Introducing the Applications.

Distinguishing ENTITIES and VALUE OBJECTS.

Role and Other Attributes.

Designing Associations in the Shipping Domain.

AGGREGATE Boundaries.

Selecting REPOSITORIES.

Walking Through Scenarios.

Sample Application Feature: Changing the Destination of a Cargo.

Sample Application Feature: Repeat Business.

Object Creation.

FACTORIES and Constructors for Cargo.

Adding a Handling Event.

Pause for Refactoring: An Alternative Design of the Cargo AGGREGATE.

MODULES in the Shipping Model.

Introducing a New Feature: Allocation Checking.

Connecting the Two Systems.

Enhancing the Model: Segmenting the Business.

Performance Tuning.

A Final Look.

III. REFACTORING TOWARD DEEPER INSIGHT.

8. Breakthrough.

Story of a Breakthrough.

A Decent Model, and Yet….

The Breakthrough.

A Deeper Model.

A Sobering Decision.

The Payoff.

Opportunities.

Focus on Basics.

Epilogue: A Cascade of New Insights.

9. Making Implicit Concepts Explicit.

Digging Out Concepts.

Listen to Language.

Scrutinize Awkwardness.

Contemplate Contradictions.

Read the Book.

Try, Try Again.

How to Model Less Obvious Kinds of Concepts.

Explicit Constraints.

Processes as Domain Objects.

SPECIFICATION

Applying and Implementing SPECIFICATION.

10. Supple Design.

INTENTION-REVEALING INTERFACES.

SIDE-EFFECT-FREE FUNCTIONS.

ASSERTIONS.

CONCEPTUAL CONTOURS.

STANDALONE CLASSES.

CLOSURE OF OPERATIONS.

DECLARATIVE DESIGN.

Domain-Specific Languages.

A Declarative Style of Design.

Extending SPECIFICATIONS in a Declarative Style.

Angles of Attack.

Carve Off Subdomains.

Draw on Established Formalisms, When You Can.

11. Applying Analysis Patterns.
12. Relating Design Patterns to the Model.

STRATEGY (A.K.A. POLICY).

COMPOSITE.

Why Not FLYWEIGHT?

13. Refactoring Toward Deeper Insight.

Initiation.

Exploration Teams.

Prior Art.

A Design for Developers.

Timing.

Crisis as Opportunity.

IV. STRATEGIC DESIGN.

14. Maintaining Model Integrity.

BOUNDED CONTEXT.

Recognizing Splinters Within a BOUNDED CONTEXT

CONTINUOUS INTEGRATION.

CONTEXT MAP.

Testing at the CONTEXT Boundaries.

Organizing and Documenting CONTEXT MAPS.

Relationships Between BOUNDED CONTEXTS.

SHARED KERNEL.

CUSTOMER/SUPPLIER DEVELOPMENT TEAMS.

CONFORMIST.

ANTICORRUPTION LAYER.

Designing the Interface of the ANTICORRUPTION LAYER.

Implementing the ANTICORRUPTION LAYER.

A Cautionary Tale.

SEPARATE WAYS.

OPEN HOST SERVICE.

PUBLISHED LANGUAGE.

Unifying an Elephant.

Choosing Your Model Context Strategy.

Team Decision or Higher.

Putting Ourselves in Context.

Transforming Boundaries.

Accepting That Which We Cannot Change: Delineating the External Systems.

Relationships with the External Systems.

The System Under Design.

Catering to Special Needs with Distinct Models.

Deployment.

The Trade-off.

When Your Project Is Already Under Way.

Transformations.

Merging CONTEXTS: SEPARATE WAYS—SHARED KERNEL.

Merging CONTEXTS: SHARED KERNEL—CONTINUOUS INTEGRATION.

Phasing Out a Legacy System.

OPEN HOST SERVICE—PUBLISHED LANGUAGE.

15. Distillation.

CORE DOMAIN.

Choosing the CORE.

Who Does the Work?

An Escalation of Distillations.

GENERIC SUBDOMAINS.

Generic Doesn't Mean Reusable.

Project Risk Management.

DOMAIN VISION STATEMENT.

HIGHLIGHTED CORE.

The Distillation Document.

The Flagged CORE.

The Distillation Document as Process Tool.

COHESIVE MECHANISMS.

GENERIC SUBDOMAIN Versus COHESIVE MECHANISM.

When a MECHANISM Is Part of the CORE DOMAIN.

Distilling to a Declarative Style.

SEGREGATED CORE.

The Costs of Creating a SEGREGATED CORE.

Evolving Team Decision.

ABSTRACT CORE.

Deep Models Distill.

Choosing Refactoring Targets.

16. Large-Scale Structure.

EVOLVING ORDER.

SYSTEM METAPHOR.

The “Naive Metaphor” and Why We Don't Need It.

RESPONSIBILITY LAYERS.

Choosing Appropriate Layers.

KNOWLEDGE LEVEL.

PLUGGABLE COMPONENT FRAMEWORK.

How Restrictive Should a Structure Be?

Refactoring Toward a Fitting Structure.

Minimalism.

Communication and Self-Discipline.

Restructuring Yields Supple Design.

Distillation Lightens the Load.

17. Bringing the Strategy Together.

Combining Large-Scale Structures and BOUNDED CONTEXTS.

Combining Large-Scale Structures and Distillation.

Assessment First.

Who Sets the Strategy?

Emergent Structure from Application Development.

A Customer-Focused Architecture Team.

Six Essentials for Strategic Design Decision Making.

The Same Goes for the Technical Frameworks.

Beware the Master Plan.

Conclusion.
Appendix: The Use of Patterns in This Book.
Glossary.
References.
Photo Credits.
Index. 0321125215T08272003

Updates

Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020