University of Groningen

Large scale continuous integration and deliveryStahl, Daniel

IMPORTANT NOTE: You are advised to consult the publisher's version (publisher's PDF) if you wish to cite fromit. Please check the document version below.

Document VersionPublisher's PDF, also known as Version of record

Publication date:2017

Link to publication in University of Groningen/UMCG research database

Citation for published version (APA):Stahl, D. (2017). Large scale continuous integration and delivery: Making great software better and faster.[Groningen]: University of Groningen.

CopyrightOther 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 theauthor(s) and/or copyright holder(s), unless the work is under an open content license (like Creative Commons).

Take-down policyIf you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediatelyand investigate your claim.

Downloaded from the University of Groningen/UMCG research database (Pure): http://www.rug.nl/research/portal. For technical reasons thenumber of authors shown on this cover page is limited to 10 maximum.

Download date: 02-10-2020

Bibliography

[Ablett 2007] Ablett, R., Sharlin, E., Maurer, F., Denzinger, J., & Schock, C. (2007). BuildBot: robotic monitoring of agile software development teams. In The 16th IEEE International Symposium on Robot and Human interactive Communication, 2007. (pp. 931-936). IEEE.

[Abrantes 2011] Abrantes, J. F., & Travassos, G. H. (2011). Common agile practices in software processes. In International Symposium on Empirical Software Engineering and Measurement (ESEM), 2011 (pp. 355-358). IEEE.

[Abreu 2015] Abreu, R., Erdogmus, H., & Perez, A. (2015). CodeAware: sensor-based fine-grained monitoring and management of software artifacts. In Proceedings of the 37th International Conference on Software Engineering-Volume 2 (pp. 551-554). IEEE Press.

[Agile 2001] The Agile Manifesto [Online].Available: http://agilemanifesto.org.Accessed: 25 September 2012.

[Agresti 2011] Agresti, A., & Kateri, M. (2011). Categorical data analysis (pp. 206-208). Springer Berlin Heidelberg.

[Alyahya 2011] Alyahya, S., Ivins, W. K., & Gray, W. A. (2011). Co-ordination support for managing progress of distributed agile projects. In Sixth International Conference on Global Software Engineering Workshop (pp. 31-34). IEEE.

[Alyahya 2012] AlYahya, S., Ivins, W. K., & Gray, W. A. (2012). A holistic approach to developing a progress tracking system for distributed agile teams. In 11th International Conference on Computer and Information Science (ICIS), 2012(pp. 503-512). IEEE.

[Antoniol 2002] Antoniol, G., Canfora, G., Casazza, G., De Lucia, A., & Merlo, E. (2002). Recovering traceability links between code and documentation. IEEE Transactions on Software Engineering, 28(10), 970-983.

[Asuncion 2009] Asuncion, H. U., & Taylor, R. N. (2009). Capturing custom link semantics among heterogeneous artifacts and tools. In Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering (pp. 1-5). IEEE Computer Society.

[Asuncion 2010] Asuncion, H. U., Asuncion, A. U., & Taylor, R. N. (2010). Software traceability with topic modeling. In Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering-Volume 1 (pp. 95-104). ACM.

[Bartoszuk 2014] Bartoszuk, C., Timoszuk, G., Dabrowski, R., & Stencel, K. (2014). On VisualAssessment of Software Quality. e-Informatica Software Engineering Journal, 8(1), 7-26.

233

[Baumeister 2011] Baumeister, J., & Reutelshoefer, J. (2011). Developing knowledge systems with continuous integration. In Proceedings of the 11th International Conference on Knowledge Management and Knowledge Technologies (Article No. 33). ACM.

[Beaumont 2012] Beaumont, O., Bonichon, N., Courtes, L., Hanin, X., & Dolstra, E. (2012). Mixed data-parallel scheduling for distributed continuous integration. In 26thInternational Parallel and Distributed Processing Symposium Workshops & PhD Forum (IPDPSW), 2012 (pp. 91-98). IEEE.

[Bouillon 2013] Bouillon, E., Mäder, P., & Philippow, I. (2013). A survey on usage scenarios for requirements traceability in practice. In International Working Conference on Requirements Engineering: Foundation for Software Quality (pp. 158-173). Springer Berlin Heidelberg.

[Beck 1999] Beck, K. (1999). Embracing change with extreme programming. Computer, 32(10), 70-77.

[Beck 2000] Beck, K. (2000). Extreme programming explained: embrace change. Addison-Wesley Professional.

[Beck 2005] Beck, K., & Andres, C. (2005). Extreme programming explained: embrace change, 2nd edition. Addison-Wesley Professional.

[BEL-V 2013] BEL-V, BfS, CSN, ISTec, ONR, SSM, STUK (2013). Licensing of safety critical software for nuclear reactors.

[Bellomo 2014] Bellomo, S., Ernst, N., Nord, R., & Kazman, R. (2014). Toward Design Decisions to Enable Deployability: Empirical Study of Three Projects Reaching for the Continuous Delivery Holy Grail. In 44th Annual IEEE/IFIPInternational Conference on Dependable Systems and Networks (pp. 702-707). IEEE.

[Boehm 1984] Boehm, B. W. January 1984,“Software Engineering Economics,“. IEEE Transactions on Software Engineering, 4-21.

[Boehm 2000] Boehm, B. W., Madachy, R., & Steece, B. (2000). Software cost estimation with Cocomo II with Cdrom. Prentice Hall PTR.

[Boehm 2005] Boehm, B., & Turner, R. (2005). Management challenges to implementing agile processes in traditional development organizations. Software, IEEE, 22(5), 30-39.

[Breivold 2010] Breivold, H. P., Sundmark, D., Wallin, P., & Larsson, S. (2010). What does research say about agile and architecture?. In Fifth International Conference on Software Engineering Advances (ICSEA), 2010 (pp. 32-37). IEEE.

[Briand 1996] Briand, L. C., Morasca, S., & Basili, V. R. (1996). Property-based software engineering measurement. IEEE Transactions on Software Engineering, 22(1), 68-86.

[Brooks 1975] Brooks, F. P. (1975). Jr. The Mythical Man-Month. Essays on Software Engineering. Addison-Wesley Publishing Company.

[Brooks 2008] Brooks, G. (2008). Team pace keeping build times down. In Agile Conference, 2008 (pp. 294-297). IEEE.

[Brown 2013] Brown, S. (2013). Software Architecture for Developers. Coding the Architecture.

234

[Bowyer 2006] Bowyer, J., & Hughes, J. (2006). Assessing undergraduate experience of continuous integration and test-driven development. In Proceedings of the 28th international conference on Software engineering (pp. 691-694). ACM.

[Cannizzo 2008] Cannizzo, F., Clutton, R., & Ramesh, R. (2008). Pushing the boundaries of testing and continuous integration. In Agile Conference, 2008 (pp. 501-505). IEEE.

[Cleland-H. 2014] Cleland-Huang, J., Gotel, O. C., Huffman Hayes, J., Mäder, P., & Zisman, A. (2014). Software traceability: trends and future directions. In Proceedings of the on Future of Software Engineering (pp. 55-69). ACM.

[Clements 2002] Clements, P., & Northrop, L. (2002). Software product lines. Addison-Wesley.

[CoEST 2015] Center of Excellence of Software Traceability [Online].Available: http://coest.org.Accessed: 11 June 2015

[Cohan 2008] Cohan, S. (2008). Successful customer collaboration resulting in the right product for the end user. In Agile Conference, 2008 (pp. 284-288). IEEE.

[Cohn 2005] Cohn, M. (2005). Agile estimating and planning. Pearson Education.

[Cohn 2010] Cohn, M. (2010). Succeeding with agile: software development using Scrum. Pearson Education.

[Collis 2009] Collis, J., & Hussey, R. (2009). Business Research: A Practical Guide for Undergraduate and Postgraduate Students. Palgrave Macmillan.

[Conway 1968] Conway, M. E. (1968). How do committees invent. Datamation, 14(4), 28-31.

[Cook 1979] Cook, T. D., Campbell, D. T., & Day, A. (1979). Quasi-experimentation: Design & analysis issues for field settings (Vol. 351). Boston: Houghton Mifflin.

[Creswell 2007] Creswell, J. W. (2007). Qualitative Inquiry & Research Design. Sage Publications, Inc., pp. 40, 73-74.

[Cruzes 2011] Cruzes, D. S., & Dybå, T. (2011). Recommended steps for thematic synthesisin software engineering. In 2011 International Symposium on Empirical Software Engineering and Measurement (pp. 275-284). IEEE.

[Dabrowski 2012] Dąbrowski, R., Stencel, K., & Timoszuk, G. (2012). Improving software quality by improving architecture management. In Proceedings of the 13th International Conference on Computer Systems and Technologies (pp. 208-215). ACM.

[Dabrowski 2013] Dąbrowski, R., Timoszuk, G., & Stencel, K. (2013). One graph to rule them all software measurement and management. Fundamenta Informaticae, 128(1-2), 47-63.

[Diaz 2012] V. Garcia-Diaz, B. C. Pelayo Garcia-Bustelo, and J. M. Cueva Lovelle. Mdci:Model-driven continuous integration. Journal of Ambient Intelligence and Smart Environments, 4(5):479-481, 2012.

235

[Dömges 1998] Dömges, R., & Pohl, K. (1998). Adapting traceability environments to project-specific needs. Communications of the ACM, 41(12), 54-62.

[Downs 2010] Downs, J., Hosking, J., & Plimmer, B. (2010). Status communication in agile software teams: A case study. In Fifth International Conference on Software Engineering Advances (ICSEA), 2010 (pp. 82-87). IEEE.

[Downs 2012] Downs, J., Plimmer, B., & Hosking, J. G. (2012). Ambient awareness of build status in collocated software teams. In Proceedings of the 34th International Conference on Software Engineering (pp. 507-517). IEEE Press.

[Duvall 2007] Duvall, P. M. (2007). Continuous Integration. Addison-Wesley.

[Dybå 2008] Dybå, T., & Dingsøyr, T. (2008). Empirical studies of agile software development: A systematic review. Information and software technology, 50(9), 833-859.

[Dösinger 2012] Dösinger, S., Mordinyi, R., & Biffl, S. (2012). Communicating continuous integration servers for increasing effectiveness of automated testing. In Proceedings of the 27th IEEE/ACM International Conference on Automated Software Engineering (pp. 374-377). ACM.

[Easterbrook 2008] Easterbrook, S., Singer, J., Storey, M. A., & Damian, D. (2008). Selecting empirical methods for software engineering research. In Guide to advanced empirical software engineering (pp. 285-311). Springer London.

[ECSS 2015] European Cooperation for Space Standardization (2015). ECSS-E-40C.

[Fenton 2000] Fenton, N. E., & Neil, M. (2000). Software metrics: roadmap. In Proceedingsof the Conference on the Future of Software Engineering (pp. 357-370). ACM.

[Fitzgerald 2006] Fitzgerald, B. (2006). The transformation of open source software. Mis Quarterly, 587-598.

[Fowler 2006] Fowler, M. Continuous Integration [Online]. Available: http://martinfowler.com/articles/continuousIntegration.htmlAccessed: 30 January 2013.

[Fowler 2012] Fowler, M. Test Pyramid [Online]. Available: http://martinfowler.com/bliki/TestPyramid.htmlAccessed: 24 May 2016.

[Fowler 2013] Fowler, M. Continuous Delivery [Online].Available: http://martinfowler.com/bliki/ContinuousDelivery.htmlAccessed: 20 November 2015.

[Gatrell 2009] Gatrell, M., Counsell, S., & Hall, T. (2009). Empirical support for two refactoring studies using commercial C# software. In 13th International Conference on Evaluation & Assessment in Software Engineering (pp. 1-10).

[Genuchten 2007] Van Genuchten, M. (2007). The impact of software growth on the electronics industry. IEEE Computer, 40(1), 106-108.

[Gestwicki 2012] Gestwicki, P. (2012). The entity system architecture and its application in an undergraduate game development studio. In Proceedings of the International Conference on the Foundations of Digital Games (pp. 73-80). ACM.

236

[Gilb 1976] Gilb, T. (1976). Software metrics. Winthrop Publishers.

[Goodman 2008] Goodman, D., & Elbaz, M. (2008). "It's Not the Pants, it's the People in the Pants" Learnings from the Gap Agile Transformation What Worked, How We Did it, and What Still Puzzles Us. In Agile Conference, 2008 (pp. 112-115). IEEE.

[Gotel 1994] Gotel, O. C., & Finkelstein, C. W. (1994). An analysis of the requirements traceability problem. In Proceedings of the First International Conference onRequirements Engineering (pp. 94-101). IEEE.

[Grady 1994] Grady, B. (1994). Object-oriented analysis and design with applications. Benjamin/Cummings Publishing Company.

[Gregory 2015] Gregory, J., & Crispin, L. (2014). More Agile Testing: Learning Journeys for the Whole Team. Addison-Wesley Professional.

[GtAP 2011] Guide to Agile Practices [Online].Available: http://guide.agilealliance.org.Accessed: 25 September 2012.

[Halstead 1977] Halstead, M. H. (1977). Elements of software science (Vol. 7, p. 127). New York: Elsevier.

[Hevner 2004] Von Alan, R. H., March, S. T., Park, J., & Ram, S. (2004). Design science in information systems research. MIS quarterly, 28(1), 75-105.

[Hill 2008] Hill, J. H., Schmidt, D. C., Porter, A. A., & Slaby, J. M. (2008). CiCUTS: combining system execution modeling tools with continuous integration environments. In 15th Annual IEEE International Conference and Workshop on the Engineering of Computer Based Systems, 2008 (pp. 66-75). IEEE.

[Hoffman 2009] Hoffman, B., Cole, D., & Vines, J. (2009). Software process for rapid development of HPC software using CMake. In DoD High Performance Computing Modernization Program Users Group Conference (HPCMP-UGC), 2009 (pp. 378-382). IEEE.

[Hofmeister 2000] Hofmeister, C., Nord, R., & Soni, D. (2000). Applied software architecture. Addison-Wesley Professional.

[Holck 2003] Holck, J., & Jørgensen, N. (2003). Continuous integration and quality assurance: A case study of two open source projects. Australasian Journal of Information Systems, 11(1).

[Holmes 2006] Holmes, A., & Kellogg, M. (2006). Automating functional tests using Selenium. In Agile Conference, 2006 (pp. 270-275). IEEE.

[Hove 2005] Hove, S. E., & Anda, B. (2005). Experiences from conducting semi-structured interviews in empirical software engineering research. In 11th IEEE International Software Metrics Symposium (METRICS'05) (pp. 10-pp). IEEE.

[Huang 2008] Huang, H. Y., Liu, H. H., Li, Z. J., & Zhu, J. (2008). Surrogate: A simulation apparatus for continuous integration testing in service oriented architecture. In IEEE International Conference on Services Computing, 2008 (Vol. 2, pp. 223-230). IEEE.

237

[Huang 2012] Huang, Y. C., Peng, K. L., & Huang, C. Y. (2012). A history-based cost-cognizant test case prioritization technique in regression testing. Journal of Systems and Software, 85(3), 626-637.

[Humble 2010] Humble, J., & Farley, D. (2010). Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation. Pearson Education.

[ISO 42010 2015a] ISO/IEC/IEEE 42010 [Online].Available: http://www.iso-architecture.org/42010.Accessed: 22 April 2015.

[ISO 42010 2015b] ISO/IEC/IEEE 42010 frequently asked questions [Online].Available: http://www.iso-architecture.org/42010/faq.html.Accessed: 22 April 2015.

[ISO 42010 2015c] ISO/IEC/IEEE 42010 survey of architecture frameworks [Online].Available: http://www.iso-architecture.org/42010/afs/frameworks-table.html.Accessed: 12 March 2015.

[Janus 2012] Janus, A., Dumke, R., Schmietendorf, A., & Jäger, J. (2012). The 3C approach for agile quality assurance. In 3rd International Workshop on Emerging Trends in Software Metrics (WETSoM), 2012 (pp. 9-13). IEEE.

[Jiang 2012] Jiang, B., Zhang, Z., Chan, W. K., Tse, T. H., & Chen, T. Y. (2012). How welldoes test case prioritization integrate with statistical fault localization?. Information and Software Technology, 54(7), 739-758.

[Kalantar 2014] Kalantar, M. H., Rosenberg, F., Doran, J., Eilam, T., Elder, M. D., Oliveira, F., ... & Roth, T. (2014). Weaver: Language and runtime for software defined environments. IBM Journal of Research and Development, 58(2/3), 10-1.

[Karlström 2002] Karlström, D. (2002). Introducing extreme programming-an experience report. In Proceedings of the 3rd International Conference on eXtreme Processing and Agile Processing Software Engineering (XP2002).

[Khomh 2012] Khomh, F., Dhaliwal, T., Zou, Y., & Adams, B. (2012, June). Do faster releases improve software quality? an empirical case study of mozilla firefox.In 9th IEEE Working Conference on Mining Software Repositories (MSR), (pp. 179-188). IEEE.

[Ki 2009] Ki, Y., & Song, M. (2009). An Open Source-Based Approach to Software Development Infrastructures. In Proceedings of the 2009 IEEE/ACM International Conference on Automated Software Engineering (pp. 525-529). IEEE Computer Society.

[Kim 2008] Kim, S., Park, S., Yun, J., & Lee, Y. (2008). Automated continuous integration of component-based software: An industrial experience. In Proceedings of the 23rd IEEE/ACM International Conference on Automated Software Engineering, 2008 (pp. 423-426). IEEE Computer Society.

[Kim 2009a] Kim, E. H., Na, J. C., & Ryoo, S. M. (2009). Implementing an effective test automation framework. In 33rd Annual IEEE International Computer Software and Applications Conference, 2009 (Vol. 2, pp. 534-538). IEEE.

[Kim 2009b] Kim, E. H., Na, J. C., & Ryoo, S. M. (2009). Test automation framework for implementing continuous integration. In Sixth International Conference on Information Technology: New Generations, 2009 (pp. 784-789). IEEE.

238

[Kitchenham 2004] Kitchenham, B. (2004). Procedures for performing systematic reviews. Keele, UK, Keele University, 33(2004), 1-26.

[Kitchenham 2007] Kitchenham, B. (2007). Guidelines for performing Systematic Literature Reviews in Software Engineering. Keele, UK, Keele University.

[Klepper 2015] Klepper, S., Krusche, S., Peters, S., Bruegge, B., & Alperowitz, L. (2015). Introducing continuous delivery of mobile apps in a corporate environment: acase study. In Rapid Continuous Software Engineering (RCoSE), 2015 IEEE/ACM 2nd International Workshop on (pp. 5-11). IEEE.

[Kooten 2011] Global Software Top 100 – Edition 2011 [Online].Available: http://www.softwaretop100.org/globalsoftware-top-100-edition-2011. Accessed: 19 December 2012.

[Kruchten 1995] Kruchten, P. B. (1995). The 4+1 view model of architecture. IEEE software, 12(6), 42-50.

[Krusche 2014] Krusche, S., & Alperowitz, L. (2014). Introduction of continuous delivery in multi-customer project courses. In Companion Proceedings of the 36th International Conference on Software Engineering (pp. 335-343). ACM.

[Laanti 2011] Laanti, M., Salo, O., & Abrahamsson, P. (2011). Agile methods rapidly replacing traditional methods at Nokia: A survey of opinions on agile transformation. Information and Software Technology, 53(3), 276-290.

[Lacoste 2009] Lacoste, F. J. (2009). Killing the gatekeeper: Introducing a continuous integration system. In Agile Conference, 2009 (pp. 387-392). IEEE.

[Lagerberg 2013] Lagerberg, L., & Skude, T. (2013). The impact of agile principles and practices on large-scale software development projects: A multiple-case studyof two software development projects at Ericsson. Linköping University, Linköping (MSc Thesis).

[Larman 2009] Larman, C., & Vodde, B. (2010). Practices for scaling lean & Agile development: large, multisite, and offshore product development with large-scale scrum. Pearson Education.

[Leffingwell 2010] Leffingwell, D. (2010). Agile software requirements: lean requirements practices for teams, programs, and the enterprise. Addison-Wesley Professional.

[Lekvall 2001] Lekvall, P., & Wahlbin, C. (2001). Information för marknadsföringsbeslut. IHM Publishing.

[Li 2010] Li, J., Moe, N. B., & Dybå, T. (2010). Transition from a plan-driven process to scrum: a longitudinal case study on software quality. In Proceedings of the2010 ACM-IEEE international symposium on empirical software engineeringand measurement (p. 13). ACM.

[Lier 2012] Lier, F., Wrede, S., Siepmann, F., Lütkebohle, I., Paul-Stueve, T., & Wachsmuth, S. (2012). Facilitating research cooperation through linking and sharing of heterogenous research artefacts: cross platform linking of semantically enriched research artefacts. In Proceedings of the 8th International Conference on Semantic Systems (pp. 157-164). ACM.

239

[v.d. Linden 2007] vd Linden, F. J., Schmid, K., & Rommes, E. (2007). Software Product Lines in Action: The Best Industrial Practice in Product Line Engineering. Secaucus.

[Liu 2009] Liu, H., Li, Z., Zhu, J., Tan, H., & Huang, H. (2009). A unified test framework for continuous integration testing of SOA solutions. In IEEE International Conference on Web Services (ICWS), 2009 (pp. 880-887). IEEE.

[Long 2008] Long, B. (2008). Managing module dependencies to facilitate continuous testing. Information Processing Letters, 108(3), 127-131.

[Mäder 2009] Mader, P., Gotel, O., & Philippow, I. (2009). Motivation matters in the traceability trenches. In 17th IEEE International Requirements Engineering Conference (pp. 143-148). IEEE.

[Mäntylä 2013] Mäntylä, M. V., Khomh, F., Adams, B., Engström, E., & Petersen, K. (2013). On rapid releases and software testing. In 29th International Conference on Software Maintenance (ICSM) (pp. 20-29). IEEE.

[March 1995] March, S. T., & Smith, G. F. (1995). Design and natural science research on information technology. Decision support systems, 15(4), 251-266.

[Mårtensson 2016] Mårtensson, T., Ståhl, D., & Bosch, J. (2016). Continuous Integration Applied to Software-Intensive Embedded Systems – Problems and Experiences. In press; accepted by The 17th International Conference on Product-Focused Software Process Improvement.

[Manzo 2012] Manzo, A. N., & Burke, J. M. (2012). Increasing response rate in web-based/internet surveys. In Handbook of survey methodology for the social sciences (pp. 327-343). Springer New York.

[Matsumoto 2012] Matsumoto, K., Kibe, S., Uehara, M., & Mori, H. (2012). Design of Development as a Service in the Cloud. In 15th International Conference on Network-Based Information Systems (pp. 815-819). IEEE.

[McCabe 1976] McCabe, T. J. (1976). A complexity measure. IEEE Transactions on softwareEngineering, (4), 308-320.

[McHugh 2012] McHugh, O., Conboy, K., & Lang, M. (2012). Agile practices: The impact ontrust in software project teams. Software, IEEE, 29(3), 71-76.

[Meyer 1988] Meyer, B. (1988). Eiffel: A language and environment for software engineering. Journal of Systems and Software, 8(3), 199-246.

[Miller 2008] Miller, A. (2008). A hundred days of continuous integration. In Agile Conference, 2008 (pp. 289-293). IEEE.

[Mishra 2008] Mishra, D., & Mishra, A. (2008). Workspace environment for collaboration in small software development organization. In Cooperative Design, Visualization, and Engineering (pp. 196-203). Springer Berlin Heidelberg.

[Moore 1965] Moore, G. E. (1965). Cramming more components onto integrated circuits. Electronics, 38(8), 114-117.

240

[Moreira 2010] de Souza Pereira Moreira, G., Mellado, R. P., Montini, D. Á., Dias, L. A. V., & Da Cunha, A. M. (2010). Software product measurement and analysis in a continuous integration environment. In Seventh International Conference on Information Technology: New Generations (ITNG), 2010 (pp. 1177-1182). IEEE.

[Morris 1992] Morris, G. (1992). Candlestick charting explained. New York, McGrawHill.

[Mossige 2014] Mossige, M., Gotlieb, A., & Meling, H. (2014). Using CP in automatic test generation for ABB robotics paint control system. In International Conference on Principles and Practice of Constraint Programming (pp. 25-41). Springer International Publishing.

[Nagappan 2008] Nagappan, N., Murphy, B., & Basili, V. (2008). The influence of organizational structure on software quality: an empirical case study. In Proceedings of the 30th international conference on Software engineering (pp. 521-530). ACM.

[Nerur 2005] Nerur, S., Mahapatra, R., & Mangalaraj, G. (2005). Challenges of migrating to agile methodologies. Communications of the ACM, 48(5), 72-78.

[Newman 2015] Newman, S. (2015). Building Microservices. O'Reilly Media, Inc.

[Nilsson 2014] Nilsson, A., Bosch, J., & Berger, C. (2014). Visualizing testing activities to support continuous integration: A multiple case study. In International Conference on Agile Software Development (pp. 171-186). Springer International Publishing.

[Oliveto 2010] Oliveto, R., Gethers, M., Poshyvanyk, D., & De Lucia, A. (2010). On the equivalence of information retrieval methods for automated traceability link recovery. In 18th International Conference on Program Comprehension (ICPC) (pp. 68-71). IEEE.

[Olsson 2012] Olsson, H. H., Alahyari, H., & Bosch, J. (2012). Climbing the "Stairway to Heaven" – A Mulitiple-Case Study Exploring Barriers in the Transition from Agile Development towards Continuous Deployment of Software. In 38th Euromicro Conference on Software Engineering and Advanced Applications (pp. 392-399). IEEE.

[Open-DO 2015] The Open-DO Initiative [Online].Available: http://www.open-do.org.Accessed: 12 June 2015.

[Open Group 2013] The Open Group ArchiMate 2.1 Specification [Online].Available: http://pubs.opengroup.org/architecture/archimate2-doc.Accessed 21 January 2016.

[Perry 1994] Perry, D. E., Staudenmayer, N. A., & Votta, L. G. (1994). People, organizations, and process improvement. IEEE Software, 11(4), 36-45.

[Pesola 2011] Pesola, J. P., Tanner, H., Eskeli, J., Parviainen, P., & Bendas, D. (2011). Integrating early V&V support to a GSE tool integration platform. In Sixth IEEE International Conference on Global Software Engineering Workshop (ICGSEW), 2011 (pp. 95-101). IEEE.

[Petersen 2010] Petersen, K., & Wohlin, C. (2010). The effect of moving from a plan-driven to an incremental software development approach with agile practices. Empirical Software Engineering, 15(6), 654-693.

241

[Pfleeger 2006] Pfleeger, S. L., & Atlee, J. M. (2006). Software Engineering: Theory and Practice. Pearson Education Inc.

[Pikkarainen 2008] Pikkarainen, M., Haikara, J., Salo, O., Abrahamsson, P., & Still, J. (2008). The impact of agile practices on communication in software development. Empirical Software Engineering, 13(3), 303-337.

[QuEST 2015] QuEST Forum, 2015. TL9000 Quality Management System [Online].Available: http://www.tl9000.org. Accessed: 11 June 2015.

[Ramesh 2001] Ramesh, B., & Jarke, M. (2001). Toward reference models for requirements traceability. IEEE Transactions on Software Engineering, 27(1), 58-93.

[Rasmusson 2004] Rasmusson, J. (2004). Long build trouble shooting guide. In Extreme Programming and Agile Methods-XP/Agile Universe 2004 (pp. 13-21). Springer Berlin Heidelberg.

[Rathod 2015] Rathod, N., & Surve, A. (2015). Test orchestration a framework for continuous integration and continuous deployment. In 2015 International Conference on Pervasive Computing (ICPC), (pp. 1-5). IEEE.

[Remencius 2009] Remencius, T., Sillitti, A., & Succi, G. (2009). Using metric visualization andsharing tool to drive agile-related practices. In International Conference on Agile Processes and Extreme Programming in Software Engineering (pp. 255-256). Springer Berlin Heidelberg.

[Rempel 2013] Rempel, P., Mçder, P., & Kuschke, T. (2013). An empirical study on project-specific traceability strategies. In 21st IEEE International Requirements Engineering Conference (pp. 195-204). IEEE.

[Roberts 2004] Roberts, M. (2004). Enterprise continuous integration using binary dependencies. In Extreme Programming and Agile Processes in Software Engineering (pp. 194-201). Springer Berlin Heidelberg.

[Robson 2011] Robson, C. (2011). Real world research, Third Edition. John Wiley & Sons.

[Rodriguez 2014] Rodríguez, P., Haghighatkhah, A., Lwakatare, L. E., Teppola, S., Suomalainen, T., Eskeli, J., ... & Oivo, M. (2016). Continuous deployment of software intensive products and services: A systematic mapping study. Journal of Systems and Software.

[Rogers 2003] Rogers, R. O. (2003). CruiseControl .NET: continuous integration for .NET. In Extreme programming and agile processes in software engineering, LNCS 2675 (pp. 114-122).

[Rogers 2004] Rogers, R. O. (2004). Scaling continuous integration. In Extreme Programming and Agile Processes in Software Engineering (pp. 68-76). Springer Berlin Heidelberg.

[Rooijmans 1996] Rooijmans, J., Aerts, H., & Van Genuchten, M. (1996). Software quality in consumer electronics products. IEEE software, 13(1), 55.

[Rouille 2013] Rouillé, E., Combemale, B., Barais, O., Touzet, D., & Jézéquel, J. M. (2013). Improving reusability in software process lines. In 39th Euromicro Conference on Software Engineering and Advanced Applications (pp. 90-93).IEEE.

242

[RTCA 2011] Radio Technical Commission for Aeronautics (2011). DO-178C, Software Considerations in Airborne Systems and Equipment Certification.

[Rozanski 2005] Rozanski, N., & Woods, E. (2005). Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives.

[Runeson 2009] Runeson, P., & Höst, M. (2009). Guidelines for conducting and reporting case study research in software engineering. Empirical software engineering, 14(2), 131-164.

[Rylander 2008] Rylander, S. (2008). Building a robust development environment. Dr Dobb's Journal, 33(9).

[Scholtes 2016] Scholtes, I., Mavrodiev, P., & Schweitzer, F. (2016). From Aristotle to Ringelmann: a large-scale analysis of team productivity and coordination in Open Source Software projects. Empirical Software Engineering, 21(2), 642-683.

[Schwaber 2004] Schwaber, K. (2004). Agile project management with Scrum. Microsoft press.

[Shaw 2002] Shaw, M. (2002). What makes good research in software engineering?. International Journal on Software Tools for Technology Transfer, 4(1), 1-7.

[Sinnema 2004] Sinnema, M., Deelstra, S., Nijhuis, J., & Bosch, J. (2004). Covamof: A framework for modeling variability in software product families. In Software product lines (pp. 197-213). Springer Berlin Heidelberg.

[Ståhl 2013] Ståhl, D., & Bosch, J. (2013). Experienced benefits of continuous integration in industry software product development: A case study. In The 12th IASTEDInternational Conference on Software Engineering (Innsbruck, Austria, 2013) (pp. 736-743).

[Ståhl 2014a] Ståhl, D., & Bosch, J. (2014). Modeling continuous integration practice differences in industry software development. Journal of Systems and Software, 87, 48-59.

[Ståhl 2014b] Ståhl, D., & Bosch, J. (2014). Automated software integration flows in industry: a multiple-case study. In Companion Proceedings of the 36th International Conference on Software Engineering (pp. 54-63). ACM.

[Ståhl 2014c] Ståhl, D., & Bosch, J. (2014). Continuous integration flows. In Continuous Software Engineering (pp. 107-115). Springer International Publishing.

[Ståhl 2016a] Ståhl, D., Hallén, K., & Bosch, J. (2016). Continuous Integration and Delivery Traceability in Industry: Needs and Practices. In 42nd Euromicro Conference on Software Engineering and Advanced Applications (pp. 68-72).IEEE.

[Ståhl 2016b] Ståhl, D., & Bosch, J. (2016). Industry application of continuous integration modeling: a multiple-case study. In Proceedings of the 38th International Conference on Software Engineering Companion (pp. 270-279). ACM.

[Ståhl 2016c] Ståhl, D., & Bosch, J. (2016). Dynamic Test Case Selection in Continuous Integration: Test Result Analysis using the Eiffel Framework. In press; accepted for inclusion in Analytic Methods in Systems and Software Testing.

[Ståhl 2016d] Ståhl, D., Hallén, K., & Bosch, J. (2016). Achieving traceability in large scalecontinuous integration and delivery deployment: usage and validation of the Eiffel framework. Empirical Software Engineering, 1-29.

243

[Ståhl 2017] Ståhl, D., Mårtensson, T., & Bosch, J. (2017). The continuity of continuous integration: correlations and consequences. In press; accepted by Journal of Systems and Software.

[Stettina 2011] Stettina, C. J., & Heijstek, W. (2011). Necessary and neglected?: an empiricalstudy of internal documentation in agile software development teams. In Proceedings of the 29th ACM international conference on Design of communication (pp. 159-166). ACM.

[Stigler, 1958] Stigler, G. J. (1958). Economies of Scale, The. JL & Econ., 1, 54.

[Stolberg 2009] Stolberg, S. (2009). Enabling agile testing through continuous integration. In Agile Conference, 2009 (pp. 369-374). IEEE.

[v. d. Storm 2005] Van Der Storm, T. (2005). Continuous release and upgrade of component-based software. In Proceedings of the 12th International Workshop on Software Configuration Management (pp. 43-57). ACM.

[v. d. Storm 2007] Van der Storm, T. (2007). The Sisyphus continuous integration system. In 11th European Conference on Software Maintenance and Reengineering, 2007 (pp. 335-336). IEEE.

[v. d. Storm 2008] Van der Storm, T. (2008). Backtracking incremental continuous integration. In 12th European Conference on Software Maintenance and Reengineering, 2009 (pp. 233-242). IEEE.

[Stray 2012] Stray, V. G., Moe, N. B., & Dybå, T. (2012). Escalation of commitment: a longitudinal case study of daily meetings. In Agile Processes in Software Engineering and Extreme Programming (pp. 153-167). Springer Berlin Heidelberg.

[Strode 2011] Strode, D. E., Hope, B. G., Huff, S. L., & Link, S. (2011). Coordination Effectiveness In An Agile Software Development Context. In PACIS (p. 183).

[Strode 2012] Strode, D. E., Huff, S. L., Hope, B., & Link, S. (2012). Coordination in co-located agile software development projects. Journal of Systems and Software, 85(6), 1222-1238.

[Sturdevant 2007] Sturdevant, K. F. (2007). Cruisin' and Chillin': Testing the Java-Based Distributed Ground Data System "Chill" with CruiseControl. In Aerospace Conference, 2007 (pp. 1-8). IEEE.

[Sunindyo 2010] Sunindyo, W. D., Moser, T., Winkler, D., & Biffl, S. (2010). Foundations for event-based process analysis in heterogeneous software engineering environments. In 36th EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA) (pp. 313-322). IEEE.

[Sutherland 2008] Sutherland, J., Jakobsen, C. R., & Johnson, K. (2008). Scrum and CMMI level 5: The magic potion for code warriors. In Hawaii International Conference on System Sciences, Proceedings of the 41st Annual (pp. 466-466). IEEE.

[Sutherland 2011] Sutherland, J., & Frohman, R. (2011). Hitting the wall: what to do when high performing scrum teams overwhelm operations and infrastructure. In 44th Hawaii International Conference on System Sciences (HICSS), 2011 (pp. 1-6). IEEE.

244

[Tingling 2007] Tingling, P., & Saeed, A. (2007). Extreme programming in action: a longitudinal case study. In Human-Computer Interaction. Interaction Design and Usability (pp. 242-251). Springer Berlin Heidelberg.

[Urbaczewski 2006] Urbaczewski, L., & Mrdalj, S. (2006). A comparison of enterprise architecture frameworks. Issues in Information Systems, 7(2), 18-23.

[Wang 2015] Wang, W., Gupta, A., & Wu, Y. (2015). Continuously delivered? Periodically updated? Never changed? Studying an open source project's releases of code,requirements, and trace matrix. In IEEE Workshop on Just-In-Time Requirements Engineering (JITRE) (pp. 13-16). IEEE.

[Watanabe 2012] Watanabe, W. M., Fortes, R. P., & Dias, A. L. (2012). Using acceptance tests to validate accessibility requirements in RIA. In Proceedings of the International Cross-Disciplinary Conference on Web Accessibility (Article No. 15). ACM.

[West 2010] West, D., Grant, T., Gerush, M., & D’silva, D. (2010). Agile development: Mainstream adoption has changed agility. Forrester Research, 2, 41.

[Wieringa 1995] Wieringa, R. (1995). An introduction to requirements traceability.

[Wieringa 2005] Wieringa, R., & Daneva, M. (2015). Six strategies for generalizing software engineering theories. Science of computer programming, 101, 136-152.

[Woskowski 2012] Woskowski, C. (2012). Applying industrial-strength testing techniques to critical care medical equipment. In Computer Safety, Reliability, and Security(pp. 62-73). Springer Berlin Heidelberg.

[Yin 2002] Yin, R.K. (2002). Case Study Research: Design and Methods. Sage, Thousand Oaks, CA

[Yin 2009] Yin, R. K. (2009). Case Study Research, vol. 5. Sage Publications, Inc., pp. 3-5, 18, 132-133.

[Yuksel 2009] Yüksel, H. M., Tüzün, E., Gelirli, E., Bıyıklı, E., & Baykal, B. (2009). Using continuous integration and automated test techniques for a robust C4ISR system. In Computer and Information Sciences, 2009. ISCIS 2009. 24th International Symposium on (pp. 743-748). IEEE.

245