Good

Morning

Aadikavi Bhanubhakta Campus

BICTE 5th Semester
Presented By: Submitted To:
Rabin Ale , Roll No : 17 Ghan Bahadur Thapa
Sarina Dawadi , Roll No : 21 Date :2079-06-31
Subject : Software Engineering And Project Management
 SOFTWARE
DEVELOPMENT
UNIT -2 PROCESS MODELS
• Waterfall Model
• V - Model
• Incremental Process Model
• RAD Model
• Prototype Model
• Spiral Model
 Waterfall Model:-

• The waterfall Model was the first Process Model to be introduced. It is also referred to as a
linear- sequential life cycle model. It is very simple and easy to use. In a waterfall model, each
phase must be completed before the next phase can begin, and there is no overlapping in the
phases.
• It illustrate the software development process in a linear sequential flow. This model was the
first SDLC Model to be used widely in software engineering to ensure success of the project. In
this model typically the outcome of one phase act as the input for the next phase sequentially.
• Over the years, the industry has seen more popular software development methodologies like
Agile, DevOps etc. However such methodologies have not been able to suit all project
scenarios.
• In order to overcome the challenge associated with such methodologies, software development
process could combine the Agile's interactivity with the step of waterfall process.
The following illustration is a representation of
different phase of the waterfall model:-
Requirement
Analysis
System
Design

Implementation

Testing

Deployment
Waterfall Model:-
Maintenance
 Advantages
• Clearly defined stages. • Easy to arrange tasks.

 Simple and easy to understand and use.

 Easy to manage due to the rigidity of the model.
 Phases are processed and completed one at a time.
 Works well for smaller projects where requirements are very well understood.
 Process and results are well documented.
 • No working software is produced until late during the lifecycle.

• Adjusting scope during the lifecycle can end a project.

• It is difficult to measure progress within stages.

Disadvantages:
• Poor model for long and ongoing projects.

• High amount of risk and uncertainty.

• Not a good model for complex and object-oriented projects.

 V-Model:-
• The V-model is a type of SDLC model where process executes in a sequential manner
in V-shape. It is also known as Verification and Validation model. It is based on the
association of a testing phase for each corresponding development stage.
• The next starts only after completion of the previous phase i.e. for each development
activity, there is a testing activity corresponding to it.
1. Verification:- It involves a static analysis method done without executing code. It is
the process of evaluation of the product development process to find whether
specified requirements meet.
2. Validation:- It involves dynamic analysis method, testing is done by executing a
code. Validation is the process to classify the software after the completion of the
development.
 Acceptance test design Acceptance
Requirement
testing
Analysis
System test design
System testing
System design

Integration test design

Integration
Architecture
testing
design
Unit test design

Module design Unit testing

Coding

V-Model
Design phase:
• Requirement analysis
• System design
• Architecture design
• Module design

Testing phase:
• Unit testing
• Integration testing
• System testing
• Acceptance testing
Advantages:-
1. It is used for smal projects where project requirements are clear.
2. This is a highly disciplined model and Phases are completed one at a
time.
3. Simple and easy to understand and use.
4. It focuses on verification and validation activities.

Disadvantages:-
1. High risk and uncertainty.
2. It is not a good for complex and object-oriented projects.
3. This model does not support iteration of phase.
4. It does not easily handle concurrent events.
 Incremental Process Model:-

• Incremental Model is a process of software development where requirements divided

into multiple standalone modules of the software development cycle. In this model,
each module goes through the requirements, design, implementation, and testing
phases.
• Every subsequent release of the module adds function to the previous release. The
process continues until the complete system achieved.

The various phases of this model are:-

1. Requirement analysis
2. Design & development
3. Testing
4. Implementation
 Incremental model

Build1 Design and Testing Implementation

development

Build2
Design and
Requirements Testing Implementation
development

Build3
Design and Testing Implementation
development
 Advantages:-
 Errors are easy to be recognized.
 Easier to test and debug.
 More flexible
 Simple to manage risk because it handled during its iteration.
 The client gets important functionality early.
 Disadvantages:-
 Need for good panning.
 Total cost is high.
 Well defined module interfaces are needed.
 RAD MODEL

Rapid Application Development model is a type of RAD emphasizes on extremely short

incremental model,where the components or development cycle.(60 -90 days )
functions are developed in parallel as if they were
mini projects.
 RAD MODEL
Team 1 Team 2 Team 3
Business Business
Business
Modeling Modeling
Modeling
Data Data
Data Modeling Modeling
Modeling
Process Process
Process Modeling Modeling
Modeling Application
Application
Generation Generation
Application
Generation Testing &
Testing &
Turnover
Turnover
Testing &
Turnover

60 - 90 Days
 Advantages:-
1. Reduced development time.

2. Increases reusability of components.

3. Quick initial reviews occur.

4. Encourages customer feedback.

Disadvantages:-
5. Requires highly skilled developers/designers.

6. High dependency on modelling skills.

7. Needs strong team collaboration.

 (Throw Away Model)
Prototype

Prototyping Model is a software development model Whenever the customer is new to the
in which prototype is built, tested, and reworked until software industry or when he doesn't know
an acceptable prototype is achieved. It also creates how to give the requirements to the
base to produce the final system or software. It works company.
best in scenarios where the project's requirements are
not known in detail When the developers are new to the
domain.
 (Throw Away Model)
Prototype
Requirement Gathering

Quick Design

Prototype Development Refining Suggestion

incorprateing Build Prototype

Customer Evaluation

Design implement Test

Iterative Development
Maintain
(Throw Away Model)
Prototype
(Cyclic) Spiral Model
Spiral is built upon two models,
namely Waterfall Model and the
iterative model.

•Risk Handling
•Radius of Spiral = Cost
•Angular Dimension = Progress
•Metal Model
Difference Between Prototype and Spiral
Model

S.No. Prototype Model Spiral Model

Difference Between Prototype and Spiral
Model

S.No. Prototype Model Spiral Model

Difference Between Prototype and Spiral
Model

S.No. Prototype Model Spiral Model

Difference Between Prototype and Spiral
Model

S.No. Prototype Model Spiral Model

Difference Between Prototype and Spiral
Model

S.No. Prototype Model Spiral Model

Difference Between Prototype and Spiral
Model

S.No. Prototype Model Spiral Model

Difference Between Prototype and Spiral
Model

S.No. Prototype Model Spiral Model

Difference Between Prototype and Spiral
Model

S.No. Prototype Model Spiral Model

 Difference Between Prototype and Spiral
Model

?
S.No. Prototype Model Spiral Model

ANY
Questions ?
? ANY
Questions ?

Hope You Have a Great Day.

Reference:
• www.javatpoint.com. (n.d.). Prototype Model - javatpoint. [online] Available at:
https://www.javatpoint.com/prototype-model [Accessed 16 Oct. 2022].
• www.javatpoint.com. (n.d.). Spiral Model - javatpoint. [online] Available at:
https://www.javatpoint.com/spiral-model.
• G
‌ eeksforGeeks. (2020). Difference between Prototype Model and Spiral Model. [online] Available
at: https://www.geeksforgeeks.org/difference-between-prototype-model-and-spiral-model/
[Accessed 16 Oct. 2022].
THANK
YOU