Increment model Software Enginnering

1. Increment Model
Abdul Hafeez Balouch
Introduction to
increment model
(Presentation 01)

2. Topic Outlines
Introduction to Incremental Model
Diagram
Phases
Example
Applicable
Advantages
Disadvantages
Problem

3. Incremental model
✓Method of s/w development
✓ Incremented until the product is furnished.
✓ Evolution of water fall model.
✓Customer satisfication.
✓Combines the element of water fall with
the iterative
✓Philosophy of prototyping.
✓Scheduling and staging strategy

4. Diagram

5. Phases
Basically five phases
Communication
Planning
Modeling (analysis, design)
Construction (code, test)
Deployment (delivery, feedback)

6. Communication
✓First or Initial phase.
✓In the meeting different aspects of the
project are
✓Suggested.
✓Collaboration b/w two company.
✓Idea of the customer about the project.
✓Customer suggestion.

7. Planning
✓Meeting of the project company,
✓Instruction of the pm to the staff,
✓In this pm emphasizes on:
✓How to work start.
✓Quickly completion of the project.
✓Give demo version to the customer.

8. Modeling
Analysis and Design
➢ Development team visits the customer and
studies
✓ their system requirement
✓ It also consists of personnel assignments, costs
of system, project schedule and target dates,
✓ System Analysis and Design phase, the whole
software development process, the overall
software structure and its outlay are defined.

9. Construction
Code
Testing
✓Code and test is performed to check the
Feasibility, Reliability and working of the
software.
✓ After code generation phase the software
program testing begins.

10. Deployment
➢The software has been delivered to the
customer and gives feedback from the
customer
Delivery and Feedback:
✓Software will definitely go through change
once when it is delivered to the customer.
✓The software should be implemented to
accommodate changes that could be happen

11. Applicable
➢Incremental software development model
may be
Applicable to Projects where:
✓Software Requirements are well defined,
but realization may be delayed.
✓The basic software functionality are
required early

12. Advantages
✓Generates working software quickly and
early during the software life cycle.
✓It is easier to test and debug during a
smaller iteration.
✓In this model customer can respond to
each built.
✓Lowers initial delivery cost.

13. Disadvantages
✓Needs good planning and design.
✓Needs a clear and complete definition of
the whole system before it can be broken
down and built incrementally.
✓Total cost is higher than waterfall.
✓Problems may arise pertaining to system
architecture because not all requirements
are gathered up front for the entire
software life cycle.