Búsqueda avanzada

Identification and analysis of the elements required to manage technical debt by means of a systematic mapping study (Artículo relevante)

Artículo publicado en Journal of Systems and Software (JSS). JSS es clasificada como Q1 en JCR 2017. @article{FERNANDEZSANCHEZ201722,title = «Identification and analysis of the elements required to manage technical debt by means of a systematic mapping study»,journal = «Journal of Systems and Software»,volume = «124»,pages = «22 – 38»,year = «2017»,issn = «0164-1212»,doi = «»,url = «»,author = «Carlos Fernández-Sánchez and Juan Garbajosa and Agustín YagÃŒe and Jennifer Perez»,keywords = «Technical debt, Technical debt management, Systematic mapping, Decision making, Basic decision-making factors, Cost estimation techniques, Practices and techniques for decision-making, Stakeholdersâ?? points of view, Engineering, Engineering management, Business-organizational management, Framework»,abstract = «Technical debt, a metaphor for the long-term consequences of weak software development, must be managed to keep it under control. The main goal of this article is to identify and analyze the elements required to manage technical debt. The research method used to identify the elements is a systematic mapping, including a synthesis step to synthesize the elements definitions. Our perspective differs from previous literature reviews because it focused on the elements required to manage technical debt and not on the phenomenon of technical debt or the activities used in performing technical debt management. Additionally, the rigor and relevance for industry of the current techniques used to manage technical debt are studied. The elements were classified into three groups (basic decision-making factors, cost estimation techniques, practices and techniques for decision-making) and mapped according three stakeholdersâ?? points of view (engineering, engineering management, and business-organizational management). The definitions, classification, and analysis of the elements provide a framework that can be deployed to help in the development of models that are adapted to the specific stakeholdersâ?? interests to assist the decision-making required in technical debt management and to assess existing models and methods. The analysis indicated that technical debt management is context dependent.»}

Ecological Debt: outlining a measure to evaluate software greenability

Developing low quality software (with design flaws, poor quality code, etc) lead to a product with an inner cost that could be measured by using technical debt, that could be consider as the economical effort to solve all the existing design problems of a given software. As time goes on, software quality is acquiring new dimensions, and one of the most important one in the recent years (required by our society) is Software Sustainability, that could be understood as the degree of environmental-friendliness of a soft-ware system. So, following the idea of technical debt, we propose the concept of Ecological Debt which purpose is to measure the economical effort to develop a sustainable software following the Green-in principles.