Iterative Model
Iterative Model
---
#### **Introduction**
In the previous session, we explored the **Waterfall Model** and the **V Model**,
along with their advantages and disadvantages. While the V Model improved upon the
Waterfall Model by involving testing in every phase, both models shared a
significant drawback: **long delivery durations**. In modern software development,
delivering value to customers quickly is essential to adapt to dynamic market
conditions. This led to the introduction of the **Iterative Development Model**.
---
---
---
---
1. **Iteration 1:**
- Build a **login page** with:
- Username and password fields.
- A login button.
- This simple version is built, tested, and deployed.
2. **Iteration 2:**
- Enhance the login page by adding:
- CSS for better design.
- Forgot Password functionality.
- These features are built, tested, and deployed.
3. **Iteration 3:**
- Add advanced login features such as:
- Google and Facebook login options.
- Build, test, and deploy these new features.
By the end of these iterations, the customer has a working e-commerce app that has
been incrementally built and tested. The customer doesn’t need to wait for 2 years
to see the software—it’s delivered in smaller, usable portions.
---
---
---
- **Differences:**
- **Iterative Development:** Retains a phased approach within iterations
(requirement, design, develop, test, deploy).
- **Agile:** Goes beyond iterations to emphasize flexibility, collaboration, and
continuous feedback throughout the process.
---
### **Conclusion**
The **Iterative Development Model** was a major step forward in software
development, enabling faster delivery and early customer feedback. However, it
still relies on a phased approach. In the next session, we’ll discuss **Agile
Development**, which takes iterative concepts to the next level, offering greater
flexibility and addressing many limitations of earlier models.
---