Scribd
Upload
10 views13 pages

Process Models Prescriptive Process Models

Uploaded by

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

Process Models Prescriptive Process Models

Uploaded by

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

PROCESS MODELS

Prescriptive process models define a set of activities, actions, tasks,


milestones, and work products that are required to engineer high-quality
software.

These process models are not perfect, but they do provide a useful roadmap
for software engineering work

Process models:

The waterfall model,


Incremental process models,
Evolutionary process models,
The unified process
THE WATERFALL MODEL:

The waterfall model, sometimes called the classic life cycle, suggests a
systematic sequential approach to software development.

That begins with customer specification of requirements and progresses


through planning, modeling, construction, and deployment.

Context:

Used when requirements are reasonably well understood.

Advantage:

It can serve as a useful process model in situations where


requirements are fixed and work is to proceed to complete in a linear manner.
THE WATERFALL MODEL
The problems that are sometimes encountered when the waterfall model is
applied are:

 Real projects rarely follow the sequential flow that the model proposes.
Although the linear model can accommodate iteration, it does so indirectly. As
a result, changes can cause confusion as the project team proceeds.

 It is often difficult for the customer to state all requirements explicitly.

The waterfall model requires has difficulty in accommodating the natural


uncertainty that exist at the beginning of many projects
INCREMENTAL PROCESS MODELS:

•The incremental model

•The RAD model


THE INCREMENTAL MODEL:

Context: Incremental development is particularly useful when staffing is


unavailable for a complete implementation by the business deadline that
has been established for the project.

Early increments can be implemented with fewer people.

If the core product is well received, additional staff can be added to


implement the next increment

In addition, increments can be planned to manage technical risks


THE INCREMENTAL MODEL conti’

•The incremental model combines elements of the waterfall model


applied in an iterative fashion.

•The incremental model delivers a series of releases called increments


that provide progressively more functionality for the customer as each
increment is delivered.

•When an incremental model is used, the first increment is often a core


product. That is, basic requirements are addressed. The core product is
used by the customer. As a result, a plan is developed for the next
increment.

•The plan addresses the modification of the core product to better meet
the needs of the customer and the delivery of additional features and
functionality.

For example, word-processing


THE RAD MODEL:

Rapid Application Development (RAD) is an incremental


software process model that emphasizes a short development cycle.

The RAD model is a “high-speed” adaption of the waterfall


model, in which rapid development is achieved by using a
component base construction approach.

Context: If requirements are well understood and project scope


is constrained, the RAD process enables a development team to
create a “fully functional system” within a very short time period.
The RAD approach maps into the generic framework activities.

Communication works to understand the business problem and the


information characteristics that the software must accommodate.

Planning is essential because multiple software teams works in parallel on


different system functions.

Modeling encompasses three major phases- business modeling, data


modeling and process modeling- and establishes design representation that
serve existing software components and the application of automatic code
generation.

Deployment establishes a basis for subsequent iterations.


The RAD approach has drawbacks:

• For large, but scalable projects, RAD requires sufficient human


resources to create the right number of RAD teams.

• If developers and customers are not committed to the rapid-fire


activities necessary to complete the system in a much abbreviated time
frame, RAD projects will fail

• If a system cannot be properly modularized, building the components


necessary for RAD will be problematic

• If high performance is an issue, and performance is to be achieved


through tuning the interfaces to system components, the RAD approach
may not work; and

• RAD may not be appropriate when technical risks are high


Thank you..

You might also like