Scribd
Upload
11 views19 pages

Evolutionary Process Models

Uploaded by

faisal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
11 views19 pages

Evolutionary Process Models

Uploaded by

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

EVOLUTIONARY PROCESS MODELS:

 Evolutionary process models produce with each iteration produce an


increasingly more complete version of the software with every iteration.

 Evolutionary models are iterative.

They are characterized in a manner that enables software engineers to


develop increasingly more complete versions of the software.
We have:

1. Prototyping Model
2. Spiral Model and
3. Concurrent Model
1
Prototyping is more commonly used as a technique that can be
implemented within the context of anyone of the process model.

The prototyping paradigm begins with communication. The software


engineer
and customer meet and define the overall objectives for the software.

Prototyping iteration is planned quickly and modeling occurs.

The quick design leads to the construction of a prototype. The prototype is


deployed and then evaluated by the customer/user.

Iteration occurs as the prototype is tuned to satisfy the needs of the


customer, while at the same time enabling the developer to better
understand what needs to
be done
Advantages:

The prototyping paradigm assists the software engineer and the


customer to better understand what is to be built when requirements are
fuzzy.

The prototype serves as a mechanism for identifying software


requirements..
2. Spiral Model
Planning

Communication

modeling

deployment
Construction
•The spiral model can be adapted to apply throughout the entire life
cycle of an application, from concept development to maintenance.

• Using the spiral model, software is developed in a series of


evolutionary releases.

• During early iterations, the release might be a paper model or


prototype.

• During later iterations, increasingly more complete versions of the


system
 Anchor point milestones- a combination of work products and
conditions that are attained along the path of the spiral- are noted for
each evolutionary pass.

 The first circuit around the spiral might result in the development of
product specification.

 Each pass through the planning region results in adjustments to the


project plan. Cost and schedule are adjusted based on feedback derived
from the customer after delivery.
• The first circuit around the spiral might represent a “concept
development project” which starts at the core of the spiral and
continues for multiple iterations until concept development is complete.

• If the concept is to be developed into an actual product, the process


proceeds outward on the spiral and a “new product development
project” commences.

• Later, a circuit around the spiral might be used to represent a “product


enhancement project.” In essence, the spiral, when characterized in this
way, remains operative until the software is retired.
Advantages:
It provides the potential for rapid development of increasingly more complete
versions of the software.

The spiral model is a realistic approach to the development of large-scale


systems and software.

Draw Backs:

The spiral model is not a panacea.

It may be difficult to convince customers that the evolutionary approach is


controllable.

It demands considerable risk assessment expertise and relies on this expertise


for success.

If a major risk is not uncovered and managed, problems will undoubtedly


occur
3. Concurrent model
The concurrent development model, sometimes called concurrent
engineering.

It allows a software team to represent iterative and concurrent


elements of any of the process model.

For example, the modeling activity defined for the spiral model is
accomplished by invoking one or more of the software engineering
actions: prototyping, analysis, and design.

The activity— modeling—may be in any one of the states noted at


any given time
The Unified Process divides the project into four
phases:

• Inception
• Elaboration
• Construction
• Transition
• Production
Inception phase

Inception is the smallest phase in the project, and ideally it should


be quite short.

If the Inception Phase is long then it may be an indication of


excessive up-front specification, which is contrary to the spirit of
the Unified Process.

The following are typical goals for the Inception phase:


• Establish
• Prepare a preliminary project schedule and cost estimate
• Feasibility
• Buy or develop it
Elaboration phase

During the Elaboration phase, the project team is expected to


capture a healthy majority of the system requirements.

However, the primary goals of Elaboration are to address


known risk factors and to establish and validate the system
architecture.
Construction phase

• Construction is the largest phase of the project. In this phase, the


remainder of the system is built on the foundation laid in
Elaboration.

• System features are implemented in a series of short, time-boxed


iterations.

• Each iteration results in an executable release of the software. It is


customary to write full-text use cases during the construction phase
and each one becomes the start of a new iteration.

• Iterative implementation for the lower risks and easier elements


are done. The final Construction phase deliverable is software ready
to be deployed in the Transition phase.
Transition phase

• The final project phase is Transition. In this phase the system is


deployed to the target users.

• Feedback received from an initial release (or initial releases) may


result in further refinements to be incorporated over the course of
several Transition phase iterations.

• The Transition phase also includes system conversions and user


training.
Thank you..

You might also like