Software Process Models

 S O FT WA R E
 PROCESS
 P R O C E S S M O D EL S
 Software

instructions that when executed provide desired

features, function, and performance

enable the programs to manipulate information

describes the operation and use of the programs

Thus Software is a product and also a vehicle that

delivers the product to end users

 Software process

A process is a collection of activities, actions, and tasks that are performed

when some work product is to be created.

 An activity has a broad objective
 Requirements gathering

 An action encompasses a set of tasks that produce a major work product

 Communication with customer

 A task focuses on a small well-defined objective

 Make contact with stakeholder via telephone, Discuss requirements and take notes,
Organize notes into a brief written statement of requirements, E-mail to stakeholder for
review and approval
 Process framework

A generic process framework for software engineering

encompasses five activities
 communication,
 planning,
 modeling,
 construction, and
 deployment

This sequence, this flow is applied repeatedly through a

number of project iterations.

 Process flow
Organizes the activities based on sequence and timeline
 A linear process flow
 executes each of the five
framework activities in
sequence
 An iterative process flow
 repeats one or more of the
activities before proceeding
to the next
 An evolutionary process
flow
 executes the activities in a
“circular” manner.
 Each circuit through the five
activities leads to a more
complete version of the
software
 A parallel process flow
 executes one or more
activities in parallel with
other activities
 (e.g., modeling for one aspect
of the software might be
executed in parallel with
construction of another
aspect of the software).
The Waterfall Model
 Incremental Process Models

Objective is to develop a product with basic functionality in first step and

then add additional features in following steps

Every increment is treated as sub project

Every increment is assigned a priority and high priority increment is

released first
At any specified time plan focuses on current increment only

After it passes testing and validation the process moves on to next

increment
Very flexible and easy to test and debug
Incremental Process Model
 When Incremental Process Models used?

When there is a demand for early release of product in the

market.
When resource with required skill set is not available.

When high risks, new technology are involved.

When project has lengthy development schedules.

When problem modules and interfaces are well defined.

 Evolutionary model

Prototyping
 Prototyping types

 Rapid throwaway Prototype

 Once actual requirements are understood the prototype is ignored
and start with clear understanding of user requirements
 Evolutionary prototyping
 Prototype is modified after feedback

 Incremental prototyping
 Develops functional prototypes for divided sub products

 Extreme prototyping
 For web applications
1. Static pages are developed
2. Data processing is simulated
3. Services are implemented
Thank you