The document discusses the incremental model of software development. It involves constructing a partial initial implementation and then gradually adding more functionality through subsequent releases. Each release builds on previous ones by delivering additional features. The incremental model allows for early delivery of basic functionality, customer feedback, and a divide and conquer approach. However, it requires good planning, design of the complete system upfront, and well-defined module interfaces. The incremental model is best for projects that need early benefits, lengthy development schedules, or new technologies.

1. Sushant Kushwaha

2. Hello……

3. INCREMENTAL MODEL

4. STEPS:
 Construct partial implementation of a total system.
 Then slowly add increased functionality.
 Prioritize requirements and implement them in group.
 Each subsequent release of the system add functions
to the previous ones

5. Strengths……
 Develop high risk and major functionality first.
 Each release delivers an operational product.
 Customer can respond to each product.
 Uses “Divide and Conquer” paradigm for breakdown .
 Initial delivery is faster and of lower cost.

6. Weakness…..
 Requires good planning and designing.
 Requires early definition of a complete and fully
functional system to allow for the definition of the
increment.
 Well defined module interface are required

7. When to use this model…..
 A need for early realization of benefit.
 A need to get basic functionality to the market early.
 Project which have lengthy development schedule.
 Project with new Technology.

8. Iterative Development
 Develop, then evaluate, then change, …
 Never expected it to be right.
 Iterate to find the right solution.

9. Iterative Development
Iteration means the act of repeating a process usually with
the aim of approaching a desired goal or target or result.
Each repetition of the process is also called an
“iteration”, and the results of one iteration are used as
the starting point for the next iteration.

10. 1st Iteration

11. 2nd Iteration

12. 3rd Iteration

13. 4th Iteration

14. Incremental development
 Incrementally add software a time
 Build up functionality gradually
 Release incrementally so that we actually get that
business value we're chasing.
 We don't really get return on investment till people
begin to use the software we've built.

15. Incremental development
 Incrementalism is a method of working by adding to a
project using many small, incremental changes instead
of a few (extensively planned) large jumps.
It means you develop one part of the system and when
it’s ready you develop the next part

17. 1st Increment

18. 2nd Increment

19. 3rd Increment

20. 4th Increment

21. Putting both together……
 Incremental development goes through all the phases of
development (analysis, testing, development, design,
integration, production) it is a perfect tool to expose all
problems in the process.
 Incrementalism improves the process and
adds new topics.
 Iterative process means rework on the existing product.
 Iterativity improves the product
 Both can be used without each other but they can be used
together as well.

22. 1st Increment and 1st Iteration

23. 1st Increment and 4th Iteration

24. 2nd Increment and 4th Iteration

25. 3rd Increment

26. 4th Increment