{"id":810,"date":"2018-05-27T11:57:41","date_gmt":"2018-05-27T11:57:41","guid":{"rendered":"http:\/\/www.gonzalez-huerta.net\/?page_id=810"},"modified":"2018-05-27T12:25:14","modified_gmt":"2018-05-27T12:25:14","slug":"shade-a-value-oriented-strategy-to-handle-software-asset-degradation-references","status":"publish","type":"page","link":"http:\/\/www.gonzalez-huerta.net\/?page_id=810","title":{"rendered":"SHADE \u2013 A Value-Oriented Strategy to Handle Software Asset Degradation: References"},"content":{"rendered":"

Back<\/a><\/p>\n

References<\/h2>\n

[1] Jan Bosch, Speed, Data, and Ecosystems: Excelling in a Software-Driven World<\/em>. CRC Press, Taylor and Francis Group, 2016.<\/p>\n

[2] W. Cunningham, \u201cThe WyCash portfolio management system,\u201d Proc. Object-Oriented Program. Syst. Lang. Appl. (OOPSLA \u201992)<\/em>, vol. 4, no. 2, pp. 29\u201330, Apr. 1993.<\/p>\n

[3] Andy Kyte, \u201cMeasure and Manage Your IT Debt,\u201d Gartner<\/em>, 2010. [Online]. Available: https:\/\/www.gartner.com\/doc\/1419325\/measure-manage-it-debt. [Accessed: 10-Apr-2017].<\/p>\n

[4] Bill Curtis, \u201cArchitecturally Complex Defects | CISQ \u2013 Consortium for IT Software Quality,\u201d 2012. [Online]. Available: http:\/\/it-cisq.org\/architecturally-complex-defects\/. [Accessed: 10-Apr-2017].<\/p>\n

[5] M. Khurum, T. Gorschek, and M. Wilson, \u201cThe software value map \u2013 an exhaustive collection of value aspects for the development of software intensive products,\u201d J. Softw. Evol. Process<\/em>, vol. 25, no. 7, pp. 711\u2013741, Jul. 2013.<\/p>\n

[6] Z. Li, P. Avgeriou, and P. Liang, \u201cA systematic mapping study on technical debt and its management,\u201d J. Syst. Softw.<\/em>, vol. 101, pp. 193\u2013220, 2015.<\/p>\n

[7] T. Besker, A. Martini, and J. Bosch, \u201cA Systematic Literature Review and a Unified Model of ATD,\u201d in 2016 42th Euromicro Conference on Software Engineering and Advanced Applications (SEAA)<\/em>, 2016, pp. 189\u2013197.<\/p>\n

[8] E. Tom, A. Aurum, and R. Vidgen, \u201cAn exploration of technical debt,\u201d J. Syst. Softw.<\/em>, vol. 86, no. 6, pp. 1498\u20131516, 2013.<\/p>\n

[9] A. Ampatzoglou, A. Ampatzoglou, A. Chatzigeorgiou, and P. Avgeriou, \u201cThe financial aspect of managing technical debt: A systematic literature review,\u201d in Information and Software Technology<\/em>, 2015, vol. 64.<\/p>\n

[10]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 N. Moha and Y. Gu\u00e9h\u00e9neuc, \u201cDECOR: A method for the specification and detection of code and design smells,\u201d IEEE Trans. Softw. Eng.<\/em>, vol. 36, no. 1, pp. 20\u201336, 2010.<\/p>\n

[11]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 N. Tsantalis, T. Chaikalis, and A. Chatzigeorgiou, \u201cJDeodorant: Identification and removal of type-checking bad smells,\u201d in Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR<\/em>, 2008, pp. 329\u2013331.<\/p>\n

[12]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SonarSource, \u201cSonarQube: Continuous Code Quality.\u201d [Online]. Available: https:\/\/www.sonarqube.org\/.<\/p>\n

[13]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 J. Holvitie and V. Leppanen, \u201cDebtFlag: Technical debt management with a development environment integrated tool,\u201d 2013 4th Int. Work. Manag. Tech. Debt, MTD 2013 \u2013 Proc.<\/em>, pp. 20\u201327, 2013.<\/p>\n

[14]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 A. Martini, J. Bosch, and M. Chaudron, \u201cInvestigating Architectural Technical Debt accumulation and refactoring over time: A multiple-case study,\u201d Inf. Softw. Technol.<\/em>, vol. 67, pp. 237\u2013253, 2015.<\/p>\n

[15]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 R. Kazman, Y. Cai, R. Mo, Q. Feng, L. Xiao, S. Haziyev, V. Fedak, and A. Shapochka, \u201cA Case Study in Locating the Architectural Roots of Technical Debt,\u201d in Proceedings \u2013 International Conference on Software Engineering<\/em>, 2015, pp. 179\u2013188.<\/p>\n

[16]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 K. Power, \u201cUnderstanding 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,\u201d in 2013 4th International Workshop on Managing Technical Debt (MTD)<\/em>, 2013, pp. 28\u201331.<\/p>\n

[17]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C. Fern\u00e1ndez-S\u00e1nchez, J. Garbajosa, A. Yag\u00fce, and J. Perez, \u201cIdentification and analysis of the elements required to manage technical debt by means of a systematic mapping study,\u201d J. Syst. Softw.<\/em>, vol. 124, pp. 22\u201338, 2017.<\/p>\n

[18]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 P. Avgeriou, P. Kruchten, R. L. Nord, I. Ozkaya, and C. Seaman, \u201cReducing friction in software development,\u201d IEEE Softw.<\/em>, vol. 33, no. 1, pp. 66\u201372, 2016.<\/p>\n

[19]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 E. Al\u00e9groth and J. Gonzalez-Huerta, \u201cTowards a Mapping of Software Technical Debt onto Testware,\u201d in SEAA 2017 Euromicro Conference on Software Engineering and Advanced Applications<\/em>, 2017.<\/p>\n

[20]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Petter M\u00e5hl\u00e9n, \u201cQualities of Quality | Labs,\u201d Spotify Labs<\/em>, 2014. [Online]. Available: https:\/\/labs.spotify.com\/2014\/04\/11\/qualities-of-quality\/.<\/p>\n

[21]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 P. Avgeriou, P. Kruchten, I. Ozkaya, C. Seaman, and C. Seaman, \u201cManaging Technical Debt in Software Engineering,\u201d in Dagstuhl Reports<\/em>, 2016, vol. 6, no. 4, pp. 110\u2013138.<\/p>\n

[22]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 M. Fowler, K. Beck, J. Brant, W. Opdyke, and D. Roberts, Refactoring: Improving the Design of Existing Code<\/em>. Addison Wesley, 1999.<\/p>\n

[23]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 E. Murphy-Hill, C. Parnin, and A. P. Black, \u201cHow We Refactor, and How We Know It,\u201d IEEE Trans. <\/em>Softw. Eng.<\/em>, vol. 38, no. 1, pp. 5\u201318, Jan. 2012.<\/p>\n

[24]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 G. Bavota, B. De Carluccio, A. De Lucia, M. Di Penta, R. Oliveto, and O. Strollo, \u201cWhen Does a Refactoring Induce Bugs? An Empirical Study,\u201d in 2012 IEEE 12th International Working Conference on Source Code Analysis and Manipulation<\/em>, 2012, pp. 104\u2013113.<\/p>\n

[25]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 G. Bavota, A. De Lucia, M. Di Penta, R. Oliveto, and F. Palomba, \u201cAn experimental investigation on the innate relationship between quality and refactoring,\u201d J. Syst. Softw.<\/em>, vol. 107, pp. 1\u201314, 2015.<\/p>\n

[26]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 J. Holvitie, S. A. Licorish, and V. Leppanen, \u201cModelling Propagation of Technical Debt,\u201d in 2016 42th Euromicro Conference on Software Engineering and Advanced Applications (SEAA)<\/em>, 2016, pp. 54\u201358.<\/p>\n

[27]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 B. Curtis, J. Sappidi, and A. Szynkarski, \u201cEstimating the size, cost, and types of technical debt,\u201d 2012 3rd Int. Work. Manag. Tech. Debt, MTD 2012 \u2013 Proc.<\/em>, pp. 49\u201353, 2012.<\/p>\n

[28]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 V. Garousi, K. Petersen, and B. Ozkan, \u201cChallenges and best practices in industry-academia collaborations in software engineering: A systematic literature review,\u201d Inf. Softw. Technol.<\/em>, vol. 79, pp. 106\u2013127, 2016.<\/p>\n

[29]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 H. Kniberg, \u201cSpotify engineering culture (part 1 & 2),\u201d Spotify Labs<\/em>, 2014. [Online]. Available: https:\/\/labs.spotify.com\/2014\/03\/27\/spotify-engineering-culture-part-1\/.<\/p>\n

[30]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 B. Kitchenham, \u201cGuidelines for performing Systematic Literature Reviews in Software Engineering,\u201d EBSE Technical Report, Keele University, UK, 2007.<\/p>\n

[31]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 K. Petersen, S. Vakkalanka, and L. Kuzniarz, \u201cGuidelines for conducting systematic mapping studies in software engineering\u202f: An update,\u201d Inf. Softw. Technol.<\/em>, vol. 64, pp. 1\u201318, 2015.<\/p>\n

[32]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 P. Runeson, M. Host, A. Rainer, and B. Regnell, Case Study Research in Software Engineering: Guidelines and Examples<\/em>. John Wiley & Sons, 2012.<\/p>\n

[33]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 G. Hecht, R. Rouvoy, N. Moha, and J. Gonz\u00e1lez-Huerta, \u201cAn Empirical Analysis of Android Code Smells,\u201d IEEE Trans. Softw. Eng.<\/em>, p. To be resubmitted, 2017.<\/p>\n

[34]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 V. Braun and V. Clarke, \u201cUsing thematic analysis in psychology,\u201d Qual. Res. Psychol.<\/em>, vol. 3, no. 2, pp. 77\u2013101, Jan. 2006.<\/p>\n

[35]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 B. G. Glaser and A. L. Strauss, The discovery of grounded theory<\/em>\u202f<\/em>: strategies for qualitative research<\/em>. Aldine Pub. Co, 1967.<\/p>\n

[36]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 K.-J. Stol, P. Ralph, and B. Fitzgerald, \u201cGrounded Theory in Software Engineering Research: A Critical Review and Guidelines,\u201d 2016.<\/p>\n

[37]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 T. Gorschek, C. Wohlin, P. Garre, and S. Larsson, \u201cA Model for Technology Transfer in Practice,\u201d IEEE Softw.<\/em>, vol. 23, no. 6, pp. 88\u201395, 2006.<\/p>\n

[38]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 K. Petersen, C. Gencel, N. Asghari, D. Baca, and S. Betz, \u201cAction research as a model for industry-academia collaboration in the software engineering context,\u201d in Proceedings of the 2014 international workshop on Long-term industrial collaboration on software engineering \u2013 WISE \u201914<\/em>, 2014, pp. 55\u201362.<\/p>\n

[39]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 S.-W. Chuang, T. Luor, and H.-P. Lu, \u201cAssessment of institutions, scholars, and contributions on agile software development (2001\u20132012),\u201d J. Syst. Softw.<\/em>, vol. 93, pp. 84\u2013101, Jul. 2014.<\/p>\n

[40]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 F. Palma, J. Gonzalez-Huerta, N. Moha, Y. G. Gu\u00e9h\u00e9neuc, and G. Tremblay, \u201cAre RESTful APIs well-designed? Detection of their linguistic (Anti)patterns,\u201d in 13th International Conference on Service Oriented Computing (ICSOC2015)<\/em>, 2015, vol. 9435, pp. 171\u2013187.<\/p>\n

[41]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 F. Palma, J. Gonzalez-Huerta, M. Founi, N. Moha, G. Tremblay, and Y.-G. Gu\u00e9h\u00e9neuc, \u201cSemantic Analysis of RESTFul APIs for the Detection of Linguistic Patterns and Antipatterns,\u201d Interational J. Coop. Inf. Syst. IJCIS<\/em>, no. In Press, 2016.<\/p>\n

[42]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 J. Gonz\u00e1lez-Huerta, S. Abrah\u00e3o, and E. Insfran, \u201cAutomatic Derivation of AADL Product Architectures in Software Product Line Development,\u201d in Architecture Centric Virtual Integration<\/em>, 2014, pp. 69\u201378.<\/p>\n

[43]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 J. Gonzalez-Huerta, E. Insfran, S. Abrah\u00e3o, and G. Scanniello, \u201cValidating a model-driven software architecture evaluation and improvement method: A family of experiments,\u201d Inf. Softw. Technol.<\/em>, vol. 57, pp. 405\u2013429, Jan. 2015.<\/p>\n

[44]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 N. Lassing, P. Bengtsson, H. van Vliet, and J. Bosch, \u201cExperiences with ALMA: Architecture-Level Modifiability Analysis,\u201d J. Syst. Softw.<\/em>, vol. 61, no. 1, pp. 47\u201357, 2002.<\/p>\n

[45]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 F. Pettersson, M. Ivarsson, T. Gorschek, and P. \u00d6hman, \u201cA practitioner\u2019s guide to light weight software process assessment and improvement planning,\u201d J. Syst. Softw.<\/em>, vol. 81, no. 6, pp. 972\u2013995, Jun. 2008.<\/p>\n

[46]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 M. Khurum, K. Petersen, and T. Gorschek, \u201cExtending value stream mapping through waste definition beyond customer perspective,\u201d J. Softw. Evol. Process<\/em>, vol. 26, no. 12, pp. 1074\u20131105, Dec. 2014.<\/p>\n

[47]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 N. Bin Ali, K. Petersen, and B. B. N. De Fran\u00e7a, \u201cEvaluation of simulation-assisted value stream mapping for software product development: Two industrial cases,\u201d Inf. Softw. Technol.<\/em>, vol. 68, pp. 45\u201361, 2015.<\/p>\n

[48]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 K. Petersen and C. Wohlin, \u201cThe effect of moving from a plan-driven to an incremental software development approach with agile practices: An industrial case study,\u201d Empir. Softw. Eng.<\/em>, vol. 15, no. 6, pp. 654\u2013693, 2010.<\/p>\n

[49]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C. Giardino, N. Paternoster, M. Unterkalmsteiner, T. Gorschek, and P. Abrahamsson, \u201cSoftware Development in Startup Companies: The Greenfield Startup Model,\u201d IEEE Trans. Softw. Eng.<\/em>, vol. 42, no. 6, pp. 585\u2013604, 2016.<\/p>\n

[50]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 K. Petersen and C. Wohlin, \u201cSoftware process improvement through the Lean Measurement (SPI-LEAM) method,\u201d J. Syst. Softw.<\/em>, vol. 83, no. 7, pp. 1275\u20131287, 2010.<\/p>\n

[51]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C. Gencel, K. Petersen, A. A. Mughal, and M. I. Iqbal, \u201cA decision support framework for metrics selection in goal-based measurement programs: GQM-DSFMS,\u201d J. Syst. Softw.<\/em>, vol. 86, no. 12, pp. 3091\u20133108, 2013.<\/p>\n

[1]<\/a> http:\/\/www.mynewsdesk.com\/se\/bth\/pressreleases\/bth-toppar-listan-oever-vetenskapliga-artiklar-i-mjukvaruutveckling-1923567<\/a><\/p>\n

In collaboration with:<\/h2>\n

\"\"<\/a>\"\"<\/a><\/p>\n

Funded by:<\/h2>\n

\"\"<\/a><\/h2>\n","protected":false},"excerpt":{"rendered":"

Back References [1] Jan Bosch, Speed, Data, and Ecosystems: Excelling in a Software-Driven World. CRC Press, Taylor and Francis Group, 2016. [2] W. Cunningham, \u201cThe WyCash portfolio management system,\u201d Proc. Object-Oriented Program. Syst. Lang. Appl. (OOPSLA \u201992), vol. 4, no. 2, pp. 29\u201330, Apr. 1993. [3] Andy Kyte, \u201cMeasure and Manage Your IT Debt,\u201d Gartner, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"class_list":["post-810","page","type-page","status-publish","hentry"],"aioseo_notices":[],"_links":{"self":[{"href":"http:\/\/www.gonzalez-huerta.net\/index.php?rest_route=\/wp\/v2\/pages\/810","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.gonzalez-huerta.net\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/www.gonzalez-huerta.net\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/www.gonzalez-huerta.net\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.gonzalez-huerta.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=810"}],"version-history":[{"count":3,"href":"http:\/\/www.gonzalez-huerta.net\/index.php?rest_route=\/wp\/v2\/pages\/810\/revisions"}],"predecessor-version":[{"id":828,"href":"http:\/\/www.gonzalez-huerta.net\/index.php?rest_route=\/wp\/v2\/pages\/810\/revisions\/828"}],"wp:attachment":[{"href":"http:\/\/www.gonzalez-huerta.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=810"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}