University of Groningen
Managing technical debt through software metrics, refactoring and traceability
Charalampidou, Sofia
IMPORTANT NOTE: You are advised to consult the publisher's version (publisher's PDF) if you wish to cite from it. Please check the document version below.
Document Version
Publisher's PDF, also known as Version of record
Publication date: 2019
Link to publication in University of Groningen/UMCG research database
Citation for published version (APA):
Charalampidou, S. (2019). Managing technical debt through software metrics, refactoring and traceability. University of Groningen.
Copyright
Other than for strictly personal use, it is not permitted to download or to forward/distribute the text or part of it without the consent of the author(s) and/or copyright holder(s), unless the work is under an open content license (like Creative Commons).
Take-down policy
If you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim.
Downloaded from the University of Groningen/UMCG research database (Pure): http://www.rug.nl/research/portal. For technical reasons the number of authors shown on this cover page is limited to 10 maximum.
Stellingen
behorende bij het proefschrift
Managing Technical Debt through
Software Metrics, Refactoring and Traceability
van
Sofia Charalampidou
1. Size is not the only parameter for characterizing a method as long, but conceptual coherence as well.
2. Technical Debt prioritization should be performed based on various parameters: the type of the smell, the intensity of the problem, and the "place" in the code, where the smell resides.
3. The SEMI approach can assist software engineers in the prioritization of the suggested refactoring opportunities by ranking them based on an estimate of their fitness for extraction.
4. Design patterns are not always beneficial for software quality. The decision making process on when a pattern should be refactored can be guided by objective criteria.
5. The state-of-the-art on software traceability suggests that the dominant artifact in traces are requirements and the most frequently studied research topic is the proposal of novel techniques for establishing traces. 6. The introduction of traces is a promising technique to facilitate future
maintenance activities and therefore assist Technical Debt Management. 7. The integration of a traceability approach within the IDE is a promising
way for preventing insufficient, incomplete and outdated documentation, and therefore preventing the accumulation of Technical Debt.
8. Technical Debt Management spans across development phases and artifacts. However, since its treatment cannot be uniform, there is a need for specialized approaches for the different artifacts in each phase. 9. “And now here is my secret, a very simple secret: It is only with the
heart that one can see rightly; what is essential is invisible to the eye.”
― Antoine de Saint-Exupéry, The little prince
10. “You have your brush, you have your colors, you paint paradise, then in you go.”
