Lesson 3: Iterative Model

1. Introduction:

   • The Iterative Model allows for flexible development through cycles (iterations) of planning, designing, developing, and testing.
   • Each iteration results in an improved version of the software based on feedback gathered during the previous iteration.

2. Phases of the Iterative Model:

   • Requirements Gathering:
     • Initial gathering of requirements from stakeholders.
   • Design:
     • High-level design based on initial requirements.
   • Implementation:
     • Coding and development of the software based on the design.
   • Testing:
     • Testing the software to identify issues and gather feedback.
   • Evaluation:
     • Evaluation of the iteration’s success and feedback incorporation for the next iteration.
   • 

3. Advantages:

   • Flexibility: Allows for changes and improvements with each iteration.
   • Early Feedback: Stakeholders can see and provide feedback on a working version early in the process.
   • Risk Management: Risks are addressed and mitigated incrementally throughout the development cycle.

4. Disadvantages:

   • Complexity: Managing multiple iterations concurrently can be complex.
   • Scope Creep: Without careful management, requirements may expand with each iteration, impacting timelines and budgets.
   • Resource Intensive: Requires continuous involvement and feedback from stakeholders and team members.

5. Real World Application of Iterative Model in Designing JUST-Learning App:

   • Example: Developing the course management module of the JUST-Learning Portal, allowing for iterative improvements based on feedback from instructors and students.
   • Benefits: Enables the JUST-Learning team to deliver incremental updates and improvements to course management features. Early testing and feedback incorporation ensure that user needs are met effectively.
   • Restrictions: Requires disciplined project management to prevent scope creep and maintain focus on delivering valuable increments with each iteration.

Conclusion: The Iterative Model is suitable for projects where requirements are likely to evolve or are not fully known upfront, such as developing interactive features for the JUST-Learning Portal. It emphasizes flexibility and continuous improvement based on stakeholder feedback.