Towards Architecting for Continuous Delivery
The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Abstract
Continuous Delivery (CD) has emerged as an auspicious software development discipline, with the promise of providing organizations the capability to release valuable software continuously to customers. Our organization has been implementing CD for the last two years. Thus far, we have moved 22 software applications to CD. I observed that CD has created a new context for architecting these applications. In this paper, I will try to characterize such a context of CD, explain why we need to architect for CD, describe the implications of architecting for CD, and discuss the challenges this new context creates. This information can provide insights to other practitioners for architecting their software applications, and provide researchers with input for developing their research agendas to further study this increasingly important topic.
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
Continuous software engineering and beyond: trends and challenges
Fitzgerald, B., & Stol, K.-J. (2014) · Proceedings of the 1st International Workshop on Rapid Continuous Software Engineering · doi:10.1145/2593812.2593813 · Cited by 212
Research works printed but not linked: 6
- 10.1109/MS.2012.174 · DOI
- 10.1109/DSN.2014.104 · DOI
- bass, 2015, DevOps A Software Architect's Perspective
- bass, 2003, Software Architecture in Practice
- humble, 2010, Continuous Delivery: Reliable Software Releases through Build, Test and Deployment Automation Addison-Wesley Professional
- 10.1109/MS.2015.27 · DOI · Paper page
Cited by
Shahin, M., Ali Babar, M., & Zhu, L. (2017) · IEEE Access · doi:10.1109/access.2017.2685629 · Cited by 680
“Therefore, the architecting phase should be considered as one of the most important phases for appropriately adopting and implementing continuous practices [56].”
BackgroundBolscher, R., & Daneva, M. (2019) · Proceedings of the 14th International Conference on Software Technologies · doi:10.5220/0007837000270039 · Cited by 28
“Chen (2015b) also discusses modifiability as one of the ASRs.”
BackgroundInfluentialBhanushali, A. (2023) · International Journal of Science and Research (IJSR) · doi:10.21275/sr231021114758 · Cited by 11
Metadata
- Authors
- Chen, L.
- Venue
- 2015 12th Working IEEE/IFIP Conference on Software Architecture
- Publisher
- IEEE
- Published
- 2015-05
- Pages
- 131-134
- OpenAlex
- W1603760080
- Cited by
- 45
- References
- 1
- FWCI
- 5.26
- 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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Towards Architecting for Continuous Delivery. https://app.cochat.ai/papers/10.1109/wicsa.2015.23
- The paper
- Chen, L. (2015). Towards Architecting for Continuous Delivery. 2015 12th Working IEEE/IFIP Conference on Software Architecture. https://doi.org/10.1109/wicsa.2015.23
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.