NEHRU ARTS AND SCIENCE COLLEGE

COIMBATORE -641 105

DEPARTMENT OF INFORMATION TECHNOLOGY

Course: Software Engineering

Facilitator : Dr.S.Saraswathi

NASC 1
 Topic

• Prescriptive Process Models

• Incremental Process Model

2
NASC
 Incremental Process Model
1. To provide a limited set of software functionality to users
quickly and then refine and expand on that functionality
in later software release.
2. In the above situation, we can choose a process model
that is designed to produce the software in increments.

NASC 3
 Incremental Process Model
1. Incremental development is based on the idea of
developing an initial implementation, exposing this to
user feedback.
2. Several versions of evolving is done through until an
acceptable system has been developed.

3. This incremental model combines elements of linear

and parallel process flows.
NASC 4
 Incremental Process Model

4. In incremental model the whole requirement is divided

into various builds.

NASC 5
 Incremental Process Model
1. Each module (independent units) passes through the
requirements, design, implementation and testing
phases.

2. The incremental build model is a method of software

development where the product is designed,
implemented and tested incrementally until the product
is finished.

NASC 6
 When to use the Incremental model
1. This model can be used when the requirements of the
complete system are clearly defined and understood.
2. Major requirements must be defined; however, some
details can evolve with time.
3. There is a need to get a product to the market early.

NASC 7
 Incremental Process Model

NASC 8
 The Incremental Model
1. Applies linear sequences in a staggered fashion as
calendar time progresses.
2. Each linear sequence produces deliverable
“increments” of the software

NASC 9
 Example for Incremental Process Model
1. Development of Word-processing software:
1. 1st : Basic file management, editing and documentation

2. 2nd: More sophisticated editing

3. 3rd: Spelling and Grammar Checking Facility

4. 4th: Advanced page layout capability
5. … nth: More sophistication…

NASC 10
 Example for Incremental Process Model

In the diagram above when we work incrementally we are

adding piece by piece but expect that each piece is fully
finished. Thus keep on adding the pieces until it’s complete.

NASC 11
 Communication

1. This is the first phase and it Involves communication

among the customer and other stake holders
2. It encompasses requirements gathering

NASC 12
 Planning
1. The requirement specifications from first phase are studied
in this phase and the system is planned according to
requirements.

2. Establishes a plan for software engineering work

3. Addresses technical tasks, resources, work products, and

work schedule

NASC 13
 Modeling (Analyze, Design)
1. System Modeling helps in specifying hardware and system
requirements and also helps in defining overall system
architecture.

2. Encompasses the creation of models to better under the

requirements and the design

3. The software code to be written in the next phase.

NASC 14
 Construction (Code, Test)
1. With inputs from system design, the system is first
developed in small programs called units.
2. Each unit is developed and tested for its functionality which
is referred to as Unit Testing.
3. At last it is integrated and tested

4. Combines code generation and testing to uncover errors

NASC 15
 Deployment

The product is deployed in the customer environment or

released into the market for evaluation and feedback

NASC 16
 Advantages of Incremental Model
1. Generates working software quickly and early during the
software life cycle.
2. This model is more flexible – less costly to change
scope and requirements.
3. It is easier to test and debug during a smaller iteration.

NASC 17
 Advantages of Incremental Model
1. In this model customer can respond to each built.

2. Lowers initial delivery cost.

3. Easier to manage risk because risky pieces are
identified and handled during it’d iteration.

NASC 18
 Disadvantages of Incremental Model
1. Needs good planning and design.

2. Needs a clear and complete definition of the whole

system before it can be broken down and built
incrementally.
3. Total cost is higher than waterfall.

NASC 19
 Types of Incremental model
There are 2 types in incremental process model:

1. Staged Delivery Model

2. Parallel Development Model

NASC 20
 Staged Delivery Model

NASC 21
 Staged Delivery Model
1. Staged Delivery Model – Construction of only one part

of the project at a time.

NASC 22
 Parallel Development Model

NASC 23
 Parallel Development Model
Parallel Development Model – Different subsystems are
developed at the same time. It can decrease the calendar
time needed for the developmen

NASC 24
 When to use this model
1. Funding Schedule, Risk, Program Complexity, or need
for early realization of benefits.
2. When Requirements are known up-front.
3. When Projects having lengthy developments schedules.
4. Projects with new Technology.

NASC 25
 Advantages
1. Error Reduction (core modules are used by the
customer from the beginning of the phase and then
these are tested thoroughly)
2. Uses divide and conquer for breakdown of tasks.
3. Lowers initial delivery cost.
4. Incremental Resource Deployment

NASC 26
 Disadvantages
1. Requires good planning and design.

2. Total cost is not lower.

3. Well defined module interfaces are required.

NASC 27
 Summary
• In incremental model the whole requirement is divided
into various builds.
• Multiple development cycles take place here, making the
life cycle a “multi-waterfall” cycle.
• In this model, each module passes through the
requirements, design, implementation
and testing phases.

NASC 28
 Summary
• Generates working software quickly, more flexible ,less
cost to change scope and requirements.
• It is easier to test and debug during a smaller iteration.

NASC 29
NASC 30