More Related Content
Similar to SOAT Agile Day 2017 DDD
SOAT Agile Day 2017 DDD
- 1. Thinking in DDD GrégoryBOISSINOT 2017 April 25
- 2. DDD IS AN APPROACH TOSOFTWARE DESIGN FOR COMPLEX NEEDS
- 3. Outline • Software Designactivity • Software Projects issues • DDD approach • Explore the problem space with Collaborative Design • Implement the solution space with Strategic Design & Tactical Design
- 4.
- 5. DESIGN IS MAKINGDECISIONS
- 6.
- 7. MAKING DECISIONS TO BUILDUSEFUL PRODUCTS
- 8. AGILE IS HOWYOU ORGANIZE TO GET THE WORK DONE
- 9. AGILE IS HOWYOU ORGANIZE TO GET THE WORK DONE GETTING WORK DONE IS TO DESIGN
- 10. LOTS OF FAILURESHAPPENING ON SOFTWARE PROJECTS
- 11. SCRUM PRODUCT BACKLOGAS PROCESS EXCELLENCE
- 12. PRESSURE TO DELIVER SOFTWARERELEASES ON A RELENTLESS SCHEDULE
- 13. A LACK OFDESIGN
- 14. Language Framework Library Infra JUMP INTO SPACESOLUTION TOO QUICKLY
- 15.
- 16.
- 17. ANALYSIS MODEL CODE MODEL POORSYNCHRONIZATION BETWEEN MODELS
- 18. Initial product incarnation fastto produce without care and consideration It works but no one knows how A lack of organization
- 19.
- 20.
- 21. CLIENT CONTACT Code createdwithout a common language Different terms VS
- 22. ROOM - name ROOM - building -floor - capacity - lighting - air conditioner Code created without a common language The same term but with different meaning VS
- 23. OUR ORGANISATIONAL AND TECHNICALDESIGNS DO NOT ALIGN WITH THE PROBLEM DOMAIN
- 24.
- 25. BIG BALL OFMUD
- 28.
- 30. THE MOST SIGNIFICANTCOMPLEXITY IN SOFTWARE DESIGN IS NOT TECHNICAL
- 31. “Critical Complexity ofmost software projects is in understanding the domain itself “ Eric Evans
- 32. THE DOMAIN THE PROBLEMAREA The reality PROBLEM SPACE
- 33. THE DOMAIN IS A SPHEREOF KNOWLEDGE
- 34.
- 35. DOMAINS ARE BASEDON A MODEL
- 36. THE DOMAIN MODEL Domain Knowledge Richin Domain Model SOLUTION SPACE
- 37. Domain Domain Model The reality Anabstraction of reality designed to manage complexity for specific business cases A projection of the Real Domain THE PROBLEM SPACE THE SOLUTION SPACE
- 38.
- 39. DDD IS ABOUTCREATING SHARED UNDERSTANDING OF THE PROBLEM SPACE
- 40. MAKE THE IMPLICITEXPLICIT
- 41. BOUND BY LANGUAGE EXPRESSED AS DIAGRAMS EXPRESSEDIN CONVERSATION EXPRESSED AS DOCUMENTATION EXPRESSED AS CODE A UBIQUITOUS LANGUAGE IS AT THE HEART OF GOOD DESIGN
- 42.
- 43. BUSINESS GLOSSARY OF THEUBIQUITOUS TERMS
- 44. BUSINESS GLOSSARY AS ASHARED DOCUMENT USED AND MAINTAINED BY THE WHOLE PRODUCT TEAM
- 45. ANALYSIS MODEL CODE MODEL GOODSYNCHRONIZATION BETWEEN MODELS Ubiquitous Language
- 46.
- 47.
- 48. THE PROBLEM SPACE EXPLORETHE PROBLEM SPACE
- 49.
- 51. STAY IN SYNERGY WITHTHE VALUES OF THE SOFTWARE AND THE BUSINESS
- 52.
- 53. TAKE ALL TEAMSON BOARD
- 54.
- 55. BUSINESS USERS AREBUSY PEOPLE
- 56.
- 57. COLLABORATION AND CONSTRUCTION OF UBIQUITOUSLANGUAGE THAT MAKES DDD SO POWERFUL
- 58.
- 59. Domain Event Command Actor Question ? EventStorming Mechanisms
- 60. CLARIFYING QUESTIONS ‣ Whatdo you mean by … ? ‣ What might lead someone to do / need .. ? ‣ What else might happen ...?
- 61. BREAK THE PROBLEM &THE COMPLEXITY DOWN
- 62. NOT ALL THEPARTS OF THE PROBLEM ARE EQUAL
- 63.
- 64. “There are norules for determining service boundaries“ Udi Dahan
- 65.
- 66.
- 67.
- 68.
- 69.
- 70.
- 71. BREAK DOWN INTO SMALLERDDD SUBDOMAINS
- 72. A car systemsubdomains
- 73. Subdomains of abook e-commerce platform LibraryMembership Payments Customer Support Shipping Marketing
- 74. YOU CAN'T EQUALLYSPREAD EFFORT AND QUALITY THROUGHOUT THE ENTIRE SYSTEM
- 75. ‣ WHAT ARETHE PARTS OF THE PRODUCT THAT WILL MAKE IT A SUCCESS ? ‣ WHY ARE THESE PARTS OF THE SYSTEM IMPORTANT ? ‣ WHY CAN’T THEY BE BOUGHT OFF THE SHELF ?
- 76. YOU NEED TOUNDERSTAND THE BUSINESS STRATEGY
- 78.
- 79.
- 80. Paper justifying whythe product is a good idea Whiteboard with salient points Shared understanding of what is core CAPTURE THE CORE DOMAINS VISION
- 81. A car systemsubdomains
- 82. Partitioned subdomains of abook e-commerce platform BookMembership Payments Customer Support Shipping Marketing (Core Domain) (Generic Domain) (Supporting Domain) (Generic Domain) (Supporting Domain) (Core Domain)
- 83. TREAT YOUR COREDOMAIN AS A PRODUCT
- 84. THE CORE DOMAIN REQUIRESYOUR BEST DEVELOPERS
- 85. DESGIN THE PRODUCT INTHE SOLUTION SPACE
- 86. Ideally, one-to-one mapping betweendomain models and subdomains BookMembership Payments Customer Support Shipping Marketing (Core Domain) (Generic Domain) (Supporting Domain) (Generic Domain) (Supporting Domain) (Core Domain) Regular shipping Priority shipping
- 87.
- 88. MULTIPLE MODELS CRUD Domain Model Transaction script Anemic CQRS Richobject-oriented model
- 89.
- 90. KEEP THE CODEMODEL CLEAN OF TECHNICAL CONCERNS AND FOCUS ON THE DOMAIN
- 91. THE PRODUCT VIEWWITH DDD The Domain Model The application layer is the client of the domain layer and represent the use case of the product The logic layer (application Service) represents the logic processes and concepts of the domain infrastructure UI
- 92. CUSTOMER << Authentication Context >> User/Mdp <<Orders Context >> Method of payment << Reviewer Context>> Nb of stars BUSINESS USE CASE BUSINESS USE CASE BUSINESS USE CASE LARGE AMBIGIOUS MODEL
- 93.
- 94. USER AUTHENTICATION BOUNDED CONTEXT CUSTOMER ORDERS BOUNDED CONTEXT REVIEWER EVALUATION BOUNDEDCONTEXT DIVIDE LARGE AND COMPLEX MODEL INTO BOUNDED CONTEXTS
- 95. SERVICE PRIORITY BOUNDED CONTEXT SERVICE PAYMENT BOUNDED CONTEXT SERVICE REGULAR BOUNDEDCONTEXT SERVICE PROMOTION BOUNDED CONTEXT ALIGNMENT WITH THE BUSINESS VISION FOR THE E-BOOK PLATFORM
- 96.
- 98. USER INTERFACE BOUNDED CONTEXTA BOUNDED CONTEXT B BOUNDED CONTEXT USERINTERFACE OUR SYSTEM AS A COLLECTION OF BOUNDED CONTEXTS
- 99. A TEAM OFPROFESSIONALS WHICH OWNS THE CONTEXT WILL MAKE GOOD CHOICES
- 100. BOUNDED CONTEXT IS OWNEDENTIRELY BY ONE PRODUCT TEAM
- 101. UI + SERVICE DB PRIORITY BOUNDED CONTEXT UI + SERVICE DB PAYMENT BOUNDED CONTEXT UI + SERVICE DB REGULAR BOUNDEDCONTEXT UI + SERVICE DB PROMOTION BOUNDED CONTEXT Aligning with the business vision & BC segregation
- 102.
- 103.
- 104. SIMPLE RULES FORCOMMUNICATION BETWEEN BOUNDED CONTEXTS
- 105. DDD MAXIMISES OUR ABILITYTO DELIVERY VALUE TO COSTUMERS
- 106. DDD MAXIMISES OUR ABILITYTO DELIVERY VALUE TO CUSTOMERS AND REDUCES COST
- 107.
- 108. Cusomer Support Shipment Payment Marketing Book Membership Marketing Book Payment Shipping Membership Customer Support Reporting Custom functional deliveryteam Flow of information Cross cutting Context Map
- 109. Third Party Context Shipping Context Pricing Context Legacy Context Listing Book Context Loyalty Subdomain Open Host Service Downstream Partenership Upstream Upstream DownstreamUpstream AntiCorruption Layer Context Map with integration strategies
- 110.
- 111.
- 112.
- 113. ‣ Design isthe art of trade-off ‣ DDD enhances synergy and alignment between teams ‣ DDD focus on main concepts : ‣ Ubiquitous Language, ‣ Bounded Context, ‣ Core Domains CONCLUSION
- 114.