Lecture no.

3
Software Processes

1
Recap
 Software process model
 Different types of process models and when
they may be used
 Waterfall
 Incremental

2
Topics covered
 Software process models
 Prototype
 Rapid Application Development (RAD)
 Spiral Model

3
Prototype Model

4
Prototyping

“It is easier to tell what you don’t like about

an existing system than to describe what you
would like in an imaginary one”

A.M. Jenkins, 1983

The Prototyping Process

Identify
Initial
Requirements

Develop Use and

Iterate
System Evaluate

Document and Install

Prototyping Examples

 Skteches and diagram

 2D/3D Print
 Physical model
 Wireframes
 Video prototype
Prototyping Advantages

 Improved system usability

 Closer match to the system needed
 Reduced overall development effort (?)
Prototyping Disadvantages
 This model is costly.
 It has poor documentation because of
continuously changing customer
requirements.
 Customers sometimes demand the actual
product to be delivered soon after seeing an
early prototype.
Choice
Life Cycle Prototype
 Pre specification  Pre specification
possible difficult
 Changes expensive  Quick tools work
 Good project  Communications gap
communication  Animated model
 Static model OK needed
 Rigorous approach  Rigor after
useful requirements
 Iteration unacceptable  Iteration accepted
Rapid Application
Development (RAD)

11
RAD Model
 In RAD model, the components or functions are
developed in parallel as if they were mini projects.
 The developments are time boxed, delivered and then
assembled into a working prototype.
 This can quickly give the customer something to see and
use and to provide feedback regarding the delivery and
their requirements.
Rapid Application Development Model
RAD Model: Define
Requirements
At the very beginning, rapid application
development sets itself apart from traditional
software development models.
It doesn’t require you to sit with end users and get
a detailed list of specifications; instead, it asks for
a broad requirement.
RAD Model: Prototype
This is where the actual development takes place.
Instead of following a rigid set of requirements,
developers create prototypes with different
features and functions as fast as they can.
These prototypes are then shown to the clients
who decide what they like and what they don’t.
RAD Model: Construction
The construction stage is a crucial stage of
development. Engineers and developers work
tirelessly to flesh out a working system from a
working model.
Feedback and reviews are crucial at this stage and
most bugs, issues, and alterations are addressed
during this stage.
RAD Model: Cutover
The final stage of RAD involves deploying the
built system into a live production environment.
The deployment phase involves intensive scale
testing, technical documentation, issue tracking,
final customizations, and system simulation.
RAD Model: Advantages
Reduced development time.
Increases reusability of components
Quick initial reviews occur
Encourages customer feedback
RAD Model: Disadvantages
Only system that can be modularized can be built
using RAD
Requires highly skilled developers/designers.
Inapplicable to cheaper projects as cost of modeling
and automated code generation is very high.
RAD Model: When to use
RAD SDLC model should be chosen only if
resources with high business knowledge are
available and there is a need to produce the system
in a short span of time (2-3 months).
Spiral Model

21
Spiral Model:
The spiral model is similar to the incremental model,
with more emphasis placed on risk analysis.
The spiral model has four phases: Planning, Risk
Analysis, Engineering and Evaluation.
Spiral Model:
Spiral Model:
• Phases begin in the quadrant dedicated to the
identification and understanding of requirements. The
overall goal of the phase should be determined and
all objectives should be elaborated and analyzed. It is
important to also identify alternative solutions in case
the attempted version fails to perform.
Spiral Model:
• Next, risk analysis should be performed on all
possible solutions in order to find any faults or
vulnerabilities -- such as running over the budget or
areas within the software that could be open to cyber
attacks. Each risk should then be resolved using the
most efficient strategy.
Spiral Model:
• In the next quadrant, the prototype is built and tested.
This step includes: architectural design, design of
modules, physical product design and the final
design. It takes the proposal that has been created in
the first two quadrants and turns it into software that
can be utilized.
Spiral Model:
• Finally, in the fourth quadrant, the test results of the
newest version are evaluated.
• This analysis allows programmers to stop and
understand what worked and didn’t work before
progressing with a new build.
• At the end of this quadrant, planning for the next
phase begins and the cycle repeats.
• At the end of the whole spiral, the software is finally
deployed in its respective market.
 Spiral Model:

Ref: https://www.javatpoint.com/spiral-model
Spiral Model Examples:
• Microsoft used it to develop early versions of
Windows.
• The Gantt chart software was made using
the model as well.
• Thus, there are no surprise here — big, high
risk projects, which are also aimed at a wide
audience, choose Spiral Model.
Spiral Model Examples:
• Game development is another industry that
uses the Spiral model.
Spiral Model Advantages:
High amount of risk analysis hence, avoidance of
Risk is enhanced.
Good for large and mission-critical projects.
Strong approval and documentation control.
Additional Functionality can be added at a later
date.
Spiral Model Disadvantages:
Can be a costly model to use.
Risk analysis requires highly specific expertise.
Project’s success is highly dependent on the risk
analysis phase.
Doesn’t work well for smaller projects.
Spiral Model :When to use
When costs and risk evaluation is important
For medium to high-risk projects
Users are unsure of their needs
Requirements are complex
Significant changes are expected (research and
exploration)
The End.