Gothenburg, 27 May 2018 Identifying Architectural Technical Debt in Android Applications through Automated Compliance Checking Roberto Verdecchia roberto.verdecchia@gssi.it
Architectural Technical Debt (ATD) Sub-optimal decisions resulting in immature architectural ● artifacts 1 Hinders maintainability and evolvability ● ATD identification: detecting ATD during or after ● architecting processes 2 To date, few approaches consider Android specific ATD ● 1 “A Systematic Literature Review and a Unified Model of ATD.” IEEE, 2016, pp. 189-197. T. Besker, A. Martini, and J. Bosch 2 “Architectural Debt Management in Value-Oriented Architecting”. 2014. In Economics-Driven Software Architecture, pp. 183-204. Z. Li, P. Liang, and P. Avgeriou.
Research question “How can we identify automatically Architectural Technical Debt specific to Android applications?”
Approach overview
Approach overview Extraction of Android ● architectural guidelines
Approach overview Extraction of Android ● architectural guidelines Establishment of Android ● reference architecture
Approach overview Extraction of Android ● architectural guidelines Establishment of Android ● reference architecture Reverse engineering of ● implemented architecture
Approach overview Extraction of Android ● architectural guidelines Establishment of Android ● reference architecture Reverse engineering of ● implemented architecture Compliance checking ●
Approach overview Extraction of Android ● architectural guidelines Establishment of Android ● reference architecture Reverse engineering of ● implemented architecture Compliance checking ● Quantitative assessment of ● compliance violations
See you at the poster!
Gothenburg, 27 May 2018 Identifying Architectural Technical Debt in Android Applications through Automated Compliance Checking Roberto Verdecchia roberto.verdecchia@gssi.it
Recommend
More recommend
