A Case Study in Locating the Architectural Roots of Technical Debt

Kazman, Rick; Cai, Yuanfang; Mo, Ran; Feng, Qiong; Xiao, Lu; Haziyev, Serge; Fedak, Volodymyr; Shapochka, Andriy

doi:10.1109/icse.2015.146

Cited by 84 publications

(45 citation statements)

References 32 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Their results support our view that if DRSpaces can be constructed from architectural plans they are likely to be risk isolating. Kazman et al [2] used DRSpaces as a basis for estimating a return on investment due to preventive maintenance.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

An Evaluation of Design Rule Spaces as Risk Containers

Leigh

Wermelinger

Zisman

2016

2016 13th Working IEEE/IFIP Conference on Software Architecture (WICSA)

View full text Add to dashboard Cite

Abstract-It is well understood that software development can be a risky enterprise and industrial projects often overrun budget and schedule. Effective risk management is, therefore, vital for a successful project outcome. Design Rule Spaces (DRSpaces) have been used by other researchers to understand why implemented software is error-prone [1, 2]. This industrial case study evaluates whether such spaces are durable, meaningful, and isolating risk containers. DRSpaces were created from UML class diagrams of architectural design artefacts. In our study, object orientated metrics were calculated from the UML diagrams, and compared to the error-proneness of the DRSpace implementation, to determine whether architectural coupling translated into implementation difficulties. A correlation between architectural coupling and error-proneness of DRSpaces was observed in the case study. Software developers were asked to identify DRSpaces they found difficult to implement, in order to understand which factors, other than architectural coupling, were also important. The qualitative results show agreement between the code areas developers found difficult to implement and the error-prone DRSpaces. However, the results also show that architectural coupling is just one risk factor of many. The case study suggests that architectural DRSpaces can be used to facilitate a targeted risk review prior to implementation and manage risk.

show abstract

Section: Related Workmentioning

confidence: 99%

“…Although many of the related DRSpace approaches [1,2,8] have similar motivation to our work, the majority of the approaches are based on code analysis to identify architectural problems. However, code analysis does not support the identification of architectural risks before implementation.…”

Section: Related Workmentioning

confidence: 99%

An Evaluation of Design Rule Spaces as Risk Containers

Leigh

Wermelinger

Zisman

2016

2016 13th Working IEEE/IFIP Conference on Software Architecture (WICSA)

View full text Add to dashboard Cite

show abstract

“…Therefore, one future work will include the integration with SonarQube to use it as another source of metrics for TEDMA. Other tool, Titan [18], which provides mechanisms to estimate TD and that also provides a framework to make decisions based on these estimations, could be also integrated into TEDMA. Titan [18] is mainly focused on the analysis of modularity violations, similar to Clio [19], and a model for TDM.…”

Section: Related Workmentioning

confidence: 99%

“…Other tool, Titan [18], which provides mechanisms to estimate TD and that also provides a framework to make decisions based on these estimations, could be also integrated into TEDMA. Titan [18] is mainly focused on the analysis of modularity violations, similar to Clio [19], and a model for TDM. As the goal of TEDMA is to integrate both metrics and management models, the integration of a tool as Titan could be a good example of the capabilities of TEDMA.…”

Section: Related Workmentioning

confidence: 99%

An Open Tool for Assisting in Technical Debt Management

Fernández-Sánchez

Humanes

Garbajosa

et al. 2017

2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)

View full text Add to dashboard Cite

Abstract-Technical debt monitoring is one of the activities that have to be performed in technical debt management. To do that, there are different techniques that can be used to estimate technical debt and different tools that implement those different techniques. This paper presents TEDMA Tool, a tool for monitoring technical debt over the software evolution and that it is open to integrate third party tools. TEDMA is based on the analysis of source code repositories and is useful for researching using empirical data extracted from software projects. Currently, it is been used to analyze big projects in the execution of several case studies. The expected evolution of TEDMA will make the tool useful for software development industry.

show abstract

“…3) Using the knowledge from 1) and 2), the RAR subsystem will propose refactoring solutions to the architectures, based on removing the design flaws [15] [17]. AAFS and Titan techniques serve to identify the risks in the system.…”

Section: Developing Countermeasuresmentioning

confidence: 99%

Can Cybersecurity Be Proactive? A Big Data Approach and Challenges

Chen

Kazman

Monarch

et al. 2017

Proceedings of the 50th Hawaii International Conference on System Sciences (2017)

Self Cite

View full text Add to dashboard Cite

The cybersecurity community typically reacts to attacks after they occur. Being reactive is costly and can be fatal where attacks threaten lives, important data, or mission success. But can cybersecurity be done proactively? Our research capitalizes on the Germination Period-the time lag between hacker communities discussing software flaw types and flaws actually being exploited-where proactive measures can be taken. We argue for a novel proactive approach, utilizing big data, for (I) identifying potential attacks before they come to fruition; and based on this identification, (II) developing preventive countermeasures. The big data approach resulted in our vision of the Proactive Cybersecurity System (PCS), a layered, modular service platform that applies big data collection and processing tools to a wide variety of unstructured data sources to predict vulnerabilities and develop countermeasures. Our exploratory study is the first to show the promise of this novel proactive approach and illuminates challenges that need to be addressed.

show abstract

A Case Study in Locating the Architectural Roots of Technical Debt

Cited by 84 publications

References 32 publications

An Evaluation of Design Rule Spaces as Risk Containers

An Evaluation of Design Rule Spaces as Risk Containers

An Open Tool for Assisting in Technical Debt Management

Can Cybersecurity Be Proactive? A Big Data Approach and Challenges

Contact Info

Product

Resources

About