|
|
|
<<< Previous speaker
|
next speaker >>>
|
Eric Evans, Author of Domain Driven Design
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
Website: http://www.domainlanguage.com/
Books: Domain-Driven Design: Tackling Complexity in the
Heart of Software
|
Presentation: "Four Strategies for Recovering the Ability to Design When Surrounded by Messy Legacy"
Time:
Tuesday 15:30 - 16:30
Location:
Salon D
Abstract:
Once a large software legacy is built up, accumulated design problems and the intrinsic complexity of integration combine to make it more and more difficult to execute clean design. A team may set out to design a new piece of software using a domain model, and at first they are focused on strategically valuable new features. In collaboration with business innovators, they outline a new vision of some part of the domain. They distill a model and design the new functionality.
Of course, the new functionality calls for integration with existing functionality. As the new vision is stuck together with a messy legacy system, lots of expedient compromises are made. Perhaps the new work must also be integrated with an external system and the introduction of these external elements leads to loss of clarity in the model. In response, the team may try to redesign or replace more of the legacy system, and the scope expands, and the work bogs down. There are various ways this may happen, but they lead to the same place. The focus on strategic value is lost, and a fresh and clear approach to the problem is muddied to the point that it has no impact.
Training: "Domain Driven Overview"
Time:
Thursday 09:00 - 16:00
Location:
Robinson/Whitman
Abstract:
DDD OVERVIEW:
- 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.
TARGET AUDIENCE
Any person seriously involved in software development, including developers, technical leaders, analysts, development managers and non-technical business experts.
PREREQUISITES
Recommend some experience with projects developing complex software systems. Familiarity with iterative development processes.
TOPICS INTRODUCED
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
|
 |
| |
