Visualising architectural dependencies

@article{Brndum2012VisualisingAD,
  title={Visualising architectural dependencies},
  author={Johan Br{\o}ndum and Liming Zhu},
  journal={2012 Third International Workshop on Managing Technical Debt (MTD)},
  year={2012},
  pages={7-14}
}
  • J. Brøndum, Liming Zhu
  • Published 5 June 2012
  • Computer Science
  • 2012 Third International Workshop on Managing Technical Debt (MTD)
Visibility of technical debt is critical. A lack thereof can lead to significant problems without adequate visibility as part of the system level decision-making processes [2]. Current approaches for analysing and monitoring architecture related debt are based on dependency analysis to detect code level violations of the software architecture [2,3,6]. However, heterogeneous environments with several systems constructed using OTS, and/or several programming languages may not offer sufficient… 
DepMiner: A Pipelineable Tool for Mining of Intra-Project Dependencies
TLDR
DepMiner is an open source, language-agnostic tool for mining detailed dependencies data from source code, based on extensive static analysis capabilities of an industry standard IDE, and can be easily integrated into arbitrary mining pipelines to conduct large-scale source code processing jobs involving intra-project dependencies.
Architectural Technical Debt Identification Based on Architecture Decisions and Change Scenarios
TLDR
The results show that the proposed ATD identification approach is useful and easy to use, and it supports release planning and ATD interest measurement.
Methods for Identifying Architectural Debt: A Systematic Mapping Study
TLDR
Despite the increase of automated techniques in identifying architecture debt, pure manual methods using expert opinion is still popular and majority of the approaches use code/version history to mine archictural technical debt.
Identifying and Quantifying Architectural Debt
TLDR
This work formally defines architectural debt, describes a novel history coupling probability matrix for this purpose, and identifies architecture debts using 4 patterns of architectural flaws shown to correlate with reduced software quality.
Managing technical debt in software architecture
TLDR
This work conducted a systematic mapping study on technical debt and its management, and proposed a conceptual model of ATD, and developed an ATD management process integrating this model, in order to facilitate the architecture decision making and evaluation in a value-oriented perspective.
Anticipating Identification of Technical Debt Items in Model-Driven Software Projects
TLDR
Analysis of whether it is possible to use source code technical debt detection strategies to identify TD on code-generating models in the context of model-driven development projects to investigate the possibility and benefits of applying TD identification techniques in earlier stages of the development process.
Variations on Us Architectu
TLDR
This study applied a repres metric, called 'propagation cost', to archety transformations known to affect system mo rearchitecting a tightly coupled system to observe that in its original form the propagati not provide consistent indications of modifiability properties.
Identifying technical debt through issue trackers
................................................................................................................................. iii LAY SUMMARY
...
...