Skip to main content

Short note: Iterative development cycles

Short answer

Iterative development builds a system in short, repeated cycles (2–6 weeks), each performing analysis, design, coding, and testing to produce a tested, partial system. Features include handling risky requirements first, using feedback for adaptation, and welcoming change, enabling early problem detection and steady, visible progress.

Write a short note on Iterative cycles of development.

Iterative development builds a system through repeated cycles (iterations), each one a short, fixed-length mini-project (typically 2 to 6 weeks) that includes analysis, design, coding and testing. At the end of each iteration a tested, partially working, integrated system is produced, and the next iteration adds more features.

Larman recommends it as the basis of the Unified Process: development is divided into iterations, each with its own requirements, design, implementation and testing, and the system grows incrementally.

 Iter 1      Iter 2      Iter 3      Iter n
 +-----+    +-----+     +-----+     +-----+
 |Anal.|    |Anal.|     |Anal.|     |Anal.|
 |Des. | -> |Des. | ->  |Des. | ... |Des. |
 |Code |    |Code |     |Code |     |Code |
 |Test |    |Test |     |Test |     |Test |
 +-----+    +-----+     +-----+     +-----+
 small      bigger      bigger      final
 system     system      system      system

Features

  • Early, risky and high-value requirements are handled first.
  • Feedback from users and testers is used to adapt the next iteration.
  • Requirements are not frozen at the start, so change is welcome.

Advantages: early detection of risk and problems, early working software, easier change, steady progress that is visible, and learning from each cycle.

Difference from waterfall: waterfall does all analysis, then all design, then all coding once; iterative repeats a small version of all activities many times.

✓ Answer checked by Claude Opus 5.5 (high effort)

All Object Oriented Analysis and Design chapter 1 questions →