Op werkdagen voor 23:00 besteld, morgen in huis Gratis verzending vanaf €20

Domain-Driven Design

Tackling Complexity in the Heart of Software

Specificaties
E-book, blz. | Engels
Pearson Education | e druk, 2021
ISBN13: 9780132181266
Rubricering
Juridisch :
Pearson Education e druk, 2021 9780132181266
Verwachte levertijd ongeveer 9 werkdagen

Samenvatting

“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.

Specificaties

ISBN13:9780132181266
Taal:Engels
Bindwijze:e-book

Inhoudsopgave

<br> <br> Foreword. <br> <br> <br> Preface. <br> <br> <br> Acknowledgments. <br> <p> I. PUTTING THE DOMAIN MODEL TO WORK. </p> <div style="margin-left: 0.2in;"> 1. Crunching Knowledge. </div> <br> <p> </p> <div style="margin-left: 0.4in;"> Ingredients of Effective Modeling. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Knowledge Crunching. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Continuous Learning. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Knowledge-Rich Design. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Deep Models. </div> <p></p> <div style="margin-left: 0.2in;"> 2. Communication and the Use of Language. </div> <br> <p> </p> <div style="margin-left: 0.4in;"> UBIQUITOUS LANGUAGE. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Modeling Out Loud. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> One Team, One Language. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Documents and Diagrams. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Written Design Documents. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Executable Bedrock. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Explanatory Models. </div> <p></p> <div style="margin-left: 0.2in;"> 3. Binding Model and Implementation. </div> <br> <p> </p> <div style="margin-left: 0.4in;"> MODEL-DRIVEN DESIGN. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Modeling Paradigms and Tool Support. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Letting the Bones Show: Why Models Matter to Users. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> HANDS-ON MODELERS. </div> <p></p> <p> II. THE BUILDING BLOCKS OF A MODEL-DRIVEN DESIGN. </p> <div style="margin-left: 0.2in;"> 4. Isolating the Domain. </div> <br> <p> </p> <div style="margin-left: 0.4in;"> LAYERED ARCHITECTURE. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Relating the Layers. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Architectural Frameworks. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> The Domain Layer Is Where the Model Lives. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> THE SMART UI “ANTI-PATTERN” </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Other Kinds of Isolation. </div> <p></p> <div style="margin-left: 0.2in;"> 5. A Model Expressed in Software. </div> <br> <p> </p> <div style="margin-left: 0.4in;"> Associations. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> ENTITIES (A.K.A. REFERENCE OBJECTS). </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Modeling ENTITIES. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Designing the Identity Operation. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> VALUE OBJECTS. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Designing VALUE OBJECTS. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Designing Associations That Involve VALUE OBJECTS. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> SERVICES. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> SERVICES and the Isolated Domain Layer. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Granularity. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Access to SERVICES. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> MODULES (A.K.A. PACKAGES). </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Agile MODULES. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> The Pitfalls of Infrastructure-Driven Packaging. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Modeling Paradigms. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Why the Object Paradigm Predominates. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Nonobjects in an Object World. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Sticking with MODEL-DRIVEN DESIGN When Mixing Paradigms. </div> <p></p> <div style="margin-left: 0.2in;"> 6. The Life Cycle of a Domain Object. </div> <br> <p> </p> <div style="margin-left: 0.4in;"> AGGREGATES. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> FACTORIES. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Choosing FACTORIES and Their Sites. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> When a Constructor Is All You Need. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Designing the Interface. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Where Does Invariant Logic Go? </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> ENTITY FACTORIES Versus VALUE OBJECT FACTORIES. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Reconstituting Stored Objects. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> REPOSITORIES. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Querying a REPOSITORY. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Client Code Ignores REPOSITORY Implementation; Developers Do Not. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Implementing a REPOSITORY. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Working Within Your Frameworks. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> The Relationship with FACTORIES. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Designing Objects for Relational Databases. </div> <p></p> <div style="margin-left: 0.2in;"> 7. Using the Language: An Extended Example. </div> <br> <p> </p> <div style="margin-left: 0.4in;"> Introducing the Cargo Shipping System. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Isolating the Domain: Introducing the Applications. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Distinguishing ENTITIES and VALUE OBJECTS. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Role and Other Attributes. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Designing Associations in the Shipping Domain. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> AGGREGATE Boundaries. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Selecting REPOSITORIES. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Walking Through Scenarios. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Sample Application Feature: Changing the Destination of a Cargo. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Sample Application Feature: Repeat Business. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Object Creation. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> FACTORIES and Constructors for Cargo. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Adding a Handling Event. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Pause for Refactoring: An Alternative Design of the Cargo AGGREGATE. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> MODULES in the Shipping Model. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Introducing a New Feature: Allocation Checking. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Connecting the Two Systems. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Enhancing the Model: Segmenting the Business. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Performance Tuning. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> A Final Look. </div> <p></p> <p> III. REFACTORING TOWARD DEEPER INSIGHT. </p> <div style="margin-left: 0.2in;"> 8. Breakthrough. </div> <br> <p> </p> <div style="margin-left: 0.4in;"> Story of a Breakthrough. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> A Decent Model, and Yet…. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> The Breakthrough. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> A Deeper Model. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> A Sobering Decision. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> The Payoff. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Opportunities. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Focus on Basics. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Epilogue: A Cascade of New Insights. </div> <p></p> <div style="margin-left: 0.2in;"> 9. Making Implicit Concepts Explicit. </div> <br> <p> </p> <div style="margin-left: 0.4in;"> Digging Out Concepts. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Listen to Language. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Scrutinize Awkwardness. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Contemplate Contradictions. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Read the Book. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Try, Try Again. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> How to Model Less Obvious Kinds of Concepts. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Explicit Constraints. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Processes as Domain Objects. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> SPECIFICATION </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Applying and Implementing SPECIFICATION. </div> <p></p> <div style="margin-left: 0.2in;"> 10. Supple Design. </div> <br> <p> </p> <div style="margin-left: 0.4in;"> INTENTION-REVEALING INTERFACES. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> SIDE-EFFECT-FREE FUNCTIONS. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> ASSERTIONS. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> CONCEPTUAL CONTOURS. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> STANDALONE CLASSES. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> CLOSURE OF OPERATIONS. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> DECLARATIVE DESIGN. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Domain-Specific Languages. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> A Declarative Style of Design. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Extending SPECIFICATIONS in a Declarative Style. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Angles of Attack. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Carve Off Subdomains. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Draw on Established Formalisms, When You Can. </div> <p></p> <div style="margin-left: 0.2in;"> 11. Applying Analysis Patterns. </div> <br> <div style="margin-left: 0.2in;"> 12. Relating Design Patterns to the Model. </div> <br> <p> </p> <div style="margin-left: 0.4in;"> STRATEGY (A.K.A. POLICY). </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> COMPOSITE. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Why Not FLYWEIGHT? </div> <p></p> <div style="margin-left: 0.2in;"> 13. Refactoring Toward Deeper Insight. </div> <br> <p> </p> <div style="margin-left: 0.4in;"> Initiation. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Exploration Teams. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Prior Art. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> A Design for Developers. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Timing. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Crisis as Opportunity. </div> <p></p> <p> IV. STRATEGIC DESIGN. </p> <div style="margin-left: 0.2in;"> 14. Maintaining Model Integrity. </div> <br> <p> </p> <div style="margin-left: 0.4in;"> BOUNDED CONTEXT. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Recognizing Splinters Within a BOUNDED CONTEXT </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> CONTINUOUS INTEGRATION. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> CONTEXT MAP. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Testing at the CONTEXT Boundaries. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Organizing and Documenting CONTEXT MAPS. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Relationships Between BOUNDED CONTEXTS. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> SHARED KERNEL. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> CUSTOMER/SUPPLIER DEVELOPMENT TEAMS. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> CONFORMIST. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> ANTICORRUPTION LAYER. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Designing the Interface of the ANTICORRUPTION LAYER. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Implementing the ANTICORRUPTION LAYER. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> A Cautionary Tale. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> SEPARATE WAYS. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> OPEN HOST SERVICE. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> PUBLISHED LANGUAGE. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Unifying an Elephant. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Choosing Your Model Context Strategy. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Team Decision or Higher. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Putting Ourselves in Context. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Transforming Boundaries. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Accepting That Which We Cannot Change: Delineating the External Systems. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Relationships with the External Systems. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> The System Under Design. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Catering to Special Needs with Distinct Models. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Deployment. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> The Trade-off. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> When Your Project Is Already Under Way. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Transformations. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Merging CONTEXTS: SEPARATE WAYS—SHARED KERNEL. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Merging CONTEXTS: SHARED KERNEL—CONTINUOUS INTEGRATION. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Phasing Out a Legacy System. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> OPEN HOST SERVICE—PUBLISHED LANGUAGE. </div> <p></p> <div style="margin-left: 0.2in;"> 15. Distillation. </div> <br> <p> </p> <div style="margin-left: 0.4in;"> CORE DOMAIN. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Choosing the CORE. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Who Does the Work? </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> An Escalation of Distillations. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> GENERIC SUBDOMAINS. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Generic Doesn't Mean Reusable. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Project Risk Management. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> DOMAIN VISION STATEMENT. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> HIGHLIGHTED CORE. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> The Distillation Document. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> The Flagged CORE. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> The Distillation Document as Process Tool. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> COHESIVE MECHANISMS. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> GENERIC SUBDOMAIN Versus COHESIVE MECHANISM. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> When a MECHANISM Is Part of the CORE DOMAIN. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Distilling to a Declarative Style. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> SEGREGATED CORE. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> The Costs of Creating a SEGREGATED CORE. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Evolving Team Decision. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> ABSTRACT CORE. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Deep Models Distill. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Choosing Refactoring Targets. </div> <p></p> <div style="margin-left: 0.2in;"> 16. Large-Scale Structure. </div> <br> <p> </p> <div style="margin-left: 0.4in;"> EVOLVING ORDER. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> SYSTEM METAPHOR. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> The “Naive Metaphor” and Why We Don't Need It. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> RESPONSIBILITY LAYERS. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Choosing Appropriate Layers. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> KNOWLEDGE LEVEL. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> PLUGGABLE COMPONENT FRAMEWORK. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> How Restrictive Should a Structure Be? </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Refactoring Toward a Fitting Structure. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Minimalism. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Communication and Self-Discipline. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Restructuring Yields Supple Design. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Distillation Lightens the Load. </div> <p></p> <div style="margin-left: 0.2in;"> 17. Bringing the Strategy Together. </div> <br> <p> </p> <div style="margin-left: 0.4in;"> Combining Large-Scale Structures and BOUNDED CONTEXTS. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Combining Large-Scale Structures and Distillation. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Assessment First. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Who Sets the Strategy? </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Emergent Structure from Application Development. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> A Customer-Focused Architecture Team. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Six Essentials for Strategic Design Decision Making. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> The Same Goes for the Technical Frameworks. </div> <p></p> <p> </p> <div style="margin-left: 0.4in;"> Beware the Master Plan. </div> <p></p> <div style="margin-left: 0.2in;"> Conclusion. </div> <br> <div style="margin-left: 0.2in;"> Appendix: The Use of Patterns in This Book. </div> <br> <div style="margin-left: 0.2in;"> Glossary. </div> <br> <div style="margin-left: 0.2in;"> References. </div> <br> <div style="margin-left: 0.2in;"> Photo Credits. </div> <br> <div style="margin-left: 0.2in;"> Index. 0321125215T08272003 </div> <br>

Net verschenen

Rubrieken

Populaire producten

    Personen

      Trefwoorden

        Domain-Driven Design