Eric Evans, TweetAuthor of Domain Driven Design
Biography: Eric Evans
Eric Evans is a specialist in domain modeling and design in large business systems. Since the early 1990s, he has worked on many projects developing large business systems with objects and has been deeply involved in applying 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 2003.
Eric now leads Domain Language, Inc., a consulting group which coaches and trains teams to make their development more productive and relevant through effective application of domain modeling and design.
Software Passion: Breaking My Own Domain Models
Books: Domain-Driven Design: Tackling Complexity in the Heart of Software
-Then he will talk about how the current explosion of new software approaches is forcing a rethinking of some of the DDD patterns and making some of them more relevant than ever.
Training: Domain Driven Overview Tweet
- Build your awareness of the basic concepts and value of Domain-Driven Design (DDD) in one day.
- Understand what DDD is and when and why it is valuable to software intensive organizations.
- Overview the basic principles and processes needed develop the useful sort of models, tie them into implementation and business analysis,
and place them within a viable, realistic strategy.
Any person seriously involved in software development, including developers, technical leaders, analysts, development managers and non-technical business experts.
Recommend some experience with projects developing complex software systems. Familiarity with iterative development processes.
Morning: Ubiquitous Language & Model Discovery
• What is DDD?
• What makes a model useful to a software project?
• Cultivation of a model-based language to connect domain experts, developers, and the code itself
• Exploratory interaction of technical and business people in the modeling process
• Aggregates: A taste of rigor. This pattern addresses, at the model level, the scaling of systems in complexity, performance, and distribution.
Afternoon: Strategic Design
• Distilling the Core Domain: Focusing fine modeling and design into those subdomains where the organization distinguishes itself
• Clarifying a shared vision
• Context Mapping: A pragmatic approach to dealing with the diversity models and processes on real large projects with multi-team/multi-subsystem development.
• Combining the Core Domain and Context Map to illuminate Strategic Design options for a project