Research

TD SWOT (Strengths, Weaknesses, Opportunities, and Threats) analysis for TD management encompasses a set of infographics to support identifying strategic capabilities or issues that the project team can improve, maintain, or reduce to manage debt items. Strengths are internal practices used to prevent, monitor, and repay debt items, while opportunities are external practices for improving TD management. On the other side, weaknesses are the team's decision factors for not preventing, monitoring, or repaying TD items, and threats are external factors outside the team's control.

This research supports practitioners in:

• Identifying common practices used for preventing, monitoring, and repaying debt items;

• Starting or improving TD management initiatives, including the improvement of the team’s ability to manage debt;

• Understanding impediments to TD management practices that can be addressed in TD management initiatives.

Stack Exchange (SE) is a network of question-and-answer (Q&A) websites on topics in diverse fields, each site covering a specific topic, where questions, answers, and users are subject to a reputation award process. This reputation system allows the website's self-moderating and helps them to bring confidence to the content available. The SE network has currently more than 60 million of posts and is one of the main sources of professionals from various areas to daily search for solutions to day-to-day challenges. This is especially true for software engineering practitioners, who ask from simple questions, such as a solution of a small bug, to more complex ones, such as advice and knowledge about some topic, approach, or task.

In this context, the SE network can be a rich source of the perception, practices, and approaches used by practitioners regarding TD identification and management. However, the TD literature lacks an approach to mining these relevant data from Q&A. Therefore the main goal of this study is to propose and evaluate an approach based on text mining to gather empirical evidence from the SE network regarding TD. This research can help researchers to understand practitioners' point of view regarding TD and its findings can lead to the development of new tools and approaches related to TD, besides that, the theoretical framework proposed can be adapted to other areas.

Stack Exchange (SE) is a network of question-and-answer (Q&A) websites on topics in diverse fields, each site covering a specific topic, where questions, answers, and users are subject to a reputation award process. This reputation system allows the website's self-moderating and helps them to bring confidence to the content available. The SE network has currently more than 60 million of posts and is one of the main sources of professionals from various areas to daily search for solutions to day-to-day challenges. This is especially true for software engineering practitioners, who ask from simple questions, such as a solution of a small bug, to more complex ones, such as advice and knowledge about some topic, approach, or task.

In this context, the SE network can be a rich source of the perception, practices, and approaches used by practitioners regarding TD identification and management. However, the TD literature lacks an approach to mining these relevant data from Q&A. Therefore the main goal of this study is to propose and evaluate an approach based on text mining to gather empirical evidence from the SE network regarding TD. This research can help researchers to understand practitioners' point of view regarding TD and its findings can lead to the development of new tools and approaches related to TD, besides that, the theoretical framework proposed can be adapted to other areas.

Several works have investigated how TD affects coding activities, but TD can affect other software process activities. More specifically, requirements technical debt (RTD) items are related to trade-offs made concerning what requirements the development team needs to implement or how to implement them. Knowing the causes and effects of RTD can support software teams in defining actions to prevent the occurrence of these items and aid in the prioritization for eliminating them, respectively. Besides, having information on how software practitioners deal with RTD items can support developing new strategies and artifacts for managing RTD items.

This work aims to investigate the state of the practice of RTD, revealing its causes, effects, and practices used for its preventing, monitoring, and repaying. We intend to run a multi-method research strategy composed of a survey and case studies based on interviews. The results from these studies will be triangulated to provide a more comprehensive view of RTD in practice. We also seek to organize these results in an artifact to make their use more feasible for practitioners.