Pragmatic Architecture (SATURN 2017)
•
2 likes•790 views
Third iteration of my pragmatic architecture talk. This version is tailored for architects. I presented it at the SATURN 2017 conference in Denver, Colorado. Software development has evolved. Agile is now the de-facto standard. The role of an architect in an agile project is very different than the typical role in a more classic waterfall approach. Using an updated interpretation of ‘viewpoints and perspectives’, this talk will demonstrate how to make rapid, agile delivery sustainable. These viewpoints and perspectives will be linked to easy-to-produce models that can be used immediately in your projects. The talk will provide examples on how to determine which models are architecturally significant and worth the effort. Developers have always been very important stakeholders of an architectural description. A good agile architect needs to strive for consensus and buy-in.
Recommended
Recommended
More Related Content
Similar to Pragmatic Architecture (SATURN 2017)
Similar to Pragmatic Architecture (SATURN 2017) (20)
More from Bart Blommaerts
More from Bart Blommaerts (15)
Recently uploaded
Recently uploaded (20)
Pragmatic Architecture (SATURN 2017)
- 1. PRAGMATIC ARCHITECTURE, TODAY BART BLOMMAERTS @DAGGIEBE SATURN, 2017-05-02
- 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. A SYSTEM IS MORE THAN THE SUM OF ITS PARTS; IT IS AN INDIVISIBLE WHOLE. IT LOSES ITS ESSENTIAL PROPERTIES WHEN IT IS TAKEN APART. Russell L.Ackoff PRAGMATIC ARCHITECTURE, TODAY
- 18. BE PART OF THE TEAM ACTIVITY OVER ROLE
- 19. AS A TEAM ▸ Facilitating ▸ Collaborating ▸ Modelling ▸ Sharing ▸ Resolving ▸ Improving ▸ … PRAGMATIC ARCHITECTURE, TODAY
- 21. YES EXPERIENCE THE SAME PAIN AS EVERYBODY ELSE ON THE TEAM
- 22. ▸ Support and coaching ▸ Best practices ▸ Code reviews ▸ Proof of Concepts ▸ Reusable building blocks ▸ Etc. CODE PRAGMATIC ARCHITECTURE, TODAY
- 25. ONE CANNOT SEE THE OCEAN'S CURRENTS BY STUDYING DROPS OF WATER. Grady Booch PRAGMATIC ARCHITECTURE, TODAY
- 26. VISUALISATION - GOAL ▸ Consistency ▸ Reporting ▸ Checking and validation ▸ Sharing information PRAGMATIC ARCHITECTURE, TODAY
- 27. 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
- 28. VISUALISATION - GROUND RULES ▸ Decision log ▸ Document your decisions and alternatives ▸ Avoid fluffy diagrams ▸ Avoid mixed abstractions ▸ Only document what’s useful PRAGMATIC ARCHITECTURE, TODAY
- 30. WHY? UP-FRONT DESIGN PRAGMATIC ARCHITECTURE, TODAY 01
- 31. 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
- 32. JUST ENOUGH UP FRONT DESIGN TO CREATE FIRM FOUNDATIONS FOR THE SOFTWARE PRODUCT AND ITS DELIVERY. Simon Brown PRAGMATIC ARCHITECTURE, TODAY
- 33. JUST ENOUGH?
- 34. JUST ENOUGH? ▸ Greenfield ▸ All the components of the system ▸ High-level ▸ Show the whole system ▸ Add details later ▸ White board diagram PRAGMATIC ARCHITECTURE, TODAY
- 35. JUST ENOUGH? GREENFIELD PRAGMATIC ARCHITECTURE, TODAY
- 36. JUST ENOUGH? ▸ Existing system ▸ As-is situation ▸ Domain of change ▸ Extension points PRAGMATIC ARCHITECTURE, TODAY
- 37. WHY? COMMUNICATION PRAGMATIC ARCHITECTURE, TODAY 01 02
- 38. COMMUNICATION ▸ During inception ▸ Many stakeholders ▸ Many desires ▸ Many questions … PRAGMATIC ARCHITECTURE, TODAY
- 39. ▸ During development process ▸ Sharing a technical vision ▸ Everybody collaborates to the same end-goal ▸ Leave your ego at the door COMMUNICATION PRAGMATIC ARCHITECTURE, TODAY
- 40. WHY? POLITICS PRAGMATIC ARCHITECTURE, TODAY 03 01 02
- 41. POLITICS ▸ Decisions ▸ Stakeholders will question many decisions ▸ Focus on system integrity ▸ Fear of change at corporate IT ▸ Creating systems “nobody wants to touch” ▸ Play the game … PRAGMATIC ARCHITECTURE, TODAY
- 42. WHY? MAKE DECISIONS EXPLICIT PRAGMATIC ARCHITECTURE, TODAY 04 03 01 02
- 45. OODA
- 46. OBSERVE
- 47. ORIENT
- 48. DECIDE
- 49. ACT
- 50. OODA - EXAMPLE ▸ Context view PRAGMATIC ARCHITECTURE, TODAY
- 51. ▸ Context view OODA - EXAMPLE PRAGMATIC ARCHITECTURE, TODAY
- 52. OODA - EXAMPLE ▸ Context view PRAGMATIC ARCHITECTURE, TODAY
- 53. ▸ Context view OODA - EXAMPLE PRAGMATIC ARCHITECTURE, TODAY
- 54. ▸ System composition ▸ Measuring value ▸ Application-driven ▸ Capturing data RUNTIME OBSERVATIONS PRAGMATIC ARCHITECTURE, TODAY
- 55. 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