Results 31 to 40 of about 2,119 (166)
, 2023 This dataset includes pre-trained word embeddings and a weighted file that can be used to identify self-admitted technical debt (SATD) from issue tracking ...
Software Engineering +3 more
core +2 more sources
Identifying Self-Admitted Technical Debts With Jitterbug: A Two-Step Approach [PDF]
IEEE Transactions on Software Engineering, 2022 Keeping track of and managing Self-Admitted Technical Debts (SATDs) are important to maintaining a healthy software project. This requires much time and effort from human experts to identify the SATDs manually. The current automated solutions do not have satisfactory precision and recall in identifying SATDs to fully automate the process.
Zhe Yu 0002 +3 more
openaire +2 more sources
, 2021 This repository contains the dataset of the manuscript "Self-Admitted Technical Debt Practices: A Comparison Between Industry and Open-Source" accepted in the Empirical Software Engineering Journal, edited by ...
Fucci, Gianmarco +5 more
core +3 more sources
Zeszyty Prawnicze, 2017 THE ROMAN ORIGINS OF THE NOTICE TO DEBTOR OF ASSIGNMENT DENUNTIATIO IN C. 8,41,3 PR. AND SELECTED CONTEMPORARY LEGAL SYSTEMS Summary The transferability of relative rights is now commonly admitted as one of the most basic and indispensable foundations
Piotr Ściślicki
doaj +1 more source
Detecting and quantifying different types of self-admitted technical Debt [PDF]
2015 IEEE 7th International Workshop on Managing Technical Debt (MTD), 2015 Technical Debt is a term that has been used to express non-optimal solutions during the development of software projects. These non optimal solutions are often shortcuts that allow the project to move faster in the short term, at the cost of increased maintenance in the future. To help alleviate the impact of technical debt, a number of studies focused
Everton da S. Maldonado, Emad Shihab
openaire +1 more source
Was self-admitted technical debt removal a real removal? [PDF]
Proceedings of the 15th International Conference on Mining Software Repositories, 2018 Technical Debt (TD) has been defined as "code being not quite right yet", and its presence is often self-admitted by developers through comments. The purpose of such comments is to keep track of TD and appropriately address it when possible. Building on a previous quantitative investigation by Maldonado et al.
Fiorella Zampetti +2 more
openaire +2 more sources
, 2023 <p>This is a research artifact of the paper titled Quantifying and Characterizing Clones of Self-Admitted Technical Debt in Build Systems</p ...
Xiao, Tao
core +1 more source
Dataset: An empirical study on self-admitted technical debt in modern code review
, 2023 This data was used in the IST paper "An Empirical Study on Self-Admitted Technical Debt in Modern Code Review". The program to use this data is published in GitHub (https://github.com/Yutaro-Kashiwa/ReviewSATD_RP) When you use this data in your research,
Yutaro Kashiwa
core +1 more source
Automated Detection of Self-Admitted Technical Debt: A Systematic Literature Review
IEEE AccessIn modern software development, developers frequently introduce comments that describe temporary solutions, incomplete implementations, or deferred improvements.
Anas Abdulaziz +2 more
doaj +1 more source
Subordination of related party claims in insolvency: A suggestive framework for Asian regimes
International Insolvency Review, EarlyView.Abstract Related party loans, due to their inherent nature, warrant a higher threshold for scrutiny when compared to loans extended by unrelated parties. Why were these monies advanced as loans, carrying higher priority in insolvency, rather than being invested as share capital?
Aditya Jain, Dhanya Jha, Rebecca Parry
wiley +1 more source