Evolution of Architectural Work

Transcript

1. Evolution of Architectural Work 1 | Date: 2023 Author: Felix Rieß EVOLUTION OF ARCHITECTURAL WORK
2. FELIX RIESS Software Architect felix.riess@bcxp.de https://speakerdeck.com/felix185
4. Fundamental concepts or properties of a system in its environment embodied in its elements, relationships and in the principles of its design and evolution. ISO/IEC/IEEE 42010 Evolution of Architectural Work 4 |
5. All architecture is design, but not all design is architecture. Architecture represents the set of significant design decisions that shape the form and the function of a system, where significant is measured by the cost of change. GRADY BOOCH Evolution of Architectural Work 5 |
6. Architecture is about the important stuff. Whatever that is. RALPH JOHNSON Evolution of Architectural Work 6 |
7. Software architecture is the set of design decisions which, if made incorrectly, may cause your project to be cancelled. EOIN WOODS Evolution of Architectural Work 7 |
8. Evolution of Architectural Work 8 | Software Architecture represents the set of significant decisions.
9. Evolution of Architectural Work 9 |
10. Evolution of Architectural Work 10 | Decisions System Design Tech-Stack Environment Approach
11. Evolution of Architectural Work 11 | Quality Attributes (ISO 25010) Performance Efficiency Functional Suitability Compatibility Operability Portability Maintainability Security Reliability
12. Evolution of Architectural Work 12 | Decisions Software Architecture Quality Goals Set of significant influence
13. Evolution of Architectural Work 13 | Decisions Software Architecture Quality Goals Set of significant Constraints restrict influence
14. A long time ago in a galaxy not so far away… Evolution of Architectural Work 14 | https://www.indeed.com/career-advice/career-development/waterfall-project-management
15. Evolution of Architectural Work 15 | https://wiki.eclipse.org/EclipseLink/Development/Architecture/EclipseLink/ClassDiagram
17. Evolution of Architectural Work 17 | https://en.wikipedia.org/wiki/Cynefin_framework#/media/File:Cynefin_framework_2022.jpg
18. Benefits of Agile Evolution of Architectural Work 18 | More Flexibility Higher Product Quality Faster Time to Market Higher Visibility & Transparency Less Risk
19. Agile Manifesto Individuals and interactions over Processes and tools Working software over Comprehensive documentation Customer collaboration over Contract negotiation Responding to change over Following a plan Evolution of Architectural Work 19 |
20. Agile Manifesto – slightly adjusted Processes and tools for Individuals and interactions Useful documentation for Working Software Contract negotiation for Customer collaboration Enough plan for Responding to change Evolution of Architectural Work 20 |
21. Continuous attention to technical excellence and good design enhances agility Evolution of Architectural Work 21 | PRINCIPLES BEHIND THE AGILE MANIFESTO
22. Architectural work Risks
23. Architecture Vision Evolution of Architectural Work 23 | What? How?
24. Architecture Vision Evolution of Architectural Work 24 | What? System context Constraints Quality goals (prioritized) Risks
25. Architecture Vision Evolution of Architectural Work 25 | How? Big picture Concepts, patterns, principles Base technologies Hypotheses
26. Evolution of Architectural Work 26 | https://canvas.arc42.org/architecture-inception-canvas
27. Evolution of Architectural Work 27 | https://canvas.arc42.org/architecture-communication-canvas
28. Big design up front is dumb. Doing no design up front is even dumber. DAVE THOMAS Evolution of Architectural Work 28 |
29. Evolution of Architectural Work 29 | Architecture Vision instead of Big Design Up Front!
30. Last reasonable Moment Evolution of Architectural Work 30 | Time Risk/Question LRM x x
31. A Walking Skeleton is a tiny implementation of the system that performs a small end-to-end function. It need not use the final architecture, but it should link together the main architectural components. The architecture and the functionality can the evolve in parallel. ALISTAIR COCKBURN Evolution of Architectural Work 31 |
33. From Quality Goals to Scenarios Evolution of Architectural Work 33 | https://faq.arc42.org/questions/C-10-2/
34. Different Scenario Types • Use-Case-Scenario • What happens during normal use of the system? • Scenario of change • How is the system evolving? • Failure scenario • How does the system respond to unexpected events? Evolution of Architectural Work 34 |
35. Why Quality Scenarios? Evolution of Architectural Work 35 | Transparency Architectural Decisions Architectural Reviews Communication Acceptance Tests
36. Categories of Quality Scenarios Architectural relevance Isolated Implementability Acceptance Criteria Quality Stories Gap of Principles Evolution of Architectural Work 36 |
37. Quality Scenarios in the Backlog • Acceptance Criteria • Part of concerning user stories • Quality Story • Own user story • Gap in Principles • Own user story: Definition of principle Evolution of Architectural Work 37 |
38. Obligation that a software organization incurs when it chooses a design or construction approach that’s expedient in the short term but that increases complexity and is more costly in the long term. STEVE MCCONNELL Evolution of Architectural Work 38 |
39. Types of Technical Debt Evolution of Architectural Work 39 | Architecture Code Test
40. How Technical Debt arises Evolution of Architectural Work 40 | https://martinfowler.com/bliki/TechnicalDebtQuadrant.html
41. How to handle Technical Debt Evolution of Architectural Work 41 | List of Technical Debt Elimination profitable? Debt restructuring profitable? Archiving Technical Debt Scenarios with urgency No No Yes Yes
42. Working with the Backlog Evolution of Architectural Work 42 | Story B Gap of Principles Quality Story Technical Debt Story C Acceptance Criteria Story A
44. The best architectures, requirements, and designs emerge from self-organizing teams. Evolution of Architectural Work 44 | PRINCIPLES BEHIND THE AGILE MANIFESTO
45. Cross-Functional Teams Evolution of Architectural Work 45 | Problem Solution
46. Interpretations of the Architect‘s role No named Architect Evolution of Architectural Work 46 |
47. Interpretations of the architect‘s role Architect Agents Evolution of Architectural Work 47 |
48. Interpretations of the architect‘s role Supporting Architect Evolution of Architectural Work 48 |
49. Interpretations of the architect‘s role Classical architect Evolution of Architectural Work 49 |
50. When to use what? Evolution of Architectural Work 50 | Architectural frame, external dependencies, experience, familiarity Project size, distribution, business domain, technical domain Discipline, organizational structure, goals, environment
51. Contact Person Raise Questions Architecture Owner Evolution of Architectural Work 51 | Contribute Context Escalate Problems Know-how Transfer Organization/ Coordination
53. • Verticals • Responsibility • Anti-Viscosity • Communication Governance 2.0 Evolution of Architectural Work 53 |
54. Wrap-up • Risk-oriented • Empirical • Working with the Backlog • Architecture Owner • Governance 2.0 Evolution of Architectural Work 54 |
55. FELIX RIESS Software Architect felix.riess@bcxp.de https://speakerdeck.com/felix185
56. References • http://www.iso-architecture.org/ieee-1471/defining- architecture.html • https://twitter.com/Grady_Booch/status/1459007228954832 896?lang=de • https://www.oreilly.com/library/view/software-architects- handbook/9781788624060/70f73094-77a1-44f5-85d7- d36f393bc906.xhtml#:~:text=Computer%20scientist%20Ra lph%20Johnson%2C%20who,Whatever%20that%20is.%2 2 • http://www.softwarearchitectures.com/overview.html • https://iso25000.com/index.php/en/iso-25000- standards/iso-25010 • https://agilemanifesto.org/iso/en/manifesto.html • https://agilemanifesto.org/iso/en/principles.html • https://dev.to/simonbrown/software-architecture-isn-t- about-big-design-up-front-4hol • https://wiki.c2.com/?WalkingSkeleton • https://www.construx.com/wp- content/uploads/2019/02/CxWhitePaper_TechnicalDebt.pdf Evolution of Architectural Work 56 |
57. Images • https://unsplash.com/de/fotos/QdAAasrZhdk • https://unsplash.com/de/fotos/rsGd-rXFGkM • https://unsplash.com/de/fotos/1K9T5YiZ2WU • https://unsplash.com/de/fotos/bH7kZ0yazB0 • https://unsplash.com/de/fotos/kn-UmDZQDjM • https://unsplash.com/de/fotos/98MbUldcDJY • https://unsplash.com/de/fotos/wxWulfjN-G0 • https://unsplash.com/de/fotos/p6rNTdAPbuk • https://unsplash.com/de/fotos/Zyx1bK9mqmA • https://unsplash.com/de/fotos/VBPzRgd7gfc Evolution of Architectural Work 57 |
58. Thank you! Wenn aus Technik Freundschaft wird