Reducing Technical Debt in Software Architecture

1. Reducing Technical Debt in Software Architecture Florian Stefan ● @f_s_t_e_f_a_n

2. Reducing Technical Debt in Software Architecture

3. Reducing Technical Debt in Software Architecture Platform Business Model

5. Linear Business Model Reducing Technical Debt in Software Architecture

6. Screaming Architecture “Just as the plans for a house or a library scream about the use cases of those buildings, so should the architecture of a software application scream about the use cases of the application.” (Robert C. Martin) Reducing Technical Debt in Software Architecture

8. Legacy Software “Having legacy software is often a sign of success. Your business was successful to last long enough for your software to become legacy.” (Sam Newman) Reducing Technical Debt in Software Architecture

9. C ase Stud y Reducing Technical Debt in Software Architecture

10. C a se Stu d y Reducing Technical Debt in Software Architecture

13. C ase Stud y Reducing Technical Debt in Software Architecture

17. Reducing Technical Debt in Software Architecture Legacy “Systems & Functions with a design contrary to architectural principles.”

18. Reducing Technical Debt in Software Architecture Technical Debt “Legacy Systems & Functions that could threaten our business success.”

19. (Dr. Carola Lilienthal) Reducing Technical Debt in Software Architecture

42. Reducing Technical Debt in Software Architecture Rigidity Fragility Repetition Complexity

49. Communicator Leader Developer Systems Focused Entrepreneur Strategic Technologist (Patrick Kua) Reducing Technical Debt in Software Architecture

50. Strategy Principles Practices Reducing Technical Debt in Software Architecture

52. Architectural Principles Technical Debt Report Clearance Commitment Balanced Scorecard Clearance Sponsoring Reducing Technical Debt in Software Architecture

56. changes for different reasons Reducing Technical Debt in Software Architecture

62. Principles PracticesStrategy Organize around Business Capabilities “Develop a ubiquitous language inside bounded contexts - the maximal extent of a concept so that the concept remains consistent.”

63. Principles PracticesStrategy Event Storming Domain Storytelling Organizational Structure Customer Touchpoints

73. Principles PracticesStrategy Shared Kernel Customer/ Supplier Published Language Anticorruption Layer Conformist

91. changes for different reasons changes at different rates Reducing Technical Debt in Software Architecture

92. Principles PracticesStrategy DRY Principle “Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.” (Andy Hunt, Dave Thomas)

111. Silver Bullets “A good developer is like a werewolf: afraid of silver bullets.” (Jochen Mader) Reducing Technical Debt in Software Architecture

112. Thank you! Reducing Technical Debt in Software Architecture

Reducing Technical Debt in Software Architecture

More Related Content

Similar to Reducing Technical Debt in Software Architecture (20)

Recently uploaded (20)

Reducing Technical Debt in Software Architecture