---
title: "Short note: Iterative development cycles"
subject: "Object Oriented Analysis and Design"
chapter: 1
key: "semester_6/object_oriented_analysis_and_design:short-note-iterative-development-cycles"
source: https://www.bctengineer.com/q/semester_6/object_oriented_analysis_and_design/short-note-iterative-development-cycles
site: BCT Engineering
---

# Short note: Iterative development cycles

Object Oriented Analysis and Design · Chapter 1: Object Oriented Fundamentals

- Asked in: 2069 Poush, 3 marks
- Video: [SE 5 : Learn Iterative Model in 10 Minutes with Examples | #softwareengineering](https://www.youtube.com/watch?v=dEgU7zw7dJ0) — CS & IT Tutorials by Vrushali 👩‍🎓
- Answer checked by Claude Opus 5.5 (high effort) on 2026-10-14
- Page: https://www.bctengineer.com/q/semester_6/object_oriented_analysis_and_design/short-note-iterative-development-cycles
- Whole chapter: https://www.bctengineer.com/md/semester_6/object_oriented_analysis_and_design/chapter-1

## Question

Write a short note on Iterative cycles of development.

## 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.

## Answer

**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.

```text
 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.

## Check yourself

The answer's key points as multiple-choice questions, with the correct option and why.

1. What does each iteration in iterative development contain?
   A. Only coding
   B. Only analysis and design
   C. A short mini-project with analysis, design, coding and testing, ending in a tested partial system
   D. Only testing of the final system
   Answer: C. Each fixed-length iteration (about 2 to 6 weeks) repeats all activities and yields a working integrated part. (Key point: Iteration content)

2. Which requirements are tackled in the early iterations?
   A. The easiest and least important
   B. Early, risky and high-value requirements
   C. Only documentation
   D. Those requested last by users
   Answer: B. Handling risky and high-value items first detects problems early. (Key point: What is handled first)

3. How does iterative development differ from waterfall?
   A. It does all analysis first, then all design once
   B. It repeats a small version of all activities many times, with feedback adapting later iterations
   C. It avoids testing until the end
   D. It freezes requirements at the start
   Answer: B. Waterfall does each activity once for the whole system; iterative cycles through them repeatedly and welcomes change. (Key point: Difference from waterfall)