Software Development Models
(Exploring Waterfall, V-Shaped, and Prototype Models)
1
Topics:
• Software Development Models
• Iterative Model
• Advantages and Disadvantages of Iterative Model
• V-Shaped Model
• Advantages and Disadvantages of V-Shaped Model
• Prototype Model
• Advantages and Disadvantages of Prototype Model
• Comparison Table
2
Software development models
Software development models are systematic approaches
or methodologies used in the process of designing,
developing, testing, and maintaining software systems.
3
Iterative Model
The iterative model is a software
development methodology that involves
repeating cycles or iterations of the
development process. Unlike traditional
waterfall models where the development
phases are executed sequentially, the
iterative model allows for revisiting and
refining different stages of development
in a cyclic manner.
4
Advantages and Disadvantages of Iterative Model
5
V- Shaped Model
The V-Model, also known as the
Verification and Validation model, is a
software development and testing
framework that is an extension of the
traditional waterfall model. The V-Model
emphasizes the relationship between each
development stage and its corresponding
testing phase.
6
Advantages and Disadvantages of V-Shaped Model
7
Prototype Model
The prototyping model is a systems development method
in which a prototype is built, tested and then reworked as
necessary until an acceptable outcome is achieved from
which the complete system or product can be developed.
8
Advantages and Disadvantages of Prototype Model
9
Comparison Table
Feature Iterative Model V-Shaped Model Prototype Model
Development Incremental development Extension of Waterfall with Iterative, prototype-based
Approach through repeated cycles emphasis on testing approach
Phases Requirements, Design, Requirements, Design, Coding, Initial Requirements, Quick
Implementation, Testing, Unit Testing, Integration Testing, Design, Build Prototype,
Evaluation, Repeat System Testing, Acceptance Testing User Evaluation, Refine
Prototype
Flexibility High Low to Medium Moderate
User Continuous user feedback Limited until testing phase Active involvement
Involvement throughout the development throughout
process
Documentation Continuous documentation and Documentation at each testing stage May lack comprehensive
refinement documentation
Adaptability to High Limited Moderate
Changes
Testing Ongoing throughout the Throughout the development cycle Early and continuous testing
Emphasis development process
10
Conclusion
Each model has its strengths and weaknesses, and the choice depends on project specifics. Agile principles can be integrated
for flexibility, emphasizing the importance of constant communication, testing, and user involvement throughout the
development process. Ultimately, the selection should align with the unique needs and dynamics of the project at hand.
11
S U B M I T T E D B Y: SUBMITTED TO:
Abdullah Al Azme Fatema Binte Hassan
ID-210321001 Lecturer, Department of CSE,
Program-Bsc in CSE(Reg) European University Of Bangladesh
8th Semester,20th batch
European University Of Bangladesh.
12
Thank You
13