Pragmatic Architecture, Today (v2)
3 likes•2,143 views
The document discusses pragmatic architecture, emphasizing the need for architectural viewpoints, stakeholder involvement, and iterative communication throughout the software development process. It highlights the importance of visualizations, decision logging, and just enough up-front design to build effective software systems that can evolve over time. Additionally, it addresses challenges related to politics and stakeholder engagement in architectural decision-making.
Pragmatic Architecture, Today (v2)
- 1. PRAGMATIC ARCHITECTURE, TODAY BART BLOMMAERTS @DAGGIEBE
- 2. BART BLOMMAERTS ▸ Application Architect ▸ Ordina Belgium ▸ JWorks ▸ @DaggieBe PRAGMATIC ARCHITECTURE, TODAY
- 9. VIEWPOINTS ▸ Context ▸ Functional ▸ Information ▸ Concurrency ▸ Development ▸ Deployment ▸ Operational PRAGMATIC ARCHITECTURE, TODAY
- 11. ▸ Accessibility ▸ Availability and Resilience ▸ Development Resource ▸ Evolution ▸ Internationalization PERSPECTIVES ▸ Location ▸ Performance and Scalability ▸ Regulation ▸ Security ▸ Usability PRAGMATIC ARCHITECTURE, TODAY
- 15. ARCHITECTURE REPRESENTS THE SIGNIFICANT DESIGN DECISIONS THAT SHAPE A SYSTEM, WHERE SIGNIFICANT IS MEASURED BY COST OF CHANGE. Grady Booch PRAGMATIC ARCHITECTURE, TODAY
- 17. BE PART OF THE TEAM ACTIVITY OVER ROLE
- 18. AS A TEAM ▸ Facilitating ▸ Collaborating ▸ Modelling ▸ Sharing ▸ Resolving ▸ Improving ▸ … PRAGMATIC ARCHITECTURE, TODAY
- 20. YES EXPERIENCE THE SAME PAIN AS EVERYBODY ELSE ON THE TEAM
- 21. ▸ Support and coaching ▸ Best practices ▸ Code reviews ▸ Proof of Concepts ▸ Reusable building blocks ▸ Etc. CODE PRAGMATIC ARCHITECTURE, TODAY
- 24. ONE CANNOT SEE THE OCEAN'S CURRENTS BY STUDYING DROPS OF WATER. Grady Booch PRAGMATIC ARCHITECTURE, TODAY
- 25. VISUALISATION - GOAL ▸ Consistency ▸ Reporting ▸ Checking and validation ▸ Sharing information PRAGMATIC ARCHITECTURE, TODAY
- 26. VISUALISATION - GROUND RULES ▸ UML is usually not necessary ▸ Can be used for model-driven development ▸ Boxes and lines ▸ Be consistent ▸ Provide a legend ▸ Make sure stakeholders understand PRAGMATIC ARCHITECTURE, TODAY
- 27. VISUALISATION - GROUND RULES ▸ Decision log ▸ Document your decisions and alternatives ▸ Avoid fluffy diagrams ▸ Avoid mixed abstractions ▸ Only document what’s useful PRAGMATIC ARCHITECTURE, TODAY
- 29. UP-FRONT DESIGN ▸ Think about the big picture ▸ eg. used technology ▸ automation ▸ patterns (monolith, distributed, …) ▸ layering ▸ And it’s evolution ▸ But … be pragmatic PRAGMATIC ARCHITECTURE, TODAY
- 30. JUST ENOUGH UP FRONT DESIGN TO CREATE FIRM FOUNDATIONS FOR THE SOFTWARE PRODUCT AND ITS DELIVERY. Simon Brown PRAGMATIC ARCHITECTURE, TODAY
- 31. JUST ENOUGH?
- 32. JUST ENOUGH? ▸ Greenfield ▸ All the components of the system ▸ High-level ▸ Add details later PRAGMATIC ARCHITECTURE, TODAY
- 33. JUST ENOUGH? GREENFIELD PRAGMATIC ARCHITECTURE, TODAY
- 34. JUST ENOUGH? ▸ Existing system ▸ As-is situation ▸ Domain of change ▸ Extension points PRAGMATIC ARCHITECTURE, TODAY
- 35. COMMUNICATION ▸ During inception ▸ Many stakeholders ▸ Many desires ▸ Many questions … PRAGMATIC ARCHITECTURE, TODAY
- 36. ▸ During development process ▸ Sharing a technical vision ▸ Everybody collaborates to the same end-goal COMMUNICATION PRAGMATIC ARCHITECTURE, TODAY
- 37. POLITICS ▸ Decisions ▸ Stakeholders will question many decisions ▸ Focus on the system as a whole ▸ Fear of change at corporate IT ▸ Creating systems “nobody wants to touch” PRAGMATIC ARCHITECTURE, TODAY
- 40. OODA
- 41. ▸ Observation ▸ Orientation ▸ Decision ▸ Action OODA PRAGMATIC ARCHITECTURE, TODAY
- 42. OODA - EXAMPLE ▸ Context view PRAGMATIC ARCHITECTURE, TODAY
- 43. ▸ Context view OODA - EXAMPLE PRAGMATIC ARCHITECTURE, TODAY
- 44. OODA - EXAMPLE ▸ Context view PRAGMATIC ARCHITECTURE, TODAY
- 45. ▸ Context view OODA - EXAMPLE PRAGMATIC ARCHITECTURE, TODAY
- 46. ▸ System composition ▸ Cloud-native? Microservice dashboard ▸ Measuring value ▸ Application-driven ▸ Capturing data RUNTIME OBSERVATIONS PRAGMATIC ARCHITECTURE, TODAY
- 47. READING MATERIAL ▸ Software Systems Architecture by Rozanski and Woods ▸ 37 Things One Architect Knows About IT Transformation by Gregor Hohpe ▸ Continuous architecture by Pureur and Erder ▸ Bredemeyer consulting - http://www.bredemeyer.com/ ▸ Form follows function - https://genehughson.wordpress.com/ ▸ A trace in the sand - http://www.ruthmalan.com/Journal/ JournalCurrent.htm ▸ Coding the architecture - http://www.codingthearchitecture.com/ ▸ Continuous architecture in practice - https://pgppgp.wordpress.com/ ▸ Who needs an architect? - http://martinfowler.com/ieeeSoftware/ whoNeedsArchitect.pdf PRAGMATIC ARCHITECTURE, TODAY