The DOI matches its Crossref record; 12 of the 12 references it cites were found in a registry or an index.
Anchoring the software process
Abstract
Software organizations need common milestones to serve as a basis for their software development processes. The author proposes three such milestones, gives an example of their use, and discusses why they are success-critical for software projects. To avoid the problems of the previous model milestones-stakeholder mismatches, gold plating, inflexible point solutions, high risk downstream capabilities, and uncontrolled developments-software projects need a mix of flexibility and discipline. The risk driven content of the LCO, LCA, and IOC milestones let you tailor them to specific software situations and yet they remain general enough to apply to most software projects. And, because they emphasize stakeholder commitment to shared system objectives, they can provide your organization with a collaborative framework for successfully realizing software's most powerful capability: its ability to help people and organizations cope with change.
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
Self-citationSoftware architecture: perspectives on an emerging discipline
Shaw, M., & Garlan, D. (1996) · CERN Document Server (European Organization for Nuclear Research) · Cited by 2,910
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
Managing the development of large software systems: concepts and techniques
Royce, W. W. (1987) · doi:10.5555/41765.41801 · Cited by 1,176
Cost models for future software life cycle processes: COCOMO 2.0
Boehm, B., Clark, B., Horowitz, E., Westland, C., Madachy, R., & Selby, R. (1995) · Annals of Software Engineering · doi:10.1007/bf02249046 · Cited by 648
Self-citationBoehm, B. W., & DeMarco, T. (1997) · IEEE Software · doi:10.1109/ms.1997.589225 · Cited by 591
Self-citationCarroll, J. M. (1997) · Handbook of Human-Computer Interaction · doi:10.1016/b978-044481862-1.50083-2 · Cited by 547
Theory-W software project management principles and examples
BOEHM, B. W., & Ross, R. W. (1989) · IEEE Transactions on Software Engineering · doi:10.1109/32.29489 · Cited by 538
Self-citationSoftware engineering risk analysis and management
(1992) · Computer Standards & Interfaces · doi:10.1016/0920-5489(92)90060-q · Cited by 416
Boehm, B. (1989) · Lecture Notes in Computer Science · doi:10.1007/3-540-51635-2_29 · Cited by 381
Self-citation
Cited by
Does Agile work? — A quantitative analysis of agile project success
Serrador, P., & Pinto, J. K. (2015) · International Journal of Project Management · doi:10.1016/j.ijproman.2015.01.006 · Cited by 844
Management Challenges to Implementing Agile Processes in Traditional Development Organizations
Boehm, B., & Turner, R. (2005) · IEEE Software · doi:10.1109/ms.2005.129 · Cited by 632
Self-citationA view of 20th and 21st century software engineering
Boehm, B. (2006) · Proceedings of the 28th international conference on Software engineering · doi:10.1145/1134285.1134288 · Cited by 510
Self-citationSplitting the organization and integrating the code: Conway's law revisited
Herbsleb, J. D., & Grinter, R. E. (1999) · Proceedings of the 21st international conference on Software engineering · doi:10.1145/302405.302455 · Cited by 425
Using risk to balance agile and plan- driven methods
Boehm, B., & Turner, R. (2003) · Computer · doi:10.1109/mc.2003.1204376 · Cited by 412
Self-citationA cognitive model of innovation
Nightingale, P. (1998) · Research Policy · doi:10.1016/s0048-7333(98)00078-x · Cited by 324
Metadata
- Authors
- Boehm, B.
- Venue
- IEEE Software
- Published
- 1996-07
- Volume
- 13
- Issue
- 4
- Pages
- 73-82
- ISSN
- 0740-7459 (ISSN-L)
- OpenAlex
- W1970925937
- Cited by
- 256
- References
- 12
- FWCI
- 33.50
- 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
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.