Synthesizing Continuous Deployment Practices Used in Software Development
The DOI matches its Crossref record; 3 of the 3 references it cites were found in a registry or an index.
Abstract
Continuous deployment speeds up the process of existing agile methods, such as Scrum, and Extreme Programming (XP) through the automatic deployment of software changes to end-users upon passing of automated tests. Continuous deployment has become an emerging software engineering process amongst numerous software companies, such as Facebook, Github, Netflix, and Rally Software. A systematic analysis of software practices used in continuous deployment can facilitate a better understanding of continuous deployment as a software engineering process. Such analysis can also help software practitioners in having a shared vocabulary of practices and in choosing the software practices that they can use to implement continuous deployment. The goal of this paper is to aid software practitioners in implementing continuous deployment through a systematic analysis of software practices that are used by software companies. We studied the continuous deployment practices of 19 software companies by performing a qualitative analysis of Internet artifacts and by conducting follow-up inquiries. In total, we found 11 software practices that are used by 19 software companies. We also found that in terms of use, eight of the 11 software practices are common across 14 software companies. We observe that continuous deployment necessitates the consistent use of sound software engineering practices such as automated testing, automated deployment, and code review.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Expectations, outcomes, and challenges of modern code review
Bacchelli, A., & Bird, C. (2013) · 2013 35th International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2013.6606617 · Cited by 650
Development and Deployment at Facebook
Feitelson, D. G., Frachtenberg, E., & Beck, K. L. (2013) · IEEE Internet Computing · doi:10.1109/mic.2013.25 · Cited by 243
Continuous Delivery? Easy! Just Change Everything (Well, Maybe It Is Not That Easy)
Neely, S., & Stolt, S. (2013) · 2013 Agile Conference · doi:10.1109/agile.2013.17 · Cited by 124
Cited by
Shahin, M., Ali Babar, M., & Zhu, L. (2017) · IEEE Access · doi:10.1109/access.2017.2685629 · Cited by 680
“Method: We used systematic literature review (SLR) method for reviewing the peer-reviewed papers on continuous practices published between 2004 and 1st June 2016.”
MethodChallenges and solutions when adopting DevSecOps: A systematic review
Rajapakse, R. N., Zahedi, M., Babar, M. A., & Shen, H. (2022) · Information and Software Technology · doi:10.1016/j.infsof.2021.106700 · Cited by 235
“Studies state that continuous practices such as CD are closely related with DevOps as a concept [32].”
BackgroundArachchi, S. A. I. B. S., & Perera, I. (2018) · 2018 Moratuwa Engineering Research Conference (MERCon) · doi:10.1109/mercon.2018.8421965 · Cited by 97
Software security in DevOps: synthesizing practitioners' perceptions and practices
Ur Rahman, A. A., & Williams, L. (2016) · Proceedings of the International Workshop on Continuous Software Evolution and Delivery · doi:10.1145/2896941.2896946 · Cited by 86
“[18] investigated the usage frequency of 11 software practices used amongst software companies that implement continuous deployment.”
MethodSelf-citationPrioritization based taxonomy of DevOps security challenges using PROMETHEE
Rafi, S., Yu, W., Akbar, M. A., Alsanad, A., & Gumaei, A. (2020) · IEEE Access · doi:10.1109/access.2020.2998819 · Cited by 50
Metadata
- Authors
- Rahman, A. A. U., Helms, E., Williams, L., & Parnin, C.
- Venue
- 2015 Agile Conference
- Publisher
- IEEE
- Published
- 2015-08
- Pages
- 1-10
- OpenAlex
- W1642473876
- Cited by
- 75
- References
- 3
- FWCI
- 8.48
- Type
- conference paper
- Language
- en
- Open access
- closed
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
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.