The DOI matches its Crossref record; 5 of the 5 references it cites were found in a registry or an index.
Software development lifecycle models
Abstract
This history column article provides a tour of the main software development life cycle (SDLC) models. (A lifecycle covers all the stages of software from its inception with requirements definition through to fielding and maintenance.) System development lifecycle models have drawn heavily on software and so the two terms can be used interchangeably in terms of SDLC, especially since software development in this respect encompasses software systems development. Because the merits of selecting and using an SDLC vary according to the environment in which software is developed as well as its application, I discuss three broad categories for consideration when analyzing the relative merits of SDLC models. I consider the waterfall model before the other models because it has had a profound effect on software development, and has additionally influenced many SDLC models prevalent today. Thereafter, I consider some of the mainstream models and finish with a discussion of what the future could hold for SDLC models.
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
A spiral model of software development and enhancement
Boehm, B. W. (1988) · Computer · doi:10.1109/2.59 · Cited by 4,972
The Unified Software Development Process
Jacobson, I., Booch, G., & Rumbaugh, J. E. (1999) · CERN Document Server (European Organization for Nuclear Research) · Cited by 3,389
Managing the Development of Large Software Systems (1970)
Royce, W. W. (2021) · Ideas That Created the Future · doi:10.7551/mitpress/12274.003.0035 · Cited by 1,778
The Relationship of System Engineering to the Project Cycle
Forsberg, K., & Mooz, H. (1991) · INCOSE International Symposium · doi:10.1002/j.2334-5837.1991.tb01484.x · Cited by 354
Production of large computer programs
Benington, H. D. (1987) · doi:10.5555/41765.41799 · Cited by 79
Cited by
DeepHunter: a coverage-guided fuzz testing framework for deep neural networks
Xie, X., Ma, L., Juefei-Xu, F., Xue, M., Chen, H., Liu, Y., Zhao, J., Li, B., Yin, J., & See, S. (2019) · Proceedings of the 28th ACM SIGSOFT International Symposium on Software Testing and Analysis · doi:10.1145/3293882.3330579 · Cited by 426
Joslin, R., & Müller, R. (2015) · International Journal of Project Management · doi:10.1016/j.ijproman.2015.03.005 · Cited by 356
Self-collaboration code generation via ChatGPT
Dong, Y., Jiang, X., Jin, Z., & Li, G. (2024) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3672459 · Cited by 256
“The task is defined as T : 𝑥 → 𝑦 .”
Self-collaboration Code Generation via ChatGPT
Dong, Y., Jiang, X., Jin, Z., & Li, G. (2023) · arXiv · doi:10.48550/arxiv.2304.07590 · Cited by 256
Self-Planning Code Generation with Large Language Models
Jiang, X., Dong, Y., Wang, L., Fang, Z., Shang, Q., Li, G., Jin, Z., & Jiao, W. (2024) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3672456 · Cited by 158
“In practice, software development is to give software solutions for real-world problems, and the generation of these solutions requires a planning process to guarantee the quality of coding [9]–[11].”
Method
Metadata
- Authors
- Ruparelia, N. B.
- Venue
- ACM SIGSOFT Software Engineering Notes
- Published
- 2010-05-11
- Volume
- 35
- Issue
- 3
- Pages
- 8-13
- ISSN
- 0163-5948 (ISSN-L)
- OpenAlex
- W2167598051
- Cited by
- 408
- References
- 5
- FWCI
- 29.82
- Type
- journal article
- 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: Software development lifecycle models. https://app.cochat.ai/papers/10.1145/1764810.1764814
- The paper
- Ruparelia, N. B. (2010). Software development lifecycle models. ACM SIGSOFT Software Engineering Notes. https://doi.org/10.1145/1764810.1764814
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.