0% found this document useful (0 votes)
36 views6 pages

Write Short Notes On Various Types of Software Process Models

The document summarizes various software process models including waterfall, V-model, incremental, RAD, agile, iterative, spiral, and prototype models. It provides details on each model such as waterfall involving sequential phases, V-model extending waterfall with testing phases, incremental adding functionality incrementally, RAD emphasizing user feedback, iterative focusing on initial features then adding complexity, spiral handling risks in loops, and agile empowering teams through small cycles.

Uploaded by

anurag
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
36 views6 pages

Write Short Notes On Various Types of Software Process Models

The document summarizes various software process models including waterfall, V-model, incremental, RAD, agile, iterative, spiral, and prototype models. It provides details on each model such as waterfall involving sequential phases, V-model extending waterfall with testing phases, incremental adding functionality incrementally, RAD emphasizing user feedback, iterative focusing on initial features then adding complexity, spiral handling risks in loops, and agile empowering teams through small cycles.

Uploaded by

anurag
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

ASSIGNMENT-3

OOSE LAB C06 C1G1

SUBMITTED BY: ANURAG DUDPURI


ROLL NO: 2K18/CE/023
EMAIL-ID: [email protected]

Write short notes on various types of


software process models
Various types of software process models are:
 Waterfall model
 V model
 Incremental model
 RAD model
 Agile model
 Iterative model
 Spiral model
 Prototype model

Waterfall Model
 The waterfall model is a breakdown of project activities into linear sequential
phases, where each phase depends on the deliverables of the previous one and
corresponds to a specialisation of tasks.
 The approach is typical for certain areas of engineering design.
V Model
 The V-model represents a development process that may be considered an
extension of the waterfall model and is an example of the more general V-model.
 Instead of moving down in a linear way, the process steps are bent upwards after
the coding phase, to form the typical V shape.
 The V-Model demonstrates the relationships between each phase of the
development life cycle and its associated phase of testing.
 The horizontal and vertical axes represent time or project completeness (left-to-
right) and level of abstraction (coarsest-grain abstraction uppermost), respectively.
Incremental model
 The incremental build model is a method of software development where the
model is designed, implemented and tested incrementally (a little more is added
each time) until the product is finished.
 It involves both development and maintenance. The product is defined as finished
when it satisfies all of its requirements.
 Each iteration passes through the requirements, design, coding and testing phases.
And each subsequent release of the system adds function to the previous release
until all designed functionally has been implemented.

Iterative Model
 An iterative life cycle model does not attempt to start with a full specification of
requirements by first focusing on an initial, simplified set user features, which then
progressively gains more complexity and a broader set of features until the
targeted system is complete.
 In other words, the iterative approach begins by specifying and implementing just
part of the software, which can then be reviewed and prioritized in order to
identify further requirements.
 This iterative process is then repeated by delivering a new version of the software
for each iteration.
RAD model
 Rapid application development was a response to plan-driven waterfall processes,
developed in the 1970s and 1980s, Rapid application development (RAD) is often
referred as the adaptive software development.
 RAD is an incremental prototyping approach to software development that end
users can produce better feedback when examining a live system, as opposed to
working strictly with documentation. It puts less emphasis on planning and more
emphasis on an adaptive process.
 RAD may resulted in a lower level of rejection when the application is placed into
production, but this success most often comes at the expense of a dramatic
overruns in project costs and schedule.
 RAD approach is especially well suited for developing software that is driven by
user interface requirements. Thus, some GUI builders are often called rapid
application development tools.

Spiral model
 The spiral model, first described by Barry Boehm in 1986, is a risk-driven software
development process model which was introduced for dealing with the
shortcomings in the traditional waterfall model.
 A spiral model looks like a spiral with many loops. The exact number of loops of the
spiral is unknown and can vary from project to project.
 This model supports risk handling, and the project is delivered in loops. Each loop
of the spiral is called a Phase of the software development process.
 The initial phase of the spiral model in the early stages of Waterfall Life Cycle that
is needed to develop a software product. The exact number of phases needed to
develop the product can be varied by the project manager depending upon the
project risks.

Agile model
 Agile is an umbrella term for a set of methods and practices based on the values
and principles expressed in the Agile Manifesto that is a way of thinking that
enables teams and businesses to innovate, quickly respond to changing demand,
while mitigating risk.
 The Agile movement proposes alternatives to traditional project management.
 The primary goal of being Agile is empowered the development team the ability to
create and respond to change in order to succeed in an uncertain and turbulent
environment.
 Agile software development approach is typically operated in rapid and small
cycles.
 This results in more frequent incremental releases with each release building on
previous functionality. Thorough testing is done to ensure that software quality is
maintained.
 Organizations can be agile using many of the available frameworks available such
as Scrum, Kanban, Lean, Extreme Programming (XP) and etc.

You might also like