Eric Evans, DomainLanguages, USA
Eric Evans is a specialist in domain modeling and design. He has worked on many projects developing large business systems and has been deeply involved in applying modeling and Agile processes on real projects. Out of this range of experiences emerged the synthesis of principles and techniques shared in the book "Domain-Driven Design" Addison-Wesley 2004. Eric now leads "Domain Language", a consulting group that trains teams to make their development more productive through effective application of domain modeling and design. Patrik Fredriksson, Citerus, Sweden As a co-founder and consultant with Citerus Patrik has been doing professional software development and mentoring for the last ten years. He has a particular passion for agile software design and architecture, software development project efficiency and developer craftsmanship. He is highly motivated to improve the way software is created and maintained; good software is fun to use and fun to create, bad software and lost projects make him sad. Patrik sees bridging the gap between business people and developers as absolutely crucial for making software development projects successful. Getting to know the business domain has always been a top priority for him when working on projects. As Domain-Driven Design addresses many of the issues that arise when working with complex domains, his interest for DDD comes as no surprise. Patrik has been an active member of the Swedish DDD community for several years and is one of the co-founders of DDD Sverige, the Swedish DDD Interest Group. http://groups.google.com/group/dddsverige Patrik Fredriksson is a certified instructor by Eric Evans and Domain Language, Inc.
Domain-Driven Design: Putting the Model to Work
Large information systems need a domain model. Development teams know this, yet they often end up with little more than data schemas which do not deliver on the productivity promises for object design. This tutorial delves into how a team, developers and domain experts together, can engage in progressively deeper exploration of their problem domain while making that understanding tangible as a practical software design. This model is not just a diagram or an analysis artifact. It provides the very foundation of the design, the driving force of analysis, even the basis of the language spoken on the project. The tutorial will focus on three topics: The conscious use of language on the project to refine and communicate models and strengthen the connection with the implementation. A subtly different style of refactoring aimed at deepening model insight, in addition to making technical improvements to the code. A brief look at strategic design, which is crucial to larger projects. These are the decisions where design and politics often intersect. The tutorial will include group reading and discussion of selected patterns from the book "Domain-Driven Design," Addison-Wesley 2003, and reenactments of domain modeling scenarios. *Intermediate*: Basic object-oriented modeling. Complex software experience helpful. Familiarity with Agile development or Extreme Programming helpful. *Goals*: To communicate the basic principles of domain-driven design and outline the key factors in making a domain model an effective tool for a software project. *Format*: Mixture of lecture, reinactments, group reading and discussion. |
