Which type of nature does spiral model define?
Answers
Answered by
0
Spiral model (Boehm, 2000). A number of misconceptions stem from oversimplifications in this widely circulated diagram (there are some errors in this diagram).[1]
The spiral model is a risk-driven process model generator for software projects. Based on the unique risk patterns of a given project, the spiral model guides a team to adopt elements of one or more process models, such as incremental, waterfall, or evolutionary prototyping.
This model was first described by Barry Boehm in his 1986 paper "A Spiral Model of Software Development and Enhancement".[2]In 1988 Boehm published a similar paper[3] to a wider audience. These papers introduce a diagram that has been reproduced in many subsequent publications discussing the spiral model.
History
These early papers use the term "process model" to refer to the spiral model as well as to incremental, waterfall, prototyping, and other approaches. However, the spiral model's characteristic risk-driven blending of other process models' features is already present:
[R]isk-driven subsetting of the spiral model steps allows the model to accommodate any appropriate mixture of a specification-oriented, prototype-oriented, simulation-oriented, automatic transformation-oriented, or other approach to software development.[3]
In later publications,[1] Boehm describes the spiral model as a "process model generator", where choices based on a project's risks generate an appropriate process model for the project. Thus, the incremental, waterfall, prototyping, and other process models are special cases of the spiral model that fit the risk patterns of certain projects.
Boehm also identifies a number of misconceptions arising from oversimplifications in the original spiral model diagram. He says the most dangerous of these misconceptions are:
that the spiral is simply a sequence of waterfall increments;that all project activities follow a single spiral sequence; andthat every activity in the diagram must be performed, and in the order shown.
While these misconceptions may fit the risk patterns of a few projects, they are not true for most projects.
In a National Research Council report[4] this model was extended to include risks related to human users.
To better distinguish them from "hazardous spiral look-alikes", Boehm lists six characteristics common to all authentic applications of the spiral model.[citation needed]
The spiral model is a risk-driven process model generator for software projects. Based on the unique risk patterns of a given project, the spiral model guides a team to adopt elements of one or more process models, such as incremental, waterfall, or evolutionary prototyping.
This model was first described by Barry Boehm in his 1986 paper "A Spiral Model of Software Development and Enhancement".[2]In 1988 Boehm published a similar paper[3] to a wider audience. These papers introduce a diagram that has been reproduced in many subsequent publications discussing the spiral model.
History
These early papers use the term "process model" to refer to the spiral model as well as to incremental, waterfall, prototyping, and other approaches. However, the spiral model's characteristic risk-driven blending of other process models' features is already present:
[R]isk-driven subsetting of the spiral model steps allows the model to accommodate any appropriate mixture of a specification-oriented, prototype-oriented, simulation-oriented, automatic transformation-oriented, or other approach to software development.[3]
In later publications,[1] Boehm describes the spiral model as a "process model generator", where choices based on a project's risks generate an appropriate process model for the project. Thus, the incremental, waterfall, prototyping, and other process models are special cases of the spiral model that fit the risk patterns of certain projects.
Boehm also identifies a number of misconceptions arising from oversimplifications in the original spiral model diagram. He says the most dangerous of these misconceptions are:
that the spiral is simply a sequence of waterfall increments;that all project activities follow a single spiral sequence; andthat every activity in the diagram must be performed, and in the order shown.
While these misconceptions may fit the risk patterns of a few projects, they are not true for most projects.
In a National Research Council report[4] this model was extended to include risks related to human users.
To better distinguish them from "hazardous spiral look-alikes", Boehm lists six characteristics common to all authentic applications of the spiral model.[citation needed]
Attachments:
Similar questions