Download as PDF, PPTX
![Checking a Domain Event
Then(/^project account should be opened for (.*)$/) do |expected_headline|
eventually(timeout: 0.8) {
last_project_opened_event = @event_logger.received['ProjectOpened'].last
expect(last_project_opened_event).to_not be_nil
expect(last_project_opened_event).to be_a ProjectOpened
expect(last_project_opened_event.headline).to eq expected_headline
}
end](https://image.slidesharecdn.com/ideastickiesgreenbar-wroclawedition-150328164648-conversion-gate01/85/Idea-stickies-green-bar-Wroclaw-edition-157-320.jpg)
![Checking a Read Model
And(/^project (.*) should be visible in the projects list$/) do |project_name|
fail 'Please set @project_account_id ' unless @project_account_id
eventually(timeout: 0.5) {
visible_project =
Quindi::Application::ProjectList.find_by_id(@project_account_id)
expect(visible_project).not_to be_nil
expect(visible_project['headline']).to eq project_name
}
end](https://image.slidesharecdn.com/ideastickiesgreenbar-wroclawedition-150328164648-conversion-gate01/85/Idea-stickies-green-bar-Wroclaw-edition-158-320.jpg)
Uploaded byAlberto Brandolini
Idea stickies green bar - Wroclaw edition
The document discusses methodologies and practices for improving software development processes, particularly focusing on identifying bottlenecks using approaches like event storming and domain-driven design (DDD). It emphasizes the importance of collaboration among key stakeholders to enhance understanding and address complexities in business processes. The content critiques traditional methods and promotes continuous evolution and experimentation as essential elements in software architecture and development.
More Related Content
Similar to Idea stickies green bar - Wroclaw edition
Idea stickies green bar - Wroclaw edition
- 1. #CDays14 – Milano25, 26 e 27 Febbraio 2014 Idea —> Post-It —> Test Verdi Idea Stickies Green Bar avanscoperta @ziobrando (original concept with @andreabalducci)
- 2. About me @ziobrando I dosomething else instead @ziobrandoAbout me avanscoperta #DDD #Agile #Lean #Entrepreneur #Developer #EventStorming #Coach #Facilitator #Consultant
- 3.
- 4.
- 8. Look for thebottleneck!
- 10. Improving the bottleneck, improves thewhole system
- 11. Other improvements have littleor negligible impact
- 12. I want tofind my bottleneck #Entrepreneur
- 13. I help mycustomers to find their bottleneck #Lean #Consultant
- 14. Should I careabout it? #Developer
- 15.
- 16. Customers will need toreduce costs in non bottleneck areas
- 17. Customers will need toimprove performances in bottleneck areas
- 19.
- 20. Customers might not knowabout their bottleneck
- 21. Customers might not wantto talk about their bottleneck #Developer
- 22. How can wedo the right thing?
- 23. Domain-Driven Design Not what you’llexpect #Developer #DDD
- 24.
- 25. Yes, this is stillwhat it looks like…
- 26. It’s actually worse thanthis #DDD
- 27.
- 28. “DDD is an architectural approachto over- engineered solutions”
- 29. This is whatwe see at the end
- 30.
- 32. “Why did ittake you so much to get there?”
- 33. “It’s the journeynot the destination”
- 34.
- 35.
- 36. Yep, not alljourneys are equal
- 37. Only some journeys areworth taking
- 38. That’s what wecall “Core Domain” #DDD
- 39. DDD supports a processof continuous evolution
- 40. It’s not forwriting software faster
- 41. It’s for rewriting softwarefrequently
- 42. Hypothesis: “DDD isan approach to software development for guys that can’t get it right the first time”
- 43.
- 44. You need arobust architecture for doing this
- 45. And in 2004, Entities,Value Objects and so on was the only viable option
- 46. DDD is notan architecture, but it needs a good one badly #DDD
- 47. Requirements Gathering Yep, that’s acommon name for our problem #Developer #DDD #Agile
- 48. How do wecollect requirements?
- 50.
- 53.
- 54. A simple solution Putall the key stakeholders in the same room and sketch a model together
- 55.
- 56.
- 59. This is waybetterEventstorming Short
- 60.
- 61.
- 62. Active Collaboration All participantshould actively contribute
- 63.
- 64.
- 65. and with afew tricks… #Agile #Coach#Facilitator
- 66.
- 67. Leveraging developer’s brain (something youwon’t admit
- 68. We basically made thebusiness problem less boring
- 70. It’s not aboutbeing faster That’s still thinking linearly
- 71. What’s Eventstorming It’s anact of deliberate collective learning
- 72.
- 73. Things we sweptunder the carpet
- 74. The Big Picture Allthe business process(es) end-to-end and beyond!
- 75. Unlimited Modelling Space Myproblem is... BIGGER
- 76.
- 77. Once you seeit…
- 78.
- 80. Unlimited surface You don’tknow the size of the problem before exploring it
- 81. Big Picture approaches -ImpactMapping -> Gojko Adzic -Specification Workshop -> Gojko Adzic -User Story Mapping -> Jeff Patton -Value Stream Mapping -> Stephen Parry (and others, of course) -...
- 82. In EventStorming -All keystakeholders in the same room -With an unlimited modelling surface -Modelling key processes starting from Domain Events
- 83. Domain Events Sometimes Ido things for a reason #DDD #Developer #EventStorming
- 85.
- 87.
- 90. Can’t you dothe same with an activity diagram?
- 91.
- 92. too afraid ofthe conference code of conduct to tell the joke Could you please laugh anyway?
- 94.
- 95. Humans evolved as the most efficient creaturesto spot someone else’s mistakes
- 96.
- 97.
- 98.
- 103. We have abig a behavioural model of the whole thing, now what?
- 104. We can havethe bottleneck emerge BIG problem here!!!
- 106. We can finally dothe right thing #DDD #Lean #Entrepreneur #Developer Please ignore what your brain is suggesting right now
- 107. Can we also doit right? #DDD #Developer
- 108. Business conversation Domain-‐Driven Design Event Sourcing CQRS Event Driven Architecture a business-‐driven model evolution
- 109. Pain-Oriented EventStorming Focus on Explorenormally foggy areas Let an action plan emerge! Pain Point Someone else’s pain point
- 110. Pain Oriented Show thewhole flow Display the pain Explore Choose Eve Pai
- 111.
- 112. best advice comesfrom KEEP YOUR MOUTH SHUT
- 113.
- 114. Impact Mapping What isthe expected outcome?
- 115.
- 116. POES as retrospectivebackground Big Picture first Retrospective scope explicitly widened Facilitated root cause analysis Hints for collaboration
- 118. As a learningtool Every new hire in avanscoperta gets an EventStorming session The result is visible on the wall … I am here! :-)
- 119.
- 120.
- 121.
- 122. Many others arepointing here… -Lean Startup -Lean UX -Popcorn Flow -Small Controlled Experiments -Modellathlon
- 123.
- 124. Modelling Sympathy Don’t know whatit means but sounds so cool
- 125.
- 126.
- 128. class Customer attr_reader :name, :surname, :address, :picture, :email, :id, :status #... end <— The system will probably care only about this one <— User will need to see all these..
- 129. Yep, there isno such thing as “the model”
- 130.
- 131.
- 132.
- 133.
- 134.
- 135. Aggregate Aggregate Command Command Event Event Event Event Event Event EventEvent Event store Domain Model Projection Projection ReadModel DTO DTO Presentation UI UI UI UI Old picture… please ignore the colors
- 136. It’s not aboutspeed
- 138.
- 140. “… and afteryou mixed the ingredients, now separate them”
- 141.
- 142. UI Constraints Item pageProjection (readmodel) Command User Price Special offer!
- 143. Can I influencethe user decision? UX Readability Information Images Speed
- 144. Can I improvethe quality of the user decision? UX Readability Information Images Speed
- 145.
- 147. Can I improve processes? Reliability SpeedAutomation Composability
- 148.
- 149.
- 150. Design Level Active collaboration Wisdomof the crowd Visually consistent models Big visible
- 151.
- 153. I m ean it! If you don’tI am gonna find where you live!
- 154. Hey, you mentioned… …the greenbar #Developer #DDD #Agile
- 155. Cucumber to the rescue ScenarioOutline: Manually opening a project finances account When I open a project account called <project name> Then project account should be opened for <project name> And project <project name> should be visible in the projects list Examples: | project name | | Project Alpha | | Project Omega |
- 156. Executing a Command When(/^Iopen a project account called (.*)$/) do |project_name| params = { 'headline' => project_name } command = OpenProject.from_params(params) @project_account_id = command.aggregate_id Quindi::Application::ProjectFinancesCommandHandler.handle(command) end
- 157. Checking a DomainEvent Then(/^project account should be opened for (.*)$/) do |expected_headline| eventually(timeout: 0.8) { last_project_opened_event = @event_logger.received['ProjectOpened'].last expect(last_project_opened_event).to_not be_nil expect(last_project_opened_event).to be_a ProjectOpened expect(last_project_opened_event.headline).to eq expected_headline } end
- 158. Checking a ReadModel And(/^project (.*) should be visible in the projects list$/) do |project_name| fail 'Please set @project_account_id ' unless @project_account_id eventually(timeout: 0.5) { visible_project = Quindi::Application::ProjectList.find_by_id(@project_account_id) expect(visible_project).not_to be_nil expect(visible_project['headline']).to eq project_name } end
- 159. Wrapping up Doing theright thing matters Doing it right matters too Discovering it matters too Have a look to CQRS/ES EventStorming Friends
- 161.
- 162.
- 163.