Prescriptive Process models

Waterfall Model.
Incremental Process Model.
Evolutionary Process Model.
Concurrent model
 Prescriptive Process models

Waterfall Model
» Sometimes called the classic life-cycle.
« It is a systematic, sequential approach to software
development that begins with customer specification
of requirements and progresses through planning,
modelling, construction and deployment.
* The V-model provides a way of visualizing how
verification and validation actions are applied to
earlier engineering work.
 Communication
Planning
Project initiation [ Estimating
Requirement gathering Scheduling \ Modeling
Analysis N\ Construction Deployment
Tracking Code Delivery
Design
Test Support
Feedback

Requirelgents Acceptance
Modeling Testing

Architectur.
Design
Waterfall Model

Problems
* Real projects rarely follow sequential flow.
e [t is often difficult for the customer to state all
requirements explicitly.
* A customer must have patience. A working version
of the program will not be available until late in the
project time span.
* Leads to “blocking states”.
Useful
* Where requirements are fixed and is to proceed to
completion in a linear manner.
 Prescriptive Process models
Incremental Process Model

Combines elements of linear and parallel process

flows.
It delivers a series of releases, called increments that
provide progressively more functionality for the
customer as each is delivered
The first increment is often a core product.
The plan addresses the modification of the core
product to better meet the needs of the customer and
the delivery of additional feature and functionality.
It focuses on the delivery of an operational product
with each increment.
Incremental Process Model
* It is useful when staffing is unavailable for a
complete implementation.
* Increments can be planned to manage
technical risks.
O Communication
O Planning
salnjes) pue Ajljeuoloun) alemyos

Modeling (analysis, design)

@ Construction (code, test)
B Deployment ( delivery, feedback)
Ho Ho
PY ]

DDE-- °
Tomg,
Delivery of 1st Increment
Project calendar Time
Evolutionary Process Model
* Complex systems evolve over a period of time
-Business and product requirements often change as development
proceeds.
- tight market deadlines make completion of a comprehensive software
productimpossible, but a limited version must be introduced to meet
competitive or business pressure
- a set of core product or system requirements is well understood, but the
details of product or system extensions have yet to be defined.
» Evolutionary models are iterative.
* Evolutionary Process Model produce an increasingly
more complete version of the software with each
iteration.
* Specification, development and validation are
interleaved.
 Prescriptive Process models

Evolutionary Process Model

Prototyping
» Spiral Model
 Evolutionary Process Model

Prototyping
+ It assists you and stakeholders to better understand what is to
built when requirements are fuzzy.
Prototyping paradigm
-begins with communication.
- planned quickly and modelling occurs
- quick design focuses on a representation of those aspects of the
software that will be visibleto end users.
» Itserves as a mechanism for identifying software
requirements.
Prototyping Model
Problems
* Overall software quality or long-term maintainability
is not considered.
» As a Software Engineer make implementation
compromises in order to get a prototype working
quickly.
Useful
* The customer get feel for the actual system and
developers get to build something immediately
» Key here is all the stakeholders should agree that the
prototype is built to serve as a mechanism for defining
requirements.
 Evolutionary Process Model
Spiral development
Originally proposed by Barry Boehm.
It couples the iterative nature of prototyping with the
controlled and systematic aspects of water fall model.
Process is represented as a spiral rather than as a
sequence of activities with backtracking.
Each loop in the spiral represents a phase in the
process.
No fixed phases such as specification or design -
loops in the spiral are chosen depending on what is
required.
Risks are explicitly assessed and resolved throughout
the process.
 Spiral model
It is a realistic approach to the development of
large-scale systems and software.
The software evolves as the process progresses, the
developer and customer better understand and react
at each evolutionary level.
It uses prototyping as a risk reduction mechanism.
It demands considerable risk assessment expertise
and realise on this expertise for success.
 Evolutionary development
* Problems
— Do not establish the max. speed of the evolution.
— Systems are often poorly structured,
— Special skills (e.g. in languages for rapid prototyping)
may be required.
— Proj. mgmt. and estimation technique do not fit
completely
» Applicability
— For small or medium-size interactive systems;
— For parts of large systems (e.g. the user interface);
— For short-lifetime systems.
 Concurrent Model
The concurrent development model sometimes called
Concurrent Engineering.
It allows team to represent iterative and concurrent
elements of any of the process models.
All software engineering activities exist concurrently but
reside in different states.
Concurrent modeling defines a series of events that will
trigger transitions from state to state for each of the
activities.
Concurrent modeling is applicable to all types of
software development and provide an accurate picture of
the current state of a project.
 One element of the concurrent
process model
Inactive > . TEHa s/w
State of CH
Modeling Activity
— |

/Y Under
/ Development
N
Awaiting Under
Changes Review

ol - /
gl Baselined
(/ Rev ision
\ J