References
[1] Jan Bosch, Speed, Data, and Ecosystems: Excelling in a Software-Driven World. CRC Press, Taylor and Francis Group, 2016.
[2] W. Cunningham, “The WyCash portfolio management system,” Proc. Object-Oriented Program. Syst. Lang. Appl. (OOPSLA ’92), vol. 4, no. 2, pp. 29–30, Apr. 1993.
[3] Andy Kyte, “Measure and Manage Your IT Debt,” Gartner, 2010. [Online]. Available: https://www.gartner.com/doc/1419325/measure-manage-it-debt. [Accessed: 10-Apr-2017].
[4] Bill Curtis, “Architecturally Complex Defects | CISQ – Consortium for IT Software Quality,” 2012. [Online]. Available: http://it-cisq.org/architecturally-complex-defects/. [Accessed: 10-Apr-2017].
[5] M. Khurum, T. Gorschek, and M. Wilson, “The software value map – an exhaustive collection of value aspects for the development of software intensive products,” J. Softw. Evol. Process, vol. 25, no. 7, pp. 711–741, Jul. 2013.
[6] Z. Li, P. Avgeriou, and P. Liang, “A systematic mapping study on technical debt and its management,” J. Syst. Softw., vol. 101, pp. 193–220, 2015.
[7] T. Besker, A. Martini, and J. Bosch, “A Systematic Literature Review and a Unified Model of ATD,” in 2016 42th Euromicro Conference on Software Engineering and Advanced Applications (SEAA), 2016, pp. 189–197.
[8] E. Tom, A. Aurum, and R. Vidgen, “An exploration of technical debt,” J. Syst. Softw., vol. 86, no. 6, pp. 1498–1516, 2013.
[9] A. Ampatzoglou, A. Ampatzoglou, A. Chatzigeorgiou, and P. Avgeriou, “The financial aspect of managing technical debt: A systematic literature review,” in Information and Software Technology, 2015, vol. 64.
[10] N. Moha and Y. Guéhéneuc, “DECOR: A method for the specification and detection of code and design smells,” IEEE Trans. Softw. Eng., vol. 36, no. 1, pp. 20–36, 2010.
[11] N. Tsantalis, T. Chaikalis, and A. Chatzigeorgiou, “JDeodorant: Identification and removal of type-checking bad smells,” in Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR, 2008, pp. 329–331.
[12] SonarSource, “SonarQube: Continuous Code Quality.” [Online]. Available: https://www.sonarqube.org/.
[13] J. Holvitie and V. Leppanen, “DebtFlag: Technical debt management with a development environment integrated tool,” 2013 4th Int. Work. Manag. Tech. Debt, MTD 2013 – Proc., pp. 20–27, 2013.
[14] A. Martini, J. Bosch, and M. Chaudron, “Investigating Architectural Technical Debt accumulation and refactoring over time: A multiple-case study,” Inf. Softw. Technol., vol. 67, pp. 237–253, 2015.
[15] R. Kazman, Y. Cai, R. Mo, Q. Feng, L. Xiao, S. Haziyev, V. Fedak, and A. Shapochka, “A Case Study in Locating the Architectural Roots of Technical Debt,” in Proceedings – International Conference on Software Engineering, 2015, pp. 179–188.
[16] K. Power, “Understanding the impact of technical debt on the capacity and velocity of teams and organizations: Viewing team and organization capacity as a portfolio of real options,” in 2013 4th International Workshop on Managing Technical Debt (MTD), 2013, pp. 28–31.
[17] C. Fernández-Sánchez, J. Garbajosa, A. Yagüe, and J. Perez, “Identification and analysis of the elements required to manage technical debt by means of a systematic mapping study,” J. Syst. Softw., vol. 124, pp. 22–38, 2017.
[18] P. Avgeriou, P. Kruchten, R. L. Nord, I. Ozkaya, and C. Seaman, “Reducing friction in software development,” IEEE Softw., vol. 33, no. 1, pp. 66–72, 2016.
[19] E. Alégroth and J. Gonzalez-Huerta, “Towards a Mapping of Software Technical Debt onto Testware,” in SEAA 2017 Euromicro Conference on Software Engineering and Advanced Applications, 2017.
[20] Petter Måhlén, “Qualities of Quality | Labs,” Spotify Labs, 2014. [Online]. Available: https://labs.spotify.com/2014/04/11/qualities-of-quality/.
[21] P. Avgeriou, P. Kruchten, I. Ozkaya, C. Seaman, and C. Seaman, “Managing Technical Debt in Software Engineering,” in Dagstuhl Reports, 2016, vol. 6, no. 4, pp. 110–138.
[22] M. Fowler, K. Beck, J. Brant, W. Opdyke, and D. Roberts, Refactoring: Improving the Design of Existing Code. Addison Wesley, 1999.
[23] E. Murphy-Hill, C. Parnin, and A. P. Black, “How We Refactor, and How We Know It,” IEEE Trans. Softw. Eng., vol. 38, no. 1, pp. 5–18, Jan. 2012.
[24] G. Bavota, B. De Carluccio, A. De Lucia, M. Di Penta, R. Oliveto, and O. Strollo, “When Does a Refactoring Induce Bugs? An Empirical Study,” in 2012 IEEE 12th International Working Conference on Source Code Analysis and Manipulation, 2012, pp. 104–113.
[25] G. Bavota, A. De Lucia, M. Di Penta, R. Oliveto, and F. Palomba, “An experimental investigation on the innate relationship between quality and refactoring,” J. Syst. Softw., vol. 107, pp. 1–14, 2015.
[26] J. Holvitie, S. A. Licorish, and V. Leppanen, “Modelling Propagation of Technical Debt,” in 2016 42th Euromicro Conference on Software Engineering and Advanced Applications (SEAA), 2016, pp. 54–58.
[27] B. Curtis, J. Sappidi, and A. Szynkarski, “Estimating the size, cost, and types of technical debt,” 2012 3rd Int. Work. Manag. Tech. Debt, MTD 2012 – Proc., pp. 49–53, 2012.
[28] V. Garousi, K. Petersen, and B. Ozkan, “Challenges and best practices in industry-academia collaborations in software engineering: A systematic literature review,” Inf. Softw. Technol., vol. 79, pp. 106–127, 2016.
[29] H. Kniberg, “Spotify engineering culture (part 1 & 2),” Spotify Labs, 2014. [Online]. Available: https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/.
[30] B. Kitchenham, “Guidelines for performing Systematic Literature Reviews in Software Engineering,” EBSE Technical Report, Keele University, UK, 2007.
[31] K. Petersen, S. Vakkalanka, and L. Kuzniarz, “Guidelines for conducting systematic mapping studies in software engineering : An update,” Inf. Softw. Technol., vol. 64, pp. 1–18, 2015.
[32] P. Runeson, M. Host, A. Rainer, and B. Regnell, Case Study Research in Software Engineering: Guidelines and Examples. John Wiley & Sons, 2012.
[33] G. Hecht, R. Rouvoy, N. Moha, and J. González-Huerta, “An Empirical Analysis of Android Code Smells,” IEEE Trans. Softw. Eng., p. To be resubmitted, 2017.
[34] V. Braun and V. Clarke, “Using thematic analysis in psychology,” Qual. Res. Psychol., vol. 3, no. 2, pp. 77–101, Jan. 2006.
[35] B. G. Glaser and A. L. Strauss, The discovery of grounded theory : strategies for qualitative research. Aldine Pub. Co, 1967.
[36] K.-J. Stol, P. Ralph, and B. Fitzgerald, “Grounded Theory in Software Engineering Research: A Critical Review and Guidelines,” 2016.
[37] T. Gorschek, C. Wohlin, P. Garre, and S. Larsson, “A Model for Technology Transfer in Practice,” IEEE Softw., vol. 23, no. 6, pp. 88–95, 2006.
[38] K. Petersen, C. Gencel, N. Asghari, D. Baca, and S. Betz, “Action research as a model for industry-academia collaboration in the software engineering context,” in Proceedings of the 2014 international workshop on Long-term industrial collaboration on software engineering – WISE ’14, 2014, pp. 55–62.
[39] S.-W. Chuang, T. Luor, and H.-P. Lu, “Assessment of institutions, scholars, and contributions on agile software development (2001–2012),” J. Syst. Softw., vol. 93, pp. 84–101, Jul. 2014.
[40] F. Palma, J. Gonzalez-Huerta, N. Moha, Y. G. Guéhéneuc, and G. Tremblay, “Are RESTful APIs well-designed? Detection of their linguistic (Anti)patterns,” in 13th International Conference on Service Oriented Computing (ICSOC2015), 2015, vol. 9435, pp. 171–187.
[41] F. Palma, J. Gonzalez-Huerta, M. Founi, N. Moha, G. Tremblay, and Y.-G. Guéhéneuc, “Semantic Analysis of RESTFul APIs for the Detection of Linguistic Patterns and Antipatterns,” Interational J. Coop. Inf. Syst. IJCIS, no. In Press, 2016.
[42] J. González-Huerta, S. Abrahão, and E. Insfran, “Automatic Derivation of AADL Product Architectures in Software Product Line Development,” in Architecture Centric Virtual Integration, 2014, pp. 69–78.
[43] J. Gonzalez-Huerta, E. Insfran, S. Abrahão, and G. Scanniello, “Validating a model-driven software architecture evaluation and improvement method: A family of experiments,” Inf. Softw. Technol., vol. 57, pp. 405–429, Jan. 2015.
[44] N. Lassing, P. Bengtsson, H. van Vliet, and J. Bosch, “Experiences with ALMA: Architecture-Level Modifiability Analysis,” J. Syst. Softw., vol. 61, no. 1, pp. 47–57, 2002.
[45] F. Pettersson, M. Ivarsson, T. Gorschek, and P. Öhman, “A practitioner’s guide to light weight software process assessment and improvement planning,” J. Syst. Softw., vol. 81, no. 6, pp. 972–995, Jun. 2008.
[46] M. Khurum, K. Petersen, and T. Gorschek, “Extending value stream mapping through waste definition beyond customer perspective,” J. Softw. Evol. Process, vol. 26, no. 12, pp. 1074–1105, Dec. 2014.
[47] N. Bin Ali, K. Petersen, and B. B. N. De França, “Evaluation of simulation-assisted value stream mapping for software product development: Two industrial cases,” Inf. Softw. Technol., vol. 68, pp. 45–61, 2015.
[48] K. Petersen and C. Wohlin, “The effect of moving from a plan-driven to an incremental software development approach with agile practices: An industrial case study,” Empir. Softw. Eng., vol. 15, no. 6, pp. 654–693, 2010.
[49] C. Giardino, N. Paternoster, M. Unterkalmsteiner, T. Gorschek, and P. Abrahamsson, “Software Development in Startup Companies: The Greenfield Startup Model,” IEEE Trans. Softw. Eng., vol. 42, no. 6, pp. 585–604, 2016.
[50] K. Petersen and C. Wohlin, “Software process improvement through the Lean Measurement (SPI-LEAM) method,” J. Syst. Softw., vol. 83, no. 7, pp. 1275–1287, 2010.
[51] C. Gencel, K. Petersen, A. A. Mughal, and M. I. Iqbal, “A decision support framework for metrics selection in goal-based measurement programs: GQM-DSFMS,” J. Syst. Softw., vol. 86, no. 12, pp. 3091–3108, 2013.
[1] http://www.mynewsdesk.com/se/bth/pressreleases/bth-toppar-listan-oever-vetenskapliga-artiklar-i-mjukvaruutveckling-1923567
In collaboration with:
