A spiral model of software development and enhancement

@article{Boehm1988ASM,
  title={A spiral model of software development and enhancement},
  author={Barry W. Boehm},
  journal={Computer},
  year={1988},
  volume={21},
  pages={61-72}
}
  • B. Boehm
  • Published 1 August 1986
  • Computer Science
  • Computer
A short description is given of software process models and the issues they address. An outline is given of the process steps involved in the spiral model, an evolving risk-driven approach that provides a framework for guiding the software process, and its application to a software project is shown. A summary is given of the primary advantages and implications involved in using the spiral model and the primary difficulties in using it at its current incomplete level of elaboration.<<ETX>> 

Figures and Tables from this paper

REVIEW OF THE SPIRAL MODEL AND ITS APPLICATIONS
TLDR
The spiral model is discussed and its application in various scenarios such as website development, where it is needed for eliciting the user’s requirements is discussed.
Proposed Software Development Model for Small Organization and Its Explanation
TLDR
A new software development model for small organization is proposed that can elicit the software requirement and also compute the functionality and risk in each and every phase of the software development.
A Survey of Boehm's Work on the Spiral Models and COCOMO II—Towards Software Development Process Quality Improvement
  • P. Oriogun
  • Computer Science
    Software Quality Journal
  • 2004
TLDR
This paper investigates the Spiral Model (Sommerville 1997) with particular reference to recent enhancements to it, examines the interaction of COCOMO II within the WinWin framework, and reports on a case study using the Win Win Spiral Model to develop software.
An iterative-cyclic software process model
  • G.W.M. Rauterberg
  • Computer Science
    Proceedings Fourth International Conference on Software Engineering and Knowledge Engineering
  • 1992
TLDR
The relationship between several different kinds of local optimisation cycles with known techniques for user participation is discussed and integrated into a general concept of participatory software development.
A Study of Software Development Models for Small Organisations
TLDR
A key component of any software development process is the lifecycle model on which the process is based, and this document explains how this model is changed over time.
Weaving the Software Development Process Between Requirements and Architectures
TLDR
The paper suggests that the use of various kinds of patterns – of requirements, architectures, and designs – may provide a way to increase software development productivity and stakeholder satisfaction in this setting.
Five Models of Software Development Engineering
TLDR
The main objective of this research is to represent different models of software development and to understand and show the features and defects of each model.
Common Meta-Model for a Living Software Development Processes
TLDR
Empirical studies and research results have shown that applying a well defined organization-wide standardized software development process has profound influence on the magic triangle of time, costs, and quality.
A collaborative spiral software process model based on Theory W
  • B. Boehm, P. Bose
  • Computer Science
    Proceedings of the Third International Conference on the Software Process. Applying the Software Process
  • 1994
TLDR
An extension of the spiral model, called the Next Generation Process Model (NGPM), is presented, which uses the Theory W(win-win) approach (Boehm-Ross, 1989) to converge on a system's next-level objectives, constraints, and alternatives.
Role of software process models in enterprise system development
TLDR
This research paper examines various software process models and their impact on the overall software development life cycle of enterprise wide application development.
...
...

References

SHOWING 1-10 OF 67 REFERENCES
A Programming Process Architecture
TLDR
The Programming Process Architecture is a framework describing required activities for an operational process that can be used to develop system or application software, and requires explicit entry criteria, validation, and exit criteria for each task in the process.
A hierarchical spiral model for the software process
TLDR
The model is particularly interesting to me, since it seems to be highly consistent with some of the basic ideas of the PIOCO model for the information systems (IS) design process and also with its application to the development of embedded software.
Software processes are software too
The major theme of this meeting is the exploration of the importance of process as a vehicle for improving both the quality of software products and the way in which we develop and evolve them. In
Applying process programming to the spiral model
TLDR
The Spiral Model provides a candidate approach to determining the requirements, architecture, and design of a software process by determining which alternative process architecture minimizes the risk of not meeting the system objectives within the system constraints.
The software process and software environments (panel session)
TLDR
This panel discussion springs from a three-day workshop on the software process and software environments that was held in March 1985 and it is intended to convey some of what was discussed and to precipitate discussion of some of the issues that arose during the workshop deliberations.
Applying process programming to the model
The primary thesis of this position paper is that process programming is analogous to programming in an key respect not previously emphasized: that it will proceed more effectively if preceded by a
A Software Development Environment for Improving Productivity
TLDR
The article describes the steps that led to the creation of the software productivity project and its components and summarized the requirements analyses on which the SPS was based.
Software Technology in the 1990's: Using a New Paradigm
TLDR
There is a clear need to investigate a software paradigm based on automation, which augments the effectiveness of the costly and limited supply of people producing and maintaining software, and the existing software paradigm is not a good candidate.
Principles of software engineering management
TLDR
This most recent book of Mr. Gilb's may be destined to become part of APL's folklore; if it were to adopt these methods in a similarly serious-minded vein the authors might easily discover a lot about ourselves and just possibly find a new way of getting their message into wider environments.
Software Engineering Economics
  • B. Boehm
  • Computer Science, Economics
    IEEE Transactions on Software Engineering
  • 1984
TLDR
The field of software cost estimation is surveyed, including the major estimation techniques available, the state of the art in algorithmic cost models, and the outstanding research issues inSoftware cost estimation.
...
...