A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2018; you can also visit the original URL.
The file type is application/pdf.
Filters
Seeking Technical Debt in Critical Software Development Projects: An Exploratory Field Study
2016
2016 49th Hawaii International Conference on System Sciences (HICSS)
Preserved Fulltext
The results of an exploratory field study conducted across several projects reveal that a variety of business and environmental factors cause the occurrence of technical debt in critical domains. ...
to better identify and manage technical debt. ...
Therefore, we performed an exploratory field study to gain a better understanding of the nature of technical debt and its potential sources in critical domains. ...
doi:10.1109/hicss.2016.668
dblp:conf/hicss/Ghanbari16
fatcat:yjttuzolcvg4zkbsegen4h733u
Technical-, Social- and Process Debt in Large-Scale Agile: An Exploratory Case-Study
[chapter]
2019
Lecture Notes in Business Information Processing
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2020; you can also visit the original URL.
The file type is application/pdf.
Via both teamand large-scale retrospectives we investigated how teams coordinate and discuss Technical-, Social-and Process Debts. ...
In other words, the organization and the system accumulate debt, on which the teams pay a high interest. Such debt must therefore be prioritized and "repaid" timely. ...
This work was partially supported by the Research Council of Norway through grant 267704 and by the companies Kantega, Knowit, Storebrand and Sbanken. ...
doi:10.1007/978-3-030-30126-2_14
fatcat:n5mlsqmcjjgfffx4pl7s5ahzfm
An Exploratory Study on Self-Admitted Technical Debt
2014
2014 IEEE International Conference on Software Maintenance and Evolution
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit the original URL.
The file type is application/pdf.
Throughout a software development life cycle, developers knowingly commit code that is either incomplete, requires rework, produces errors, or is a temporary workaround. ...
Second, our work performs an exploratory study on self-admitted technical debt, hence, contributing to the body of work on technical debt. ...
CASE-STUDY RESULTS The goal of our research is to perform an exploratory study on self-admitted technical debt. ...
doi:10.1109/icsme.2014.31
dblp:conf/icsm/PotdarS14
fatcat:slbgjppzgral7pw6ljosr5ar6m
Financial Constraints, Financing Channels and Corporations' R&D Investment—Based on Development Phase and Heterogeneity of Operating Cash Flow
2016
Open Journal of Social Sciences
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2018; you can also visit the original URL.
The file type is application/pdf.
would just maintain a low level of R&D investment by cash in hold. ...
Using panel data and q model, our analysis proves that listed corporations in GEM are facing financial constraints; operating cash flow is still the main capital source of R&D investment. ...
As a result, the current asset ratio and debt financing could not be introduced into a model at the same time. ...
doi:10.4236/jss.2016.45028
fatcat:r5ow27iypjcaxlg5zhmcm5vv4y
The need for multivocal literature reviews in software engineering
2016
Proceedings of the 20th International Conference on Evaluation and Assessment in Software Engineering - EASE '16
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit the original URL.
The file type is application/pdf.
and (2) What do we, as a community, gain when we include the multivocal literature and conduct MLRs? ...
A Multivocal Literature Review (MLR) is a form of a SLR which includes grey literature in addition to the published (formal) literature. Only a few MLRs have been published in SE so far. ...
[3] is a 2015 MLR on the financial aspect of managing technical debt. [13] is a 2013 MLR on technical debt. [14] is a 2015 MLR on iOS applications testing. ...
doi:10.1145/2915970.2916008
dblp:conf/ease/GarousiFM16
fatcat:s7k3sobl2zculds5b2qurozuam
Exploration of technical debt in start-ups
2018
Proceedings of the 40th International Conference on Software Engineering Software Engineering in Practice - ICSE-SEIP '18
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2019; you can also visit the original URL.
The file type is application/pdf.
Method: We apply a case survey method to identify aspects of technical debt and contextual information characterizing the engineering context in start-ups. ...
Results: By analyzing responses from 86 start-up cases we found that start-ups accumulate most technical debt in the testing dimension, despite attempts to automate testing. ...
We use a case survey as data source and apply a combination of quantitative and qualitative methods to explore technical debt in the surveyed companies. ...
doi:10.1145/3183519.3183539
dblp:conf/icse/KlotinsUCGPTP18
fatcat:wfsh4uy7grherc2uoz3zqhgope
Wait For It: Identifying "On-Hold" Self-Admitted Technical Debt
[article]
2019
arXiv
pre-print
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2020; you can also visit the original URL.
The file type is application/pdf.
Other Versions
Self-admitted technical debt refers to situations where a software developer knows that their current implementation is not optimal and indicates this using a source code comment. ...
Based on a qualitative study of 335 comments indicating self-admitted technical debt, we first identify one particular class of debt amenable to automated management: "on-hold" self-admitted technical ...
They performed an exploratory study using text mining to extract self-admitted technical debt from source code comments. ...
arXiv:1901.09511v3
fatcat:bok7ins2ircrbojxes6jt6qnly
An Exploratory Study on the Introduction and Removal of Different Types of Technical Debt
[article]
2021
arXiv
pre-print
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2021; you can also visit the original URL.
The file type is application/pdf.
Prior research has illustrated the negative impact of technical debt, and many researchers investigated how developers deal with a certain type of technical debt. ...
As for the removal of technical debt, we find that requirement debt is removed the most, and design debt is removed the fastest. ...
To identify SATD in a project, we use source code comments that describe part of the source code containing technical debt. ...
arXiv:2101.03730v1
fatcat:hyfiagkfabfqjm54dnk3wdw7hu
On the Uncertainty of Technical Debt Measurements
2013
2013 International Conference on Information Science and Applications (ICISA)
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit the original URL.
The file type is application/pdf.
Exploratory investigations reveal that the techniques suggested allow for the comparison of uncertainties that come from differing sources. ...
We propose a departure from de-facto methods of reporting results of technical debt measurements for more rigorous techniques drawn from established methods in the physical sciences. ...
Q3: What source code testing strategies can we use to identify and detect potential sources of systematic errors? II. ...
doi:10.1109/icisa.2013.6579461
dblp:conf/icisa/IzurietaGRL13
fatcat:haxsohj7ofhh3giskh3yipexji
A case study on effectively identifying technical debt
2013
Proceedings of the 17th International Conference on Evaluation and Assessment in Software Engineering - EASE '13
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2018; you can also visit the original URL.
The file type is application/pdf.
Context: The technical debt (TD) concept describes a tradeoff between short-term and long-term goals in software development. ...
While it is highly useful as a metaphor, it has utility beyond the facilitation of discussion, to inspire a useful set of methods and tools that support the identification, measurement, monitoring, management ...
ACKNOWLEDGMENTS The participation of Seaman and Zazworka in this work is supported by the US National Science Foundation, award #0916699. ...
doi:10.1145/2460999.2461005
dblp:conf/ease/ZazworkaSVSS13
fatcat:xcwjqtojf5aktptfmwjnaghxma
Comparing Maintainability Index, SIG Method, and SQALE for Technical Debt Identification
2020
Scientific Programming
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2020; you can also visit the original URL.
The file type is application/pdf.
There are many definitions of software Technical Debt (TD) that were proposed over time. ...
Considering 20 open source Python libraries, we compare the TD measurements time series in terms of trends and evolution according to different sets of releases (major, minor, and micro), to see if the ...
of potential technical debt (PTD), and cost of total technical debt (CTD). ...
doi:10.1155/2020/2976564
fatcat:pe2qzevk3fhybbpvxzhovxj5i4
The hidden cost of backward compatibility
2020
Proceedings of the 3rd International Conference on Technical Debt
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2021; you can also visit the original URL.
The file type is application/pdf.
Conclusion This paper illustrates that integration tests can be viewed as a debt from the perspective of deprecated services. ...
Method We take an exploratory approach, reporting on experiences found before and after servicing parts of the incurred Technical Debt. ...
This is what we call excessive usage of a service version, as opposed to the expected usage of a service version which is its source code, its unit tests and integration tests of the service version itself ...
doi:10.1145/3387906.3388629
dblp:conf/icse/SundelinGW20
fatcat:sd7flaeznfgdvf47x3ehzqwuye
Influence of Developer Factors on Code Quality: A Data Study
2019
2019 IEEE 19th International Conference on Software Quality, Reliability and Security Companion (QRS-C)
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2020; you can also visit the original URL.
The file type is application/pdf.
In this exploratory study, we test this hypothesis on two large open source repositories, using TD as a code quality metric and the data that may be inferred from the version control systems. ...
Since these tools only examine the software project's codebase, they overlook other possible factors that may impact code quality and the assessment of the technical debt (TD). ...
A. Technical Debt Cunningham [10] created the Technical Debt (TD) term as an analogy between financial concepts and software cost. ...
doi:10.1109/qrs-c.2019.00035
dblp:conf/qrs/SalameaF19
fatcat:dkoujromzred3nx7xrettkm52y
Technical Debt in Large-Scale Distributed Projects: An Industrial Case Study
2021
2021 IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER)
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2021; you can also visit the original URL.
The file type is application/pdf.
Technical debt (TD) is a metaphor that refects the technical compromises that sacrifce the long-term health of a software product to achieve short term beneft. ...
We found out that Task Complexity has a strong relationship (p-value = 5.69 × 10 −5 ) with Technical Debt, while Global Distance was mentioned by the interviewees as a relevant factor for TD accumulation ...
As a result, the plots confrmed that there is some level of linearity between TD and LT, TC, DV and TS. Third, we tested for auto-correlation using the Durbin-Watson test. ...
doi:10.1109/saner50967.2021.00071
fatcat:q4pg6zzw2jhgndytx6hk734moi
Book Review: Guidance at WorkGUIDANCE AT WORK. By SmartMilo H. and MorganDeWitt S., both of Arsenal Technical School, Indianapolis. Cloth. 100 pages. (5 by 8 inches.) New York: McGraw-Hill Book Company, Inc
1931
Journal of Education
Preserved Fulltext
The Internet Archive has digitized a microfilm copy of this work. It may be possible to borrow a copy for reading.
greatest sources of difficulty by the English Tests. ...
Superintendent Rohan has demon- strated vocational vision in everything he has exploited in Appleton, and this book, “Exploratory Science,” is “safety first” as a means of “Life Guidance” of youth,
Books ...
doi:10.1177/002205743111301119
fatcat:yhngw65mencqzghm7fpxbxczei
« Previous
Showing results 1 — 15 out of 9,087 results