Continuous software engineering: A roadmap and agenda

Journal of Systems and Software

Volumn 123, Issue , 2017, Pages 176-189

  Fitzgerald, Brian ^a   Stol, Klaas Jan ^a  

^a UNIVERSITY OF LIMERICK   (Ireland)

Author keywords

Continuous software engineering; DevOps; Lean software development

Indexed keywords

INTEGRATION; INTEGRATION TESTING; PLANNING; SOFTWARE ENGINEERING;

BUSINESS STRATEGY; CONTINUOUS INTEGRATIONS; CONTINUOUS SOFTWARE ENGINEERINGS; DATA-INTENSIVE SYSTEMS; DEVOPS; LEAN SOFTWARE DEVELOPMENT; OPERATIONAL DEPLOYMENTS; RESEARCH AGENDA;

SOFTWARE DESIGN;

EID: 84937109068     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.jss.2015.06.063     Document Type: Article

References (118)

1. Ackoff, R., 1994. The learning and legacy of Dr. W. Edwards Deming. Available at: http://www.youtube.com/watch?v=OqEeIG8aPPk (accessed on July 8, 2015).
2. Adams, R.J., Evans, B., Brandt, J., Creating small products at a big company: Adobe's “pipeline” innovation process. Proceedings of CHI’13 Extended Abstracts on Human Factors in Computing Systems. ACM, 2013, 2331–2332.
3. Ågerfalk, P.J., Fitzgerald, B., Stol, K., Not so shore anymore: the new imperatives when sourcing in the age of open. Proceedings of the 23rd European Conference on Information Systems, 2015.
4. Ambler, S., 2001. When does(n't) agile modeling make sense. http://www.agilemodeling.com/essays/whenDoesAMWork.htm (accessed on July 8, 2015).
5. Baresi, L., Ghezzi, C., The disappearing boundary between development-time and run-time. Proceedings of the FSE/SDP Workshop on Future of Software Engineering Research (FoSER’10). ACM, 2010, 17–22.
6. Beck, K., Extreme Programming Explained: Embrace Change, 2000, Addison-Wesley.
7. Bernhart, M., Strobl, S., Mauczka, A., Grechenig, T., Applying continuous code reviews in airport operations software. Proceedings of the 12th International Conference on Quality Software, 2012, 214–219.
8. Bhattacherjee, A., Understanding information systems continuance: an expectation–confirmation model. MIS Q. 25:3 (2001), 351–370.
9. Boehm, B., Get ready for agile methods, with care. IEEE Comput. 35:1 (2002), 64–69.
10. Bogsnes, B., Implementing Beyond Budgeting: Unlocking the Performance Potential, 2008, Wiley.
11. Bogsnes, B., Keynote: beyond budgeting in a lean and agile world. Abrahamsson, P., Marchesi, M., Maurer, F., (eds.) Proceedings of XP 2009, LNBIP 31, 2009, Springer, 5–7.
12. Bosch, J., Building products as innovation experiment systems. Proceedings of the Third International Conference on Software Business (ICSOB), LNBIP, 2012, Springer, 27–39.
13. Bosch, J., Holmström Olsson, H., Björk, J., Ljungblad, J., The early stage software startup development model: a framework for operationalizing lean principles in software startups. Fitzgerald, B., Conboy, K., Power, K., Valerdi, R., Morgan, L., Stol, K., (eds.) Proceedings of the 4th International Conference on Lean Enterprise Software and Systems, 2013, 1–15.
14. CA Technologies, 2012. The innovation imperative: Why it needs to lead now. http://www.ca.com/us/~/media/Files/Presentations/the-innovation-imperative-external-presentation-final.pdf (accessed on July 8, 2015).
15. Chang, T.-F., Danylyzsn, A., Norimatsu, S., Rivera, J., Shepard, D., Lattanze, A., Tomayko, J., “Continuous verification” in mission critical software development. Proceedings of the 30th Hawaii International Conference on System Sciences, 1997, 273–284.
16. Chen, X., Sorenson, P., Willson, J., Continuous SPA: continuous assessing and monitoring software process. Proceedings of the IEEE Congress on Services (SERVICES), 2007, 153–158.
17. Chesbrough, H., Open Innovation: The New Imperative for creating and Profiting from Technology, 2003, Harvard Business School Press.
18. Claps, G.G., Svensson, R.B., Aurum, A., On the journey to continuous deployment: technical and social challenges along the way. Inf. Softw. Technol. 57:1 (2015), 21–31.
19. Cole, R., From continuous improvement to continuous innovation. Qual. Manage. J. 8:4 (2001), 7–21.
20. Conboy, K., Fitzgerald, B., Towards a conceptual framework of agile methods. Extreme Programming and Agile Methods-XP/Agile Universe 2004, LNCS, vol. 3134, 2004, Springer, 105–116.
21. Cordeiro, L., Fischer, B., Marques-Silva, J., Continuous verification of large embedded software using smt-based bounded model checking. Proceedings of the 17th IEEE International Conference and Workshops on Engineering of Computer-Based Systems, 2010, 160–169.
22. Daly, J.L., Pricing for Profitability: Activity-Based Pricing for Competitive Advantage, 2002, Wiley Press.
23. Davis, F., Bagozzi, R., Warshaw, P., User acceptance of computer technology: a comparison of two theoretical models. Management Science 35:8 (1989), 982–1003.
24. Debois, P., 2009. DevOps Days Ghent. http://www.devopsdays.org/events/2009-ghent/ (accessed on July 8, 2015).
25. Debois, P., Devops: a software revolution in the making?. Cutter IT J., 24(8), 2011.
26. Del Rosso, C., Continuous evolution through software architecture evaluation: a case study. J. Softw. Maint. Evol.: Res. Pract. 18:5 (2009), 351–383.
27. Earl, M., Hopwood, A., From management information to information management. Trends in Information Systems, 1980, North-Holland Publishing Co. Amsterdam, The Netherlands, 315–325.
28. Fagerholm, F., Guinea, A.S., Mäenpää, H., Münch, J., Building blocks for continuous experimentation. Tichy, M., Bosch, J., Goedicke, M., Larsson, M., (eds.) Proceedings of the 1st International Workshop on Rapid Continuous Software Engineering (RCoSE). ACM, 2014, 26–35.
29. Feitelson, D., Frachtenberg, E., Beck, K., Development and deployment at facebook. IEEE Internet Comput. 17:4 (2013), 8–17.
30. Feller, J., Fitzgerald, B., Hissam, S., Lakhani, K., Perspectives on Free and Open Source Software, 2005, MIT Press.
31. Fitz, T., 2009. Continuous deployment at IMVU: doing the impossible fifty times a day. http://timothyfitz.com/2009/02/10/continuous-deployment-at-imvu-doing-the-impossible-fifty-times-a-day/ (accessed on July 8, 2015).
32. Fitzgerald, B., Formalized systems development methodologies: a critical perspective. Inf. Syst. J. 6:1 (1996), 3–23.
33. Fitzgerald, B., Hartnett, G., Conboy, K., Customising agile methods to software practices at Intel Shannon. Eur. J. Inf. Syst. 15:2 (2006), 197–210.
34. Fitzgerald, B., Musiał, M., Stol, K., Evidence-based decision making in lean software project management. Proceedings of the 36th International Conference on Software Engineering (ICSE-SEIP). ACM, 2014, 93–102.
35. Fitzgerald, B., Stol, K., Continuous software engineering and beyond: Trends and challenges. Proceedings of the First International Workshop on Rapid and Continuous Software Engineering (RCoSE). ACM, 2014, 1–9.
36. Fitzgerald, B., Stol, K., O'Sullivan, R., O'Brien, D., Scaling agile methods to regulated environments: an industry case study. Proceedings of the 35th International Conference on Software Engineering (ICSE-SEIP), 2013, 863–872.
37. Fowler, M., Refactoring: Improving the Design of Existing Code, 1999, Addison-Wesley.
38. Frow, N., Marginson, D., Ogden, S., “Continuous” budgeting: reconciling budget flexibility with budgetary control. Account., Organ. Soc. 35:4 (2010), 444–461.
39. Gale, A., Morris, P., Pinto, J., (eds.) (Trans.) The Wiley Guide to Project Organisation and Project Management Competencies, 2007, Wiley & Sons, 143–167.
40. Gebauer, L., Sollner, M., Leimeister, J., Towards understanding the formation of continuous IT use. Proceedings of the 34th International Conference on Information Systems, 2013.
41. Gefen, D., Karahanna, E., Straub, D., Trust and tam in online shopping: an integrated model. MIS Q. 27:1 (2003), 51–90.
42. Hamel, G., What Matters Now, 2012, Jossey Bass.
43. Hoehle, H., Huff, S., Goode, S., The role of continuous trust in information systems continuance. J. Comput. Inf. Syst. 52:4 (2012), 1–9.
44. Holmström Olsson, H., Alahyari, H., Bosch, J., Climbing the “stairway to heaven”: a multiple-case study exploring barriers in the transition from agile development towards continuous deployment of software. Proceedings of the 38th EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA), 2012, 392–399.
45. Hope, J., Fraser, R., Beyond budgeting: how managers can break free from the annual performance trap. Proceedings of the Harvard Business Review, 2003.
46. Humble, J., 2010. Continuous delivery vs continuous deployment. http://continuousdelivery.com/2010/08/continuous-delivery-vs-continuous-deployment/ (accessed on July 8, 2015).
47. Humble, J., Farley, D., Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation, 2010, Addison-Wesley.
48. Humble, J., Molesky, J., Why enterprises must adopt devops to enable continuous delivery. Cutter IT J. 24:8 (2011), 6–12.
49. Jansen, A., Bosch, J., Software architecture as a set of architectural design decisions. Proceedings of teh 5th Working IEEE/IFIP Conference on Software Architecture, 2005, 109–120.
50. Järvinen, J., Hamann, D., van Solingen, R., On integrating assessment and measurement: towards continuous assessment of software engineering processes. 6th International Software Metrics Symposium, 1999.
51. Jenkins, J., Velocity culture. Talk at Velocity 2011 Conference, 2011.
52. Kettunen, P., Laanti, M., Combining agile software projects and large-scale organizational agility. Softw. Process: Improv. Pract. 13:2 (2008), 183–193.
53. Khurum, M., Petersen, K., Gorschek, T., Extending value stream mapping through waste definition beyond customer perspective. J. Softw.: Evol. Process 26:12 (2014), 1074–1105.
54. Kim, S., Park, S., Yun, J., Lee, Y., Automated continuous integration of component-based software: an industrial experience. Proceedings of the 23rd IEEE/ACM International Conference on Automated Software Engineering (ASE), 2008, 423–426.
55. Knight, R., Rabideau, G., Chien, S., Engelhardt, B., Sherwood, R., Casper: space exploration through continuous planning. IEEE Intell. Syst. 16:5 (2001), 70–75.
56. Korsaa, M., Johansen, J., Schweigert, T., Vohwinkel, D., Messnarz, R., Nevalainen, R., Biro, M., The people aspects in modern process improvement management approaches. J. Softw.: Evol. Process 25:4 (2013), 381–391.
57. Krafcik, J., Triumph of the lean production system. MIT Sloan Manage. Rev. 30:1 (1988), 41–52.
58. Krasner, H., The ASPIRE approach to continuous software process improvement. Proceedings of the 2nd International Conference on Systems Integration, 1992.
59. Kurapati, N., Manyam, V.S.C., Petersen, K., Agile software development practice adoption survey. Proceedings of the XP 2012, LNBIP 111, 2012, 16–30.
60. Lacoste, F., Killing the gatekeeper: introducing a continuous integration system. Proceedings of the Agile Conference, 2009, 387–392.
61. Larman, C., Basili, V.R., Iterative and incremental developments: a brief history. IEEE Comput. 36:6 (2003), 47–56.
62. Leffingwell, D., Scaling Software Agility: Best Practices for Large Enterprises, 2007, Addison–Wesley.
63. Lehman, M., On understanding laws, evolution, and conservation in the large-program life cycle. J. Syst. Softw. 1 (1980), 213–221.
64. Lehtola, L., Kauppinen, M., Vähäniitty, J., Komssi, M., Linking business and requirements engineering: is solution planning a missing activity in software product companies?. Requir. Eng. 14:2 (2009), 113–128.
65. Liker, J.K., The Toyota Way, 2004, McGraw Hill.
66. Lohan, G., A brief history of budgeting: reflections on beyond budgeting, its link to performance management and its appropriateness for software development. Fitzgerald, B., Conboy, K., Power, K., Valerdi, R., Morgan, L., Stol, K., (eds.) Proceedings of the 4th International Conference on Lean Enterprise Software and Systems, LNBIP, 167, 2013, Springer, 81–105.
67. Maglyas, A., Nikula, U., Smolander, K., Lean solutions to software product management problems. IEEE Softw. 29:5 (2012), 40–46.
68. Marijan, D., Gotlieb, A., Sen, S., Test case prioritization for continuous regression testing: an industrial case study. Proceedings of the 29th IEEE International Conference on Software Maintenance, 2013, 540–543.
69. Maurya, A., Running Lean, 2nd edition, 2012, O'Reilly Media Inc.
70. McHugh, M., Mc Caffery, F., Fitzgerald, B., Stol, K., Casey, V., Coady, G., Balancing agility and discipline in a medical device software organization. Proceedings of the 13th International SPICE Conference, Software Process Improvement and Capability Determination, Communications in Computer and Information Science, 349, 2013, Springer, 199–210.
71. Merkow, M., Raghavan, L., 2011. An ecosystem for continuously secure application software. CrossTalk March/April.
72. Michlmayr, M., Fitzgerald, B., Stol, K., Why and how should open source projects adopt time-based releases?. IEEE Softw. 32:2 (2015), 55–63.
73. Mintzberg, H., The Rise and Fall of Strategy Planning, 1994, Prentice Hall.
74. Morgan, J., Liker, J., The Toyota Product Development System, 2006, Productivity Press.
75. Mujtaba, S., Feldt, R., Petersen, K., Waste and lead time reduction in a software product customization process with value stream maps. Proceedings of the 21st Australian Software Engineering Conference, 2010.
76. Müller, H.A., Wong, K., Tilley, S.R., Understanding software systems using reverse engineering technology. The 62nd Congress of L'Association Canadienne Francaise pour l'Avancement des Sciences Proceedings (ACFAS), 1994, 41–48.
77. Muslu, K., Brun, Y., Meliou, A., Data debugging with continuous testing. Proceedings of the 2013 9th Joint ESEC/FSE Meeting on Foundations of Software Engineering, 2013, 631–634.
78. Myers, K., CPEF: a continuous planning and execution framework. AI Magazine 20:4 (1999), 63–69.
79. Neely, S., Stolt, S., Continuous delivery? easy! just change everything (well, maybe it is not that easy). Proceedings of the Agile Conference, 2013, 121–128.
80. O'Connor, R., Basri, S., The effect of team dynamics on software development process improvement. Int. J. Human Cap. Inf. Technol. Prof. 3 (2012), 13–26.
81. Ohno, T., Toyota Production System: Beyond Large-Scale Production, 1988, CRC Press.
82. Ortiz de Guinea, A., Markus, M., Why break the habit of a lifetime? rethinking the roles of intention, habit, and emotion in continuing information technology use. MIS Q. 33:3 (2009), 433–444.
83. Overby, E., Bharadwaj, A., Sambamurthy, V., A framework for enterprise agility and the enabling role of digital options, business agility and information technology diffusion. Business Agility and Information Technology Diffusion, IFIP International Federation for Information Processing, vol. 180, 2005, Springer, 295–312.
84. Ozden, M., A dynamic planning technique for continuous activities under multiple resource constraints. Manage. Sci. 33:10 (1987), 1333–1347.
85. Papatheocharous, E., Andreou, A.S., Empirical evidence and state of practice of software agile teams. J. Softw.: Evol. Process 26:9 (2014), 855–866.
86. Pavlou, P., Fygenson, M., Understanding and predicting electronic commerce adoption: an extension of the theory of planned behavior. MIS Q. 30:1 (2006), 115–143.
87. Petersen, K., Is lean agile and agile lean? a comparison between two software development paradigms. Modern Software Engineering Concepts and Practices: Advanced Approaches, 2011, IGI Global.
88. Petersen, K., Wohlin, C., The effect of moving from a plan-driven to an incremental software development approach with agile practices: An industrial case study. Empir. Softw. Eng. 15:6 (2010), 654–693.
89. Rajlich, V.T., Bennett, K.H., A staged model for the software life cycle. Computer 33:7 (2000), 66–71.
90. Rautiainen, K., Vuornos, L., Lassenius, C., An experience in combining flexibility and control in a small company?s software product development process. Proceedings of the ACM-IEEE International Symposium on Empirical Software Engineering (ISESE), 2003, 28–37.
91. Reifer, D., Making the Software Business Case, 2002, Addison Wesley.
92. Reifer, D.J., Maurer, F., Erdogmus, H., Scaling agile methods. IEEE Softw. 20:4 (2003), 12–14.
93. Reinertsen, D.G., The Principles of Product Development Flow, 2009, Celeritas Publishing.
94. Riaz, M., Sulayman, M., Naqvi, H., Architectural decay during continuous software evolution and impact of ‘design for change’ on software architecture. Proceedings of the International Conference on Advanced Software Engineering and Its Applications, 2009, 119–126.
95. Ries, E., The Lean Startup: How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses, 2011, Crown Business.
96. Rogers, R., Scaling continuous integration. Extreme Programming and Agile Processes in Software Engineering, LNCS, vol. 3092, 2004, Springer, 68–76.
97. Royce, W.W., Managing the development of large software systems. Proceedings of the 9th international conference on Software Engineering, 1987, 328–338.
98. Ruhe, G., Product Release Planning: Methods, Tools and Applications, 2010, CRC Press.
99. Saff, D., Ernst, M.D., Reducing wasted development time via continuous testing. Proceedings of the 14th International Symposium on Software Reliability Engineering, 2003, 281–292.
100. Shim, J.K., Siegel, J.G., Budgeting Basics and Beyond, 3rd edition, 2008, John Wiley & Sons, Inc.
101. Shingo, S., A Study of the Toyota Production System From an Industrial Engineering Viewpoint, revised Edition, 1989, Productivity Press.
102. Sommerville, I., Software Engineering, 2007, Pearson Educated Ltd.
103. Steiber, A., Alänge, S., A corporate system for continuous innovation: the case of google inc. Eur. J. Innov. Manage. 16:2 (2013), 243–264.
104. Stolberg, S., Enabling agile testing through continuous integration. Proceedings of the Agile Conference, 2009.
105. Ståhl, D., Bosch, J., Modeling continuous integration practice differences in industry software development. J. Syst. Softw. 87:1 (2013), 48–59.
106. Swanson, E.B., The dimensions of maintenance. Proceedings of the 2nd international conference on Software engineering, 1976, 492–497.
107. Swartout, P., Continuous Delivery and DevOps: a QuickStart Guide, 2012, Packt Publishing.
108. Tabib, R., Need 4 speed: leverage new metrics to boost your velocity without compromising on quality. Proceedings AGILE 2013, 2013.
109. Tichy, M., Bosch, J., Goedicke, M., Larsson, M., (eds.) Proceedings of the 1st International Workshop on Rapid Continuous Software Engineering (RCoSE 2014) ACM, 2014.
110. Tushman, M., Anderson, P., O'Reilly, C., Technology cycles, innovation streams, and ambidextrous organizations: organizational renewal through innovation streams and strategic change. Managing Strategic Innovation and Change, 1997, Oxford University Press.
111. Valtierra, C., Muñoz, M., Mejia, J., Characterization of software processes improvement needs in SMEs. Proceedings of the International Conference on Mechatronics, Electronics and Automotive Engineering (ICMEAE), 2013, 223–228.
112. van Hoorn, A., Rohr, M., Hasselbring, W., Waller, J., Ehlers, J., Frey, S., Kieselhorst, D., Continuous monitoring of software services: Design and application of the Kieker framework. Berich Nr. 0921, November 2009, 2009, Christian-Albrechts Universität zu Kiel.
113. Venkatesh, V., Morris, M., Davis, G., Davis, F., User acceptance of information technology: toward a unified view. MIS Q. 27:3 (2003), 425–478.
114. Vodanovich, S., Sundaram, D., Myers, M., Digital natives and ubiquitous information systems. Inf. Syst. Res. 21:4 (2010), 711–723.
115. Wang, X., Conboy, K., Cawley, O., “leagile” software development: an experience report analysis of the application of lean approaches in agile software development. J. Syst. Softw. 85:6 (2012), 1287–1299.
116. Womack, J., Jones, D.T., Lean Thinking: Banish Waste and Create Wealth in Your Corporation, 2003, Productivity Press.
117. Young, M., Conboy, K., Contemporary project portfolio management. Int. J. Proj. Manag. 31:8 (2013), 1089–1100.
118. Zhou, T., An empirical examination of continuance intention of mobile payment services. Decis. Support Syst. 54:2 (2013), 1085–1091.