Towards an Ontology of Terms on Technical Debt

Alves, Nicolli S.R.; Ribeiro, Leilane Ferreira; Caires, Vivyane; Mendes, Thiago Souto; Spínola, Rodrigo O.

doi:10.1109/mtd.2014.9

Cited by 123 publications

(114 citation statements)

References 17 publications

Supporting

Mentioning

107

Contrasting

Unclassified

Order By: Relevance

“…A poor identification and management of TD can bring significant losses to a software project [9]. Different types of TD can occur throughout the phases of a software development process [2]. One of them is documentation debt, which refers to issues encountered in the software project documentation that can be identified by locating missing, inadequate or incomplete artefacts.…”

Section: Introductionmentioning

confidence: 99%

Investigating the Link between User Stories and Documentation Debt on Software Projects

Soares

Alves

Mendes

et al. 2015

2015 12th International Conference on Information Technology - New Generations

Self Cite

View full text Add to dashboard Cite

Technical debt is a metaphor that describes the effect of immature artefacts in software development. One of its types is documentation debt, which can be identified by locating missing, inadequate or incomplete artefacts in software projects. Nowadays, we can observe more organizations using agile methods to support their activities. In particular, the use of user stories reduces the focus on requirement specification tasks and, as a consequence, creates difficulties that need to be overcame by the development team. In order to investigate these difficulties and assess whether they create a favourable scenario for incurring documentation debt, this paper presents the results of a literature review and an exploratory study. The results from both studies allowed us to identify a list of causes that can lead the development team to incur documentation debt when working with agile requirements. This is an important step in order to manage the technical debt from a preventive perspective.

show abstract

Section: Introductionmentioning

confidence: 99%

Investigating the Link between User Stories and Documentation Debt on Software Projects

Soares

Alves

Mendes

et al. 2015

2015 12th International Conference on Information Technology - New Generations

Self Cite

View full text Add to dashboard Cite

show abstract

“…For training purposes, we performed a presentation in the first part of the class. The presentation covered the TD concepts and context, as well as the TD indicators (Alves et al, 2014) and how to perform a qualitative analysis on the code comments. This training took one hour.…”

Section: Operationmentioning

confidence: 99%

“…We assumed as a criterion the strategy that supports decisions about when and if a TD item should be paid; • Types of TD Related to the Decision-making Criteria (RQ2): this category lists the types of TD that were related to any criterion in the studies. We used the types of debt proposed by Alves et al (2014); • Empirical Evaluation (RQ3): we verified whether the proposed criterion has been evaluated through empirical methods and, if so, which method was used. We considered that a study has an empirical evaluation if it brings at least one section with some discussion dedicated to this topic.…”

Section: Classification Schemementioning

confidence: 99%

“…These comments were analyzed in order to identify text patterns that indicate a TD. In the same way, (Maldonado and Shihab, 2015) have read 33K code comments to identify different types of debt using the indicators proposed by (Alves et al, 2014). According to the authors, these patterns can be used to manually identify TD that exists in the project by reading code comments.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

An Evaluation of the Challenges of Multilingualism in Data Warehouse Development

Dediź

Stanier

2016

Proceedings of the 18th International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

ICEIS 2016 received 257 paper submissions from 42 countries in all continents, which makes it one of the largest conferences in the World in the area of Information Systems, thus demonstrating the success and global dimension of this conference. From these, 42 papers were selected for publication and presentation at the Conference as full papers. These numbers, leading to a full-paper acceptance ratio of 16%, show the intention of preserving a high quality forum for this conference, a quality that we intend to maintain in the future, for the next editions of this conference.The high number and high quality of the received papers imposed difficult choices in the selection process. To evaluate each submission, a double blind paper review was performed by the Program Committee, whose members are highly qualified researchers in ICEIS topic areas.All presented papers will be available at the SCITEPRESS Digital Library and will be submitted for indexation by Thomson Reuters Conference Proceedings Citation Index (ISI), INSPEC, DBLP, EI (Elsevier Index) and Scopus.Additionally, a short list of presented papers will be selected to be expanded into a forthcoming book of ICEIS 2016 Selected Papers to be published by Springer in the LNBIP Series.The technical program of the conference included a panel and 4 invited talks delivered by internationally distinguished speakers, namely: Claudia Loebbecke (University of Cologne, Germany), Sergio Gusmeroli (TXT e-solutions SPA, Italy), Wil Van Der Aalst (Technische Universiteit Eindhoven, Netherlands) and Jan Vom Brocke (University of Liechtenstein, Liechtenstein). Their participation positively contributes to reinforce the overall quality of the Conference and to provide a deeper understanding of the fields addressed by the conference.Moreover, ICEIS 2016 had a Doctoral Consortium on Enterprise Information Systems and 1 tutorial. We are thankful to the Conference Co-chairs (Olivier Camp and José Cordeiro) and Program Co-chairs (Slimane Hammoudi, Leszek Maciaszek and Michele M. Missikoff) for their dedication and hard work in organizing these events.We sincerely thank all the authors for their submissions and participation in ICEIS 2016. Furthermore, we would like to thank all the members of the program committee and reviewers, who helped us with their expertise, dedication and time. We would also like to thank the invited speakers for their excellent contribution in sharing their knowledge and vision and the workshop/special session chairs whose collaboration with ICEIS 2015 was much appreciated. Finally, we gratefully acknowledge the professional support of the ICEIS 2016 team for all organizational processes. XIIIWe hope that all colleagues find this a fruitful and inspiring conference. We hope to contribute to the development of the Enterprise Information Systems community and look forward to having additional research results presented at the next edition of ICEIS, details of which are available at http://www.iceis.org. Slimane Hammoudi University of Cologne, GermanyAbstract:...

show abstract

“…According to the very broad specifications given on the categories of technical debt in Li et al [7] or Alves et al [1], in the integration and integration testing process alone, all possible technical debts could be identified. As, this does not provide a statement on how much e↵ort it would take to repay the respective debt, neither about if it has an e↵ect on the business value of the company, this is not considered as a severe problem.…”

Section: Technical Debtmentioning

confidence: 99%

Challenges from Integration Testing using Interconnected Hardware-in-the-Loop Test Rigs at an Automotive OEM

Schroeder

Berger

Herpel³

2015

Proceedings of the First International Workshop on Automotive Software Architecture

View full text Add to dashboard Cite

Developing automotive functions involves complex software to a growing extent while still following a consecutive waterfalllike development process: Integrating and testing software with other software and with hardware components is conducted towards the final phases during the development. For example, ambiguous requirements or unclear semantics in system interfaces show up very late and mostly not before integration testing. In this article, we are reporting about results from conducting interviews with integration and test engineers at a large automotive OEM about today's most resource-intense challenges when dealing with software integration testing tasks at interconnected hardware-in-the-loop test rig environments. Challenges in processes, communication, and implementation were mentioned most often as emerging topics to be tackled over and over again during this phase in a vehicle series development project.

show abstract

Towards an Ontology of Terms on Technical Debt

Cited by 123 publications

References 17 publications

Investigating the Link between User Stories and Documentation Debt on Software Projects

Investigating the Link between User Stories and Documentation Debt on Software Projects

An Evaluation of the Challenges of Multilingualism in Data Warehouse Development

Challenges from Integration Testing using Interconnected Hardware-in-the-Loop Test Rigs at an Automotive OEM

Contact Info

Product

Resources

About