Domain-Driven Design
- Tackling complexity in software development
Available as in-house training
Date and location of the in-house training to be agreed
Price: 690 EUR + VAT / person
Duration and language:
Onsite training - 14h - 2 days each 7 hours (including breaks).
Online training - 15h - 3 days each 5 hours (including breaks).
Online training schedule:
- 09:00 - 11:00 CET online session,
- 11:00 - 12:00 CET break,
- 12:00 - 14:00 CET online session.
Training is provided in English. A Polish version is also available.
Target group:
The training is intended for:
- project and development teams,
- programmers,
- IT system architects,
- business analysts and Product Owners,
- board members,
- stakeholders and domain experts.
Training preconditions:
Knowledge of basic concepts in the design and implementation of information systems. Experience in working on complex IT solutions covering a number of business domains and requiring the cooperation of a large group of specialists divided into one or more teams is recommended.
For online training, it is required to meet technical requirements: https://valkir.pl/en/online-training/.
Price includes:
- Preparation and training performed by software development processes expert.
- Effective training in a small group - on average 6-12 people.
- Training materials, requisites and a certificate of training completion issued by Valkir Academy.
- Lunch and catering (drinks and snacks). Not applicable to online training.
- Trainer’s travel and expenses (T&E). Not applicable to online training.
Certification:
The price of the authorial training includes certificates of training completion issued by Valkir Academy (in English). There is no market-recognized accredited certification path.
Available dates:
| Date | Location | Price per person | |
|---|---|---|---|
| To be agreed | To be agreed | 690 EUR | Request quote |
Training description:
What is the Domain-Driven Design training?
The Domain-Driven Design training is intended for teams that work on complex projects and create products/services in the IT industry. Based on a detailed analysis of available sources and their own experience in running commercial projects, trainers dispel doubts about DDD and teach the correct use of techniques to tackle a complex IT system.
Domain-Driven Design covers topics from the full spectrum of stages of the software development process. Therefore, the program is recommended for people performing various roles - architects, programmers, business analysts, Product Owners. The greatest benefits will be gained by companies in which the method will be understood and applied holistically throughout the organization due to the interdependencies that exist between the issues addressed to each of the above-mentioned groups.
DDD teaches how to divide and effectively model a complex business problem, reducing the distance between stakeholder requirements and technical implementation. The use of the presented techniques allows you to shorten the time of business analysis, modeling and implementation, set priorities correctly, reduce the risk of misunderstandings and build an easily adaptable system
to the changing needs of customers.
Who’s behind this?
The history of Domain-Driven Design began in 2003 when Eric Evans published his famous blue book “Domain-Driven Design: Tackling Complexity in the Heart of Software”. The author himself admits, however, that the techniques he collected, named and grouped, had already been widely used by professional business analysts and architects of information systems operating in methodologies from the Agile family.
In the following years, DDD became popular, developed and adapted to the constantly changing landscape of the IT world. Authors such as Vernon Vaughn, Martin Fowler and Jimmy Bogard are responsible for the evolution of the methodology.
Training agenda:
- Definition of Domain-Driven Design
- Presentation of Domain-Driven Design definition and premises.
- Domain-Driven Design advantages and areas of application.
- Division of DDD patterns into strategic and tactical.
- Discussion of common misconceptions about DDD.
- Communication
- The role of communication in the software development process.
- Technical and business language and common mistakes in communication.
- Presentation of the advantages of using a domain language.
- Methods of acquiring knowledge from domain experts.
- Discovering and using the ubiquitous language.
- Strategic patterns
- Introduction to the definition of a subdomain and bounded context.
- Overview of subdomain types.
- Introduction to the context map technique and presentation of the dependencies types between bounded contexts.
- Delineation of context boundaries and context size rules.
- Rules for assigning teams to bounded contexts.
- Discussion: The problem of model and code sharing between bounded contexts.
- An exercise in the application of strategic patterns in practice.
- Domain-Driven Design in the context of Agile
- How does DDD fit into the Agile approach?
- The role of independent development teams.
- KISS and YAGNI as elements of the DDD approach.
- The role of continuous learning, experiments and refactoring in the software development process.
- Tactical patterns
- A concise overview of the key characteristics of a good software architecture.
- Division into model and infrastructure in the implementation of a bounded context.
- The antipattern of the anemic domain model.
- The use of TDD in the process of modeling and implementing a bounded context.
- An exercise in code analysis based on technical patterns.
- DDD reference architecture
- Indication of application areas of the DDD reference architecture.
- Detailed description of building blocks.
- ID assignment techniques, use of ORM and other technical nuances.
- Implementation examples based on reference architecture.
- Discussion of common errors, pitfalls and anti-patterns.
- An exercise in using the reference architecture.
- Types of physical separation of bounded contexts
- Logical and physical separation between bounded contexts and between bounded context layers in a monolithic architecture.
- DDD implementation based on CQRS architecture.
- DDD implementation based on microservice architecture.
- An exercise in designing the system infrastructure based on the known patterns.
- Tools to facilitate process management
- Iterative domain model discovery using the Modeling Whirlpool technique.
- Domain modeling using the Event Storming technique.
- Communication with domain experts during Three Amigos sessions.
- Specification based on examples, i.e. Behavior-Driven Development.
- An example of a complete work schedule for enriching the system with new functionality.
- Workshops on the use of learned tools.
- Training summary
How our training look like?
Training goals:
What are the challenges we address?- How can I explain to others what exactly Domain-Driven Design is and is not?
- How can I tackle a complex IT system?
- How can I be sure that I spend time and resources on the actual clients’ needs?
- How can I speed up the implementation of IT solutions while increasing their reliability?
- How can I design a system that is easily adaptable to changing customer needs?
What benefits do you get?
The training allows participants to better understand how to effectively and efficiently respond to imprecise customer requirements by transforming them into tangible IT solutions. The methodology facilitates the launch of new initiatives, the maintenance of mature products and the improvement of the situation in legacy systems. It covers issues in the field of communication, business analysis, IT systems architecture and code quality.
As a result of this training, participants from different areas of the organization will:
- know and understood the aspects necessary for effective modeling of IT systems functionalities,
- acquire skills necessary to apply mentioned methods in practice,
- understand how and why new methods can positively affect their work.
