The document describes an incremental process model for software development. It is divided into sections that define the incremental process model, when it is used, pros, and cons. The incremental process model involves dividing the entire project into smaller increments, with each increment going through requirements analysis, design, coding, and testing. This allows working software to be developed quickly and added to over time until the full system is complete. The approach is useful when requirements are well understood but some details may change, or when early delivery to market is needed. Benefits include faster delivery and flexibility, while drawbacks include needing good upfront planning and potential higher total costs than traditional models.

1. Incremental
Process
Model
ICT2233 - Software Engineering
Requirement
Analysis
Increment
Design
Coding
Requirement
Analysis
Increment
Design
Coding
Requirement
Analysis
Increment
Design
Coding

2. Group members
o TG/2017/233 – Madushan Sandaruwan
o TG/2017/244 – Shashani Dhanujika
o TG/2017/258 – Dulmini Sandunika
o TG/2017/277 - Priyanka

3. Definition1
When it use?2
Cons4
Pros3
Contents

4. Definition

5. o In Incremental Model the whole requirement is divided into
various builds.
o Each pass through requirements, design, implementation
and testing phases.
o When we work incrementally, we are adding piece by
piece, but expect that each piece is fully finished.
o Thus, keep on adding the pieces until it’s complete.

7. When it use?

8.  Requirements of the complete system are clearly defined
and understood.
 Major requirements must be defined; however, some
details can evolve with time.
 There is a need to get a product to the market early.
 A new technology is being used.
 Resources with needed skill set are not available.
 There are some high-risk features and goals.

9. Pros

10.  Generates working software quickly and early during the
software life cycle.
 More flexible.
 Easier to test and debug during a smaller iteration.
 Customer can response to each bolt.
 Lowest initial delivery cost.
 Easy to manage risk.

11. Cons

12.  Needs to good planning and design.
 Needs a clear and complete definition of the whole system
before it can be broken down and build incrementally.
 Total cost is higher than a waterfall.
 Difficult to break the system into part.

13. Questions?

14. Thank you!