The document describes several software process models: the 4 block SDLC model, waterfall model, evolutionary development model, incremental development model, reuse-oriented development model, rapid application development model, and software prototyping models including evolutionary prototyping and throw-away prototyping. It also outlines Boehm's spiral model and notes this as a homework task.

1. Software Process Models

2. Software Process Models
 4 Blocks SDLC ( Software Development Life Cycle )
Model
Design and
SPECIFI- Testing and Maintenance
Development
CATION Validation
January 13, 2012 Made by Utpal Ray 2

3. Software Process Models
 The Classic ‘Waterfall’ Model
Requirement
Analysis and
Definition
System And
Software
Design Coding and
Unit
Testing
Integration and
System
Testing
Operation and
maintenance
January 13, 2012 Made by Utpal Ray 3

4. Software Process Models
 Evolutionary Development Model
SPECS
Initial Version
feedback
OUTLINE
DESCRIPTION Development Intermediate
feedback Versions
Validation FINAL
VERSION
January 13, 2012 Made by Utpal Ray 4

5. Software Process Models
 Incremental Development Model
Assign
Define Outline Design System
Requirements to
Requirement Architecture
Increments
Develop
Validate Integrate Validate
System
Increment Increment System
Increment
January 13, 2012 Made by Utpal Ray 5

6. Software Process Models
 REUSE-Oriented Development Model
( Component based S/W Engineering )
Analysis of the
REQUIREMENT REQUIREMENT
Available
SPECIFICATION MODIFICATION
Components
System Design DEVELOPMENT
SYSTEM
With Reuse AND
VALIDATION
Components INTEGRATION
January 13, 2012 Made by Utpal Ray 6

7. Software Process Models
 Rapid Application Development (RAD) Model
Business
Modeling TEAM #2
Data
Modeling
Process
Modeling
Application
TEAM #1 Generation
Testing
And
Turnover
60 – 90 days
January 13, 2012 Made by Utpal Ray 7

8. Software Process Models
 Characteristics of RAD Model
-Very short Development Cycle (60 to 90 days)
-Component based construction is encouraged
-Requiremet should be well understood to make a
project follow RAD model
-The modularized approach is very essential for success
of RAD
-RAD should not be followed if technological risks are
there
-Sufficient man power should be available to form
multiple RAD team
January 13, 2012 Made by Utpal Ray 8

9. Software Process Models
Software Prototyping
 Software Prototyping Benefits
Requirement Elicitations and Validations
Reducing the misunderstanding between the s/w
developers and the customers
A quick working system is available to demonstrate,
training and testing
Helps to minimize expensive design errors
It is the only way to get a 100% fool-proof system where
User Interface plays a major role
This process can be treated as a part of the specification
process or a process before it.
 Software Prototyping Disadvantages
January 13, 2012 Made by Utpal Ray 9

10. Software Process Models
 Evolutionary Prototyping
Develop Abstract Build Prototype Use Prototype
Specification System System
No
System
Deliver System Adequate
Yes ?
January 13, 2012 Made by Utpal Ray 10

11. Software Process Models
 Throw-away Prototyping
OUTLINE DEVELOP EVALUATE SPECIFY
REQUIREMENT PROTOTYPE PROTOTYPE SYSTEM
4 BLOCK SDLC MODEL
OR
Re-usable Component ANY OTHER RELEVENT
MODEL
January 13, 2012 Made by Utpal Ray 11

12. Software Process Models
 HOME TASK
Boehm’s Spiral Model
January 13, 2012 Made by Utpal Ray 12