skip to main content
10.1145/2591062.2591186acmconferencesArticle/Chapter ViewAbstractPublication PagesicseConference Proceedingsconference-collections
Article

Automated software integration flows in industry: a multiple-case study

Published: 31 May 2014 Publication History

Abstract

There is a steadily increasing interest in the agile practice of continuous integration. Consequently, there is great diversity in how it is interpreted and implemented, and a need to study, document and analyze how automated software integration flows are implemented in the industry today. In this paper we study five separate cases, using a descriptive model developed to address the variation points in continuous integration practice discovered in literature. Each case is discussed and evaluated individually, whereupon six guidelines for the design and implementation of automated software integration are presented. Furthermore, the descriptive model used to document the cases is evaluated and evolved.

References

[1]
Apache Maven Project. http://maven.apache.org. Retrieved July 30, 2013.
[2]
AUTOSAR. http://www.autosar.org. Retrieved July 30, 2013.
[3]
Google trends: continuous integration. http://www.google.com/trends/explore#q= %22continuous%20integration%22. Retrieved July 30, 2013.
[4]
Jenkins CI. http://jenkins-ci.org. Retrieved July 30, 2013.
[5]
Software Center. http://www.software-center.se. Retrieved July 30, 2013.
[6]
O. Beaumont, N. Bonichon, L. Courtès, X. Hanin, and E. Dolstra. Mixed data-parallel scheduling for distributed continuous integration. In 26th International Parallel and Distributed Processing Symposium Workshops & PhD Forum, (Shanghai, China, 2012), pages 91––98, 2012.
[7]
K. Beck. Extreme Programming Explained. Addison-Wesley Professional, Boston, MA, 2000.
[8]
J. Downs, J. Hosking, and B. Plimmer. Status communication in agile software teams: A case study. In Fifth International Conference on Software Engineering Advances, (Nice, France, 2010), pages 82–87, 2010.
[9]
D. Goodman and M. Elbaz. It’s not the pants, it’s the people in the pants. learnings from the gap agile transformation. In Agile Conference 2008, (Toronto, Canada, 2008), pages 112–115, 2008.
[10]
A. Miller. A hundred days of continuous integration. In Agile Conference 2008, (Toronto, Canada, 2008), pages 289–293, 2008.
[11]
J. Rasmusson. Long build trouble shooting guide. In 4th Conference on Extreme Programming and Agile Methods, (Calgary, Canada, 2004), pages 557–574, 2004.
[12]
M. Roberts. Enterprise continuous integration using binary dependencies. In 5th International Conference on Extreme Programming and Agile Processes in Software Engineering, (Garmisch-Partenkirchen, Germany, 2004), pages 194–201, 2004.
[13]
R. O. Rogers. Scaling continuous integration. In 6th International Conference on Extreme Programming and Agile Processes in Software Engineering, (Sheffield, UK, 2005), pages 68–76, 2005.
[14]
D. Stahl and J. Bosch. Experienced benefits of continuous integration in industry software product development: A case study. In The 12th IASTED International Conference on Software Engineering, (Innsbruck, Austria, 2013), pages 736–743, 2013.
[15]
D. Stahl and J. Bosch. Modeling continuous integration practice differences in industry software development. Journal of Systems and Software, 87:48–59, January 2014.
[16]
T. van der Storm. The sisyphus continuous integration system. In 11th European Conference on Software Maintenance and Reengineering, (Amsterdam, Netherlands, 2007), pages 335–336, 2007.
[17]
D. West and T. Grant. Agile development: Mainstream adoption has changed agility. Technical report, Forrester Research, January 2010.

Cited By

View all

Recommendations

Comments

Information & Contributors

Information

Published In

cover image ACM Conferences
ICSE Companion 2014: Companion Proceedings of the 36th International Conference on Software Engineering
May 2014
741 pages
ISBN:9781450327688
DOI:10.1145/2591062
Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

Sponsors

In-Cooperation

  • TCSE: IEEE Computer Society's Tech. Council on Software Engin.

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 31 May 2014

Permissions

Request permissions for this article.

Check for updates

Author Tags

  1. Agile software development
  2. automation
  3. continuous integration
  4. methodologies
  5. software integration

Qualifiers

  • Article

Conference

ICSE '14
Sponsor:

Acceptance Rates

Overall Acceptance Rate 276 of 1,856 submissions, 15%

Upcoming Conference

ICSE 2025

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)21
  • Downloads (Last 6 weeks)1
Reflects downloads up to 30 Jan 2025

Other Metrics

Citations

Cited By

View all

View Options

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Figures

Tables

Media

Share

Share

Share this Publication link

Share on social media