• Complain

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

Here you can read online Eric Evans - Domain-Driven Design: Tackling Complexity in the Heart of Software full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. year: 2003, publisher: Addison-Wesley Professional, genre: Computer. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:

Romance novel Science fiction Adventure Detective Science History Home and family Prose Art Politics Computer Non-fiction Religion Business Children Humor

Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.

Eric Evans Domain-Driven Design: Tackling Complexity in the Heart of Software
  • Book:
    Domain-Driven Design: Tackling Complexity in the Heart of Software
  • Author:
  • Publisher:
    Addison-Wesley Professional
  • Genre:
  • Year:
    2003
  • Rating:
    4 / 5
  • Favourites:
    Add to favourites
  • Your mark:
    • 80
    • 1
    • 2
    • 3
    • 4
    • 5

Domain-Driven Design: Tackling Complexity in the Heart of Software: summary, description and annotation

We offer to read an annotation, description, summary or preface (depends on what the author of the book "Domain-Driven Design: Tackling Complexity in the Heart of Software" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.

Describes ways to incorporate domain modeling into software development.
Title: Domain-Driven Design
Author: Evans, Eric/ Fowler, Martin (FRW)
Publisher: Prentice Hall
Publication Date: 2003/08/01
Number of Pages: 320
Binding Type: eBook
Library of Congress: 2003050331

Eric Evans: author's other books


Who wrote Domain-Driven Design: Tackling Complexity in the Heart of Software? Find out the surname, the name of the author of the book and a list of all author's works by series.

Domain-Driven Design: Tackling Complexity in the Heart of Software — read online for free the complete book (whole text) full work

Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Domain-Driven Design: Tackling Complexity in the Heart of Software" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.

Light

Font size:

Reset

Interval:

Bookmark:

Make
Copyright

Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and Addison-Wesley was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals.

The author and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein.

See page 517 for photo credits.

The publisher offers discounts on this book when ordered in quantity for bulk purchases and special sales. For more information, please contact:

U.S. Corporate and Government Sales
(800) 382-3419

For sales outside of the U.S., please contact:

International Sales
(317) 581-3793

Visit Addison-Wesley on the Web: www.awprofessional.com

Library of Congress Cataloging-in-Publication Data


Evans, Eric, 1962
Domain-driven design : tackling complexity in the heart of software / Eric
Evans.
p. cm.
Includes bibliographical references and index.
ISBN 0-321-12521-5
1. Computer softwareDevelopment. 2. Object-oriented programming
(Computer science) I. Title.
QA76.76.D47E82 2003 2003050331

Copyright 2004 by Eric Evans

All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior consent of the publisher. Printed in the United States of America. Published simultaneously in Canada.

For information on obtaining permission for use of material from this work, please submit a written request to:

Pearson Education, Inc.
Rights and Contracts Department
75 Arlington Street, Suite 300
Boston, MA 02116
Fax: (617) 8487047

Text printed on recycled paper

1 2 3 4 5 6 7 8 9 10CRW0706050403

First printing, August 2003

Dedication

To Mom and Dad

Praise for Domain-Driven Design

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

Kent Beck

"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 developersit 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."

Ward Cunningham

"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

"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 dujour have gone out of fashion."

Dave Collins, author of Designing Object-Oriented User Interfaces

"Eric weaves real-world experience modelingand buildingbusiness 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

Foreword

There are many things that make software development complex. But the heart of this complexity is the essential intricacy of the problem domain itself. If you're trying to add automation to complicated human enterprise, then your software cannot dodge this complexityall it can do is control it.

The key to controlling complexity is a good domain model, a model that goes beyond a surface vision of a domain by introducing an underlying structure, which gives the software developers the leverage they need. A good domain model can be incredibly valuable, but it's not something that's easy to make. Few people can do it well, and it's very hard to teach.

Eric Evans is one of those few who can create domain models well. I discovered this by working with himone of those wonderful times when you find a client who's more skilled than you are. Our collaboration was short but enormous fun. Since then we've stayed in touch, and I've watched this book gestate slowly.

It's been well worth the wait.

This book has evolved into one that satisfies a huge ambition: To describe and build a vocabulary about the very art of domain modeling. To provide a frame of reference through which we can explain this activity as well as teach this hard-to-learn skill. It's a book that's given me many new ideas as it has taken shape, and I'd be astonished if even old hands at conceptual modeling don't get a raft of new ideas from reading this book.

Eric also cements many of the things that we've learned over the years. First, in domain modeling, you shouldn't separate the concepts from the implementation. An effective domain modeler can not only use a whiteboard with an accountant, but also write Java with a programmer. Partly this is true because you cannot build a useful conceptual model without considering implementation issues. But the primary reason why concepts and implementation belong together is this: The greatest value of a domain model is that it provides a that ties domain experts and technologists together.

Another lesson you'll learn from this book is that domain models aren't first modeled and then implemented. Like many people, I've come to reject the phased thinking of "design, then build." But the lesson of Eric's experience is that the really powerful domain models evolve over time, and even the most experienced modelers find that they gain their best ideas after the initial releases of a system.

I think, and hope, that this will be an enormously influential book. One that will add structure and cohesion to a very slippery field while it teaches a lot of people how to use a valuable tool. Domain models can have big consequences in controlling software developmentin whatever language or environment they are implemented.

One final yet important thought. One of things I most respect about this book is that Eric is not afraid to talk about the times when he hasn't been successful. Most authors like to maintain an air of disinterested omnipotence. Eric makes it clear that like most of us, he's tasted both success and disappointment. The important thing is that he can learn from bothand more important for us is that he can pass on his lessons.

Martin Fowler
April 2003

Next page
Light

Font size:

Reset

Interval:

Bookmark:

Make

Similar books «Domain-Driven Design: Tackling Complexity in the Heart of Software»

Look at similar books to Domain-Driven Design: Tackling Complexity in the Heart of Software. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.


Reviews about «Domain-Driven Design: Tackling Complexity in the Heart of Software»

Discussion, reviews of the book Domain-Driven Design: Tackling Complexity in the Heart of Software and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.