CoChat
Sign Up
Cited by 212Software Engineering Techniques and PracticesAdvanced Software Engineering MethodologiesSoftware System Performance and Reliability

The DOI matches its Crossref record; 60 of the 64 references it cites were found in a registry or an index.

Continuous software engineering and beyond: trends and challenges

Open access
Fitzgerald, Brian, Stol, Klaas-Jan·2014·Proceedings of the 1st International Workshop on Rapid Continuous Software Engineering
DOI 10.1145/2593812.2593813
Open this paper in CoChat — free account

Abstract

Throughout its short history, software development has been characterized by harmful disconnects between important activities e.g., planning, development and implementation. The problem is further exacerbated by the episodic and infrequent performance of activities such as planning, testing, integration and releases. Several emerging phenomena reflect attempts to address these problems. For example, the Enterprise Agile concept has emerged as a recognition that the benefits of agile software development will be sub- optimal if not complemented by an agile approach in related organizational function such as finance and HR. Continuous integration is a practice which has emerged to eliminate discontinuities between development and deployment. In a similar vein, the recent emphasis on DevOps recognizes that the integration between software development and its operational deployment needs to be a continuous one. We argue a similar continuity is required between business strategy and development, BizDev being the term we coin for this. These disconnects are even more problematic given the need for reliability and resilience in the complex and data-intensive systems being developed today. Drawing on the lean concept of flow, we identify a number of continuous activities which are important for software development in today’s context. These activities include continuous planning, continuous integration, continuous deployment, continuous delivery, continuous verification, continuous testing, continuous compliance,continuous security, continuous use, continuous trust, continuous run-time monitoring, continuous improvement (both process and product), all underpinned by continuous innovation. We use the umbrella term, ``Continuous *'' (continuous star) to identify this family of continuous activities.

Overview

Integrity signals

Registry

Crossref · 10.1145/2593812.2593813

Cites

60 of 60 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

We couldn’t retrieve this paper’s full text, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Citations

Cites

Flagged first, then by citations

Show all 64 references

4 of the 64 references couldn’t be matched to a known paper.

Research works printed but not linked: 15

  1. S. Ambler . When does(n’t) agile modeling make sense , 2001 . www.agilemodeling.com/essays/whenDoesAMWork.htm. S. Ambler. When does(n’t) agile modeling make sense, 2001. www.agilemodeling.com/essays/whenDoesAMWork.htm.
  2. CA Technologies . The innovation imperative: Why it needs to lead now , 2012 . www.ca.com/us/ /media/Files/Presentations/theinnovation-imperative-external-presentation-final.pdf. CA Technologies. The innovation imperative: Why it needs to lead now, 2012. www.ca.com/us/ /media/Files/Presentations/theinnovation-imperative-external-presentation-final.pdf.
  3. 10.5555/938437.938796 · DOI
  4. P. Debois . Devops days ghent , 2009 . http://www.devopsdays.org/events/2009-ghent/. P. Debois. Devops days ghent, 2009. http://www.devopsdays.org/events/2009-ghent/.
  5. T. Fitz . Continuous deployment at IMVU: Doing the impossible fifty times a day , 2009 . http://timothyfitz.com/2009/02/10/continuousdeployment-atimvu-doing-the-impossible-fifty-times-aday/. T. Fitz. Continuous deployment at IMVU: Doing the impossible fifty times a day, 2009. http://timothyfitz.com/2009/02/10/continuousdeployment-atimvu-doing-the-impossible-fifty-times-aday/.
  6. L. Gebauer , M. Sollner , and J. Leimeister . Towards understanding the formation of continuous it use . In 34th Int’l Conf. Information Systems , 2013 . L. Gebauer, M. Sollner, and J. Leimeister. Towards understanding the formation of continuous it use. In 34th Int’l Conf. Information Systems, 2013.
  7. J. Humble . Continuous delivery vs continuous deployment , 2010 . http://continuousdelivery.com/2010/08/continuousdelivery-vs-continuous-deployment/. J. Humble. Continuous delivery vs continuous deployment, 2010. http://continuousdelivery.com/2010/08/continuousdelivery-vs-continuous-deployment/.
  8. 10.5555/520792.823969 · DOI
  9. J. Krafcik . Triumph of the lean production system . 1988 . J. Krafcik. Triumph of the lean production system. 1988.
  10. F. Lacoste . Killing the gatekeeper . In Agile Conf. , 2009 . F. Lacoste. Killing the gatekeeper. In Agile Conf., 2009.
  11. M. McHugh , F. Mc Caffery , B. Fitzgerald , K. Stol , V. Casey , and G. Coady . Balancing agility and discipline in a medical device software organization . In 13th International SPICE Conference , 2013 . M. McHugh, F. Mc Caffery, B. Fitzgerald, K. Stol, V. Casey, and G. Coady. Balancing agility and discipline in a medical device software organization. In 13th International SPICE Conference, 2013.
  12. M. Merkow and L. Raghavan . An ecosystem for continuously secure application software. CrossTalk , March/April , 2011 . M. Merkow and L. Raghavan. An ecosystem for continuously secure application software. CrossTalk, March/April, 2011.
  13. D. G. Reinertsen . The Principles of Product Development Flow . Celeritas Publishing , 2009 . D. G. Reinertsen. The Principles of Product Development Flow. Celeritas Publishing, 2009.
  14. 10.5555/951952.952340 · DOI
  15. VersionOne. 7th annual state of agile survey: The state of agile development , 2012 . VersionOne. 7th annual state of agile survey: The state of agile development, 2012.

Cited by

Sorted by citations

Items 201–212 of 212

Related

See all

Metadata

Authors
Fitzgerald, B., & Stol, K.-J.
Affiliations
University of Limerick (IE)
ORCID
Venue
Proceedings of the 1st International Workshop on Rapid Continuous Software Engineering
Publisher
ACM
Published
2014-06-03
Pages
1-9
DOI
10.1145/2593812.2593813
OpenAlex
W2128412750
Cited by
212
References
64
Citations by year
2026: 5 · 2025: 19 · 2024: 13 · 2023: 23 · 2022: 15 · 2021: 19 · 2020: 16 · 2019: 19 · 2018: 23 · 2017: 15 · 2016: 21 · 2015: 20 · 2014: 4
FWCI
17.06
Type
conference paper
Language
en
Open access
Licence
Locations
  • Arrow@dit (Dublin Institute of Technology) (acceptedVersion)
  • University of Limerick Institutional Repository (University of Limerick) (acceptedVersion, cc-by-nc-sa)
  • University of Limerick Institutional Repository (University of Limerick) (submittedVersion, cc-by-nc-sa)
  • University of Limerick Institutional Repository (University of Limerick)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
  • Physical Sciences › Computer Science › Computer Networks and Communications › Software System Performance and Reliability
Keywords
continuous software engineering, continuous integration, DevOps, continuous delivery, continuous deployment, continuous testing, continuous verification, continuous compliance, continuous improvement, continuous innovation, agile software development

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review