Making significant software architecture decisions
0 likes125 views
Presented at the NLKUG meetup on 9/4/2025.
More Related Content
Similar to Making significant software architecture decisions (20)
Recently uploaded (20)
![Movavi Video Editor Crack + Activation Key [2025]](https://cdn.slidesharecdn.com/ss_thumbnails/simunsunjiclovromatosevic-250216112916-e19beeba-250404023804-5918a24a-250407081855-ec0bae8c-thumbnail.jpg?width=560&fit=bounds)
![Parallels Desktop Crack [Latest] 2025 free](https://cdn.slidesharecdn.com/ss_thumbnails/worlddayofbullyingpreventionactivitiesinfographicsbyslidesgo-250228090445-a5019b4d-250403064534-1338-250406211207-5ba8239d-thumbnail.jpg?width=560&fit=bounds)
Making significant software architecture decisions
- 1. bertjan@openvalue.eu Making significant software architecture decisions Bert Jan Schrijver @bjschrijver.dev
- 2. Bert Jan Schrijver L e t s m e e t @bjschrijver.dev
- 3. Lets talk about software.
- 4. What is software architecture?
- 5. Software architecture == making decisions
- 7. On what?!!
- 8. Weve always done it like this We dont want to do depend on <x> We need to be future proof Because the product owner wants it Because the architect wants it Bad (reasons for) architecture decisions
- 9. Source: https://7216-presscdn-0-76-pagely.netdna-ssl.com/wp-content/uploads/2011/12/confused-man-single-good-men.jpg So how do you make architecture decisions?
- 11. On what?!!
- 12. Start with the 5 Ws Why are we even here as architects? To enable one or more teams to build something Why? To help a business reach their goals Why? Because thats why we even have a job ! Every architecture decision has a business component Input for architecture decisions Background source: GR Stocks on Unsplash
- 13. Requirements Functional Non-functional / quality attributes (Business) constraints Which of these impact our architecture the most? But: we can never fully fulfil them all So we always need to consider trade-offs between requirements & constraints Input for architecture decisions Source: https://medium.com/@jeffwhelpley/the-problem-with-shared-code-124a20fc3d3b
- 14. Quality attributes (non functionals) Which quality attributes do you now? Performance, security, availability, reliability In general: ISO 25010
- 15. ISO 25010
- 16. Which requirements or constraints are the most important?
- 18. On what?!!
- 19. On your business. But how do you prioritise?
- 20. Trade-off analysis for software architecture Source: https://images.unsplash.com/photo-1515611926865-4fcb1c2ce28d?ixlib=rb-4.0.3&dl=kelly-sikkema-kxtB2TFBF2g-unsplash.jpg&q=80&fm=jpg&crop=entropy&cs=tinysrgb Gather requirements, quality attributes & constraints Select potential solutions Discover and weigh trade-offs Pick the best fitting solution Described in Software Architecture: The Hard Parts by Ford, Richards et al
- 21. Security vs. usability Configurability vs. maintainability Availability vs. cost Performance vs. cost Performance vs. maintainability Runtime configuration vs. robustness Examples of trade-offs Background source: DALL揃E
- 22. Every architecture decision is a trade-off
- 24. Example: tradeoff analysis Source: Neal Ford - Modern Trade-off Analysis for Software Architecture - DDD Europe
- 25. Example: tradeoff analysis Source: Neal Ford - Modern Trade-off Analysis for Software Architecture - DDD Europe
- 26. Example: tradeoff analysis Source: Neal Ford - Modern Trade-off Analysis for Software Architecture - DDD Europe
- 27. Example: tradeoff analysis Source: Neal Ford - Modern Trade-off Analysis for Software Architecture - DDD Europe
- 28. Which requirements and tradeoffs should you consider?
- 29. Relevant quality attributes See ISO 25010 Technical factors Source: http://www.nasa.gov/images/content/218652main_STOCC_FS_img_lg.jpg
- 30. Developer experience Learning curve Tool & IDE support Documentation & support Integration with current landscape Organisational factors Adoption, popularity & expertise: own team industry Long-term viability (Active development, community & ecosystem)
- 31. Business factors Background source: DALL揃E Cost Infrastructure Licenses Support Engineers TCO Time-to-market Migration cost vs benefits after migration Productivity Regulatory reqs, legal, IP risk Exit strategy
- 32. When not to compromise? When risking irreversible damage to your business. Photo: Dave Lehl
- 33. Summary
- 34. Gather requirements & constraints Brainstorm for possible solutions Consider technical, organisational and business factors Discover and weigh trade-offs Pick the best fitting solution Significant software architecture decisions
- 35. How to make architecture decisions? It depends.
- 36. On the informed trade-offs you make. Source: https://images.unsplash.com/photo-1515611926865-4fcb1c2ce28d?ixlib=rb-4.0.3&dl=kelly-sikkema-kxtB2TFBF2g-unsplash.jpg&q=80&fm=jpg&crop=entropy&cs=tinysrgb
- 37. Source: https://cdn2.vox-cdn.com/thumbor/J9OqPYS7FgI9fjGhnF7AFh8foVY=/148x0:1768x1080/1280x854/cdn0.vox-cdn.com/uploads/chorus_image/image/46147742/cute-success-kid-1920x1080.0.0.jpg THATS IT. NOW GO KICK SOME ASS!
- 39. Thanks for your time. Got feedback? Let me know! All pictures belong to their respective authors @bjschrijver.dev meetup.com/isaqb-nl