Architecture technical debt demystified [rus]
Architectural technical debt is the weight of all design choices made in the past that are slowing down progress. Structure, framework, technologies — it could be anything that no longer serves its original purpose. Unlike code-level technical debt, which can be detected by static analyzers and often fixed with minimal or only incremental changes, architectural debt is hard to detect and the resolution process is difficult. My talk will cover how to measure, identify and communicate architectural debt in a fast-changing environment.
Main topics:
- Architectural debt and its place in technical debt
- Top 5 Reasons of Architectural Debt
- How to Manage Architectural Debt (Manual and Automatic Tools)
- To be or not to be? Decision-Making Techniques to Remediate Architectural Debt
Oleksandra Dudka
Sigma Software
- Software Architect at Sigma Software
- Oleksandra has over 15 years of experience in IT. Her passion is to create value for products by solving challenging business problems, designing solutions, leading groups of professionals in fast-developing startup environments
- A researcher and has Ph.D. in Information Security. As a next step this year, she has started working on a doctoral dissertation in Software Architecture Methodologies, and she is awesomely excited about this
- It's not the end. Among all the activities, as the associate professor, she is fully engaged in developing the master's program in Software Architecture at the Kharkiv National University of Radio Electronics