Resolving technical debt in software architecture
•
4 likes•956 views
Today programmers do not develop applications from scratch, but they spend their time fixing, extending, modifying and enhancing existing applications. The biggest problem in their daily work is that with time maintenance mutates from structured programming to defensive programming: The code becomes too complex to be maintained. We put in code we know is stupid from an architectural point of view but it is the only solution that will hopefully work. Maintenance is more and more difficult and expensive. Our software accumulates technical debts. In this talk, you will see how you should improve your architecture and source code to prevent technical debt growing unrestricted. With the proper knowledge about well-structured architecture, refactorings for tangled code can quickly be found. Complex code can be eliminated, and maintenance costs will be reduced.
Recommended
Recommended
More Related Content
Similar to Resolving technical debt in software architecture
Similar to Resolving technical debt in software architecture (20)
More from Carola Lilienthal
More from Carola Lilienthal (13)
Recently uploaded
Recently uploaded (20)
Resolving technical debt in software architecture
- 1. WPS - Workplace Solutions GmbH //// Hans-Henny-Jahnn-Weg 29 //// 22085 HAMBURG Resolving technical debt in software architecture Dr. Carola Lilienthal Carola.Lilienthal@wps.de, @cairolali www.wps.de
- 3. @cairolali
- 4. @cairolali 7 41 63 128 72 bis 15 Mio bis 5 Mio bis 1 Mio bis 500.000 bis 100.000
- 5. @cairolali HOW DO WE SPEND OUR TIME? 70% 20% 10% Code verstehen Problem lösen Code schreiben Code comprehension Problem solving Writing code
- 6. @cairolali WELL-FORMED COMPLEX STRUCTURES = SAVING TIME! Cognitive Mechanisms HierarchiesChunking Schemata
- 7. @cairolali
- 8. @cairolali WELL-FORMED COMPLEX STRUCTURES = SAVING TIME! Cognitive Mechanisms HierarchiesChunking Schemata Well-formed architecture Modularity
- 9. @cairolali MODULARITY ▪High Cohesion and lose Coupling ▪Responsibility Driven Design ▪Separation of Concerns ▪Single Responsibility Principle
- 10. @cairolali WELL-FORMED COMPLEX STRUCTURES = SAVING TIME! Cognitive Mechanisms HierarchiesChunking Schemata Well-formed architecture Modularity
- 12. @cairolali WELL-FORMED COMPLEX STRUCTURES = SAVING TIME! Cognitive Mechanisms HierarchiesChunking Schemata Well-formed architecture Modularity Hierarchical Layerng
- 13. @cairolali
- 14. @cairolali WELL-FORMED COMPLEX STRUCTURES = SAVING TIME! Cognitive Mechanisms HierarchiesChunking Schemata Well-formed architecture Modularity Hierarchical Layerng Pattern Consistency
- 15. @cairolali WRONG PATTERN STOP THE FLOW Domain Module Model View Con trol ValueObject Service BusinessObject Factory ✓ createBusinessObject() ✓ createValueObject() × calculate(BO) × process(BO)
- 16. @cairolali WELL-FORMED COMPLEX STRUCTURES = SAVING TIME! Cognitive Mechanisms HierarchiesChunking Schemata Well-formed architecture Modularity Hierarchical Layerng Pattern Consistency
- 17. @cairolali
- 18. @cairolali TWO DIMENSIONS IN ON ARCHITECTURE Technical layering Domain layering Tree violations that are easy to resolve Difficult violations One component cuasing several problems One component causing a problem
- 19. @cairolali DOMAIN LAYERING IS MISSING Technical layering No domain layering Some violations of the technical layering Allmost all domain components need each other
- 20. @cairolali 119 classes from 4 components + 28 other classes
- 21. @cairolali 327 classes from 8 components That all need each other
- 23. @cairolali WELL-FORMED COMPLEX STRUCTURES = SAVING TIME! Cognitive Mechanisms HierarchiesChunking Schemata Well-formed architecture Modularity Hierarchical Layerng Pattern Consistency
- 26. @cairolali DOMAIN MODULES? Models integrated in UseCasesUseCase-Driven
- 27. @cairolali UNEVEN MODULES 9 Components = 17 Subsystems
- 28. @cairolali 128 BUILD UNITS WITH NUMBER OF CLASSES ▪ 3 Mio of 9 Mio LOC ▪ 1/3 of the system
- 29. @cairolali 5.270 CLASSES IN ONE CYCLE IN ONE BUILDUNIT
- 30. @cairolali WELL-FORMED COMPLEX STRUCTURES = SAVING TIME! Cognitive Mechanisms HierarchiesChunking Schemata Well-formed architecture Modularity Hierarchical Layering Pattern Consistency
- 32. @cairolali PATTERN CONFORMITY: GOOD EXAMPLE ☺ 90% of the source code can be assigned to pattern ☺ 0,1% violations between the pattern Eventer Processes Service
- 33. @cairolali
- 34. 463 tangled classes belonging to 10 different components
- 37. @cairolali184 tangled classes left
- 38. @cairolali
- 39. @cairolali WELL-FORMED COMPLEX STRUCTURES = SAVING TIME! Cognitive Mechanisms HierarchiesChunking Schemata Modularity Hierarchical Layerng Pattern Consistency → Consistent and integrated pattern → Use a pattern language → No cycles neither on architectural level nor on class level → responsibility → coupling → size → interfaces
- 40. @cairolali 612.869 LOC 14.756.435 LOC 252.062 LOC 804.093 LOC 543.388 LOC 1.035.668 LOC 486.358 LOC 175.258 LOC 42.311 LOC 193.383 LOC 643.466 LOC 245.754 LOC 2.890.204 LOC 141.696 LOC 512.086 LOC 9.988.363 LOC 200.591 LOC 922.949 LOC 22.658 LOC 663.862 LOC 3.270.188 LOC 1.521.357 LOC 0 2 4 6 8 10 MODULARITY MATURITY INDEX (MMI)
- 41. @cairolali @cairolali cl@wps.de Available in English Summer 2019 www.langlebige-softwarearchitekturen.de www.sustainable-software-architecture.com THANK YOU FOR YOUR ATTENTION!