EUR 69,57
  • Tutti i prezzi includono l'IVA.
Disponibilità immediata.
Venduto e spedito da Amazon. Confezione regalo disponibile.
Domain-Driven Design: Tac... è stato aggiunto al tuo carrello

Spedire a:
Per vedere gli indirizzi, per favore
Inserisci un codice postale corretto.
Ne hai uno da vendere?
Passa al retro Passa al fronte
Ascolta Riproduzione in corso... In pausa   Stai ascoltando un campione dell'edizione audio udibile.
Maggiori informazioni
Visualizza tutte le 3 immagini

Domain-Driven Design: Tackling Complexity in the Heart of Software (Inglese) Copertina rigida – 20 ago 2003

4,3 su 5 stelle
5 stelle
4 stelle
3 stelle
2 stelle
1 stella
4,3 su 5 stelle 103 recensioni clienti su

Visualizza tutti i 3 formati e le edizioni Nascondi altri formati ed edizioni
Prezzo Amazon
Nuovo a partire da Usato da
Formato Kindle
"Ti preghiamo di riprovare"
Copertina rigida
"Ti preghiamo di riprovare"
EUR 69,57
EUR 42,71 EUR 50,57
Nota: Questo articolo può essere consegnato in un punto di ritiro. Dettagli
Ritira il tuo ordine dove e quando preferisci.
  • Scegli tra gli oltre 8.500 punti di ritiro in Italia
  • I clienti Prime beneficiano di consegne illimitate presso i punti di ritiro senza costi aggiuntivi
Come inviare un ordine presso un punto di ritiro Amazon.
  1. Trova il tuo punto di ritiro preferito ed aggiungilo alla tua rubrica degli indirizzi
  2. Indica il punto di ritiro in cui vuoi ricevere il tuo ordine nella pagina di conferma d’ordine
Maggiori informazioni
click to open popover

Spesso comprati insieme

  • Domain-Driven Design: Tackling Complexity in the Heart of Software
  • +
  • Implementing Domain-Driven Design
  • +
  • Clean Code: A Handbook of Agile Software Craftsmanship
Prezzo totale: EUR 121,71
Acquista tutti gli articoli selezionati

Descrizione prodotto

Dalla quarta di copertina

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


Eric Evans is the founder of Domain Language, a consulting group dedicated to helping companies build evolving software deeply connected to their businesses. Since the 1980s, Eric has worked as a designer and programmer on large object-oriented systems in several complex business and technical domains. He has also trained and coached development teams in Extreme Programming.

Non è necessario possedere un dispositivo Kindle. Scarica una delle app Kindle gratuite per iniziare a leggere i libri Kindle sul tuo smartphone, tablet e computer.

  • Apple
  • Android
  • Windows Phone

Per scaricare una app gratuita, inserisci il numero di cellulare.

Dettagli prodotto

Quali altri articoli acquistano i clienti, dopo aver visualizzato questo articolo?

Recensioni clienti

Non ci sono ancora recensioni di clienti su
5 stelle
4 stelle
3 stelle
2 stelle
1 stella

Le recensioni clienti più utili su (beta) (Potrebbero essere presenti recensioni del programma "Early Reviewer Rewards") 4.3 su 5 stelle 103 recensioni
15 di 16 persone hanno trovato utile la seguente recensione
5.0 su 5 stelle Essential software modelling 19 giugno 2016
Di Alexey Tkachenko - Pubblicato su
Formato: Copertina rigida Acquisto verificato
This is serious book about domain modeling in software design. Software development society lives from one hype wave to another. OOP, patterns, XP, TDD, CI/CD, BigData, DevOps - this is just to name few. This book is originated from golden age of OOP. The author admits that object oriented paradigm is not the only one available but the bias toward OOP/OOD is obvious (and justifiable). This book tells about how to do the modeling of core software components “the right way”.
With fast pace of modern software development, it’s easy to forget that the main part of software value is in its “brains”. You can change GUI technology or infrastructure layer. You even can totally rewrite your application but the application domain stays more or less the same and at the end of the day the model defines whether this software is useful or not.
I can say that this book is targeting architects, domain experts, business analysts (and I believe these professionals are the main audience) but this would be the usual fallacy of separating software developers into first and second class. So I say the opposite – if you want to transcend from craft of software development to its art you should read this book.
2 di 2 persone hanno trovato utile la seguente recensione
5.0 su 5 stelle Required Reading 10 febbraio 2017
Di Matthew Armstrong - Pubblicato su
Formato: Formato Kindle Acquisto verificato
IMHO required reading for enterprise level developers, architects and IT Project Managers. The principles are sound and the writing style actually makes what would otherwise be a dry read quite enjoyable.
15 di 17 persone hanno trovato utile la seguente recensione
2.0 su 5 stelle Do not purchase Kindle version - Code/graphs are impossible to read 8 marzo 2016
Di Charles - Pubblicato su
Formato: Formato Kindle Acquisto verificato
The book it's self is great the Kindle version is horrible however. Code examples are hard to read with breaks in the worst places. Charts and graphs are also impossible to read.
6 di 7 persone hanno trovato utile la seguente recensione
5.0 su 5 stelle A must have for software developers 16 agosto 2013
Di Andrei Fangli - Pubblicato su
Formato: Copertina rigida Acquisto verificato
The book explains concepts and patterns very well. Each definition comes along with a good example to make the whole idea clearer. Each pattern can solve only a class of problems and Eric Evans highlights when and why to apply a specific pattern, also provides scenarios to combing patterns for a more expressive system.

Principles that must be present in a software project are highlighted (such as communication through a language used by all team members, a language that is built from discussions with domain experts). Importance of software design and how it favors problem solving and clear communication between team members and teams.

For a while I was looking at refactoring as a "thing to do when the software is done if time allows it", Eric Evans highlights refactoring as a necessity and must not be neglected because continuous refactoring leads to deeper knowledge and understanding of what the Software needs to do and how it actually does it.

Practical problems such as the possibility of multiple models to exist within the same system have been addressed and given solutions from using one common (unified) model in the whole system (also the costs of such a choice are presented) to totally independent models. An algorithm described in steps is presented for getting two totally independent models to be completely unified allows designers and developers to combine any part of their software towards new features required by the business.

Also a common problem at this time is integration with legacy systems (there are lots of systems that were written using old, now unreliable, components that need migration towards newer, safer, faster components), this problem is approached and it's solution is detailed from beginning to end where the system is completely migrated.

Last but not least, a small oriented graph is given to visualize how concepts in the book are connected and how all pieces fall into the puzzle. Any software developer should read this book at least one time.
5.0 su 5 stelle great book 1 giugno 2017
Di Amazon Customer - Pubblicato su
Formato: Copertina rigida Acquisto verificato
Well, I'm still reading it, but it's a mandatory reading for those who want to deliver great software