Scribd
Upload
2 views

Lecture 3 (Process Models Incremental)

The document provides an overview of software process models, including the Build and Fix Model, Waterfall Model, and Incremental Model. It discusses the necessity of models in software engineering to manage risks and accommodate changes based on customer feedback. Each model's advantages and disadvantages are outlined, along with guidance on when to use them.

Uploaded by

khizarzafar19
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
2 views

Lecture 3 (Process Models Incremental)

The document provides an overview of software process models, including the Build and Fix Model, Waterfall Model, and Incremental Model. It discusses the necessity of models in software engineering to manage risks and accommodate changes based on customer feedback. Each model's advantages and disadvantages are outlined, along with guidance on when to use them.

Uploaded by

khizarzafar19
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 23

SE101 : Introduction to SE

BSAI/BSSE : Spring 2025

Software Process Models

Uswah Ahmad Khan


Lecturer

Slides Credit: Dr. Qurat-ul-Ain


This Class
◾ About software process model
◾ Build and Fix Model
◾ Why Models are needed?
◾ Process as a "black box“ & Problem
◾ Process as a “white box“ & Advantage
◾ Prescriptive Model
◾ Waterfall Model or Linear Sequential
◾ Incremental Process Models
◾ Incremental Model
◾ RAD Model
Build and Fix Model
Build and Fix Model
The earlier approach
□ Product is constructed without specification or any attempt at design.
□ developers simply build a product that is reworked as many times as
necessary to satisfy the client.
□ model may work for small projects but is totally unsatisfactory for products of
any reasonable size.
□ Maintenance is high.
□ Source of difficulties and deficiencies
■ impossible to predict
■ impossible to manage
Why Models are needed?
□ Symptoms of inadequacy: the software crisis
■ scheduled time and cost exceeded
■ user expectations not met
■ poor quality
Process as a "black box"

Quality?
Uncertain /
Incomplete requirement
In the beginning
Problems
□ The assumption is that requirements can be fully
understood prior to development
□ Interaction with the customer occurs only at the
beginning (requirements) and end (after delivery)
□ Unfortunately the assumption almost never holds
Process as a "white box"
Advantages
□ Reduce risks by improving visibility
□ Allow project changes as the project progresses
■ based on feedback from the customer
Prescriptive Model
□ Prescriptive process models advocate an orderly approach to software engineering
■ Organize framework activities in a certain order
□ Process framework activity with set of software engineering actions.
□ Each action in terms of a task set that identifies the work to be accomplished to meet the goals.
□ The resultant process model should be adapted to accommodate the nature of the specific
project, people doing the work, and the work environment.
□ Software engineer choose process framework that includes activities like;
■ Communication
■ Planning
■ Modeling
■ Construction
■ Deployment
The Waterfall Model
Waterfall Model Phases
❖ There are separate identified phases in the waterfall model

12
a phase must be
complete before moving
onto the next phase
Waterfall Model Problems
❖ Inflexible partitioning of the project into distinct stages makes it
difficult to respond to changing customer requirements.
○ requirements are well-understood and changes will be fairly limited
during the design process.
○ Few business systems have stable requirements.
❖ The waterfall model is mostly used for large systems engineering
projects where a system is developed at several sites.

14
Waterfall Model
Advantages Disadvantages

1. linear and segmental 1. define all requirements


model in the beginning
2. easy to understand 2. no accommodation for
3. non-existing change
interdependencies lead 3. working version not
to no complicated team available until late in the
coordination project’s life
4. Documentation available

15
When to use Waterfall Model?
This model is used only when the requirements are very
well known, clear and fixed.

Product definition is stable.

Technology is understood.

There are no ambiguous requirements

Ample resources with required expertise are available


freely
16
Rather than deliver the
system as a single delivery,
the development and
delivery is broken down
into increments with each
increment delivering part
of the required
functionality
Incremental Model

18
Incremental Process Model

C- Communication
P - Planning
M – Modeling
C - Construction
D - Deployment

Delivers software in small but usable pieces, each piece builds on


pieces already delivered
Incremental Model Benefits
The cost of accommodating changing
customer requirements is reduced.

It is easier to get customer feedback on


the development work that has been done.

More rapid delivery and deployment of


useful software to the customer is
possible.
20
Incremental Model Problems

The process is not visible.

System structure tends to degrade as new


increments are added.

21
Incremental Model
Advantages Disadvantages

1. generates working 1. needs good planning and


software quickly and design.
earlier 2. needs clear and
2. Useful when staff is complete definition of
unavailable whole system
3. More flexible 3. total cost higher than
4. Easier to test and debug waterfall
5. Easier to manage risk

22
When to use Incremental Model?

A new technology is being used

Resources with needed skill set are not available

There are some high-risk features and goals which


may change in the future

Major requirements must be defined; however, some


details can evolve with time.

There is a need to get a product to the market early.


23

You might also like