Scribd
Upload
6 views3 pages

Software Development Process Models

The document discusses three process models for software development: 1. The waterfall model proposes a sequential approach from requirements to support, but changes can cause confusion and it is difficult to state all requirements upfront. 2. The incremental model delivers software in increments to provide early functionality and allow for evaluation, with each increment building on the previous. 3. The iterative model is designed for software that evolves over time, allowing for increasingly complete versions as requirements and details are refined.

Uploaded by

Shamim Ahmed
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
6 views3 pages

Software Development Process Models

The document discusses three process models for software development: 1. The waterfall model proposes a sequential approach from requirements to support, but changes can cause confusion and it is difficult to state all requirements upfront. 2. The incremental model delivers software in increments to provide early functionality and allow for evaluation, with each increment building on the previous. 3. The iterative model is designed for software that evolves over time, allowing for increasingly complete versions as requirements and details are refined.

Uploaded by

Shamim Ahmed
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

PROCESS MODELS

WATERFALL MODEL

The waterfall model, sometimes called the classic life cycle, suggests a systematic, sequential approach6 to
software development that begins with customer specification of requirements and progresses through planning,
modeling, construction, and deployment, culminating in ongoing support of the completed software (Figure 2.3).

Among the problems that are sometimes encountered when the waterfall model is applied are:

1. 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.

2. It is often difficult for the customer to state all requirements explicitly. The waterfall model requires this and has
difficulty accommodating the natural uncertainty that exists at the beginning of many projects.

3. The customer must have patience. A working version of the program(s) will not be available until late in the
project time span. A major blunder, if undetected until the working program is reviewed, can be disastrous.

1
INCREMENTAL MODEL

There are many situations in which initial software requirements are reasonably well defined, but the overall scope
of the development effort precludes a purely linear process. In addition, there may be a compelling need to
provide a limited set of software functionality to users quickly and then refine and expand on that functionality in
later software releases. In such cases, you can choose a process model that is designed to produce the software in
increments.

For example, word-processing software developed using the incremental paradigm might deliver basic file
management, editing, and document production functions in the first increment; more sophisticated editing and
document production capabilities in the second increment; spelling and grammar checking in the third increment;
and advanced page layout capability in the fourth increment. It should be noted that the process flow for any
increment can incorporate the prototyping paradigm.

The incremental process model focuses on the delivery of an operational product with each increment. Early
increments are stripped-down versions of the final product, but they do provide capability that serves the user and
also provide a platform for evaluation by the user.

2
ITERATIVE PROCESS MODEL

Software, like all complex systems, evolves over a period of time. Business and product requirements often change
as development proceeds, making a straight line path to an end product unrealistic; tight market deadlines make
completion of a comprehensive software product impossible, but a limited version must be introduced to meet
competitive or business pressure; a set of core product or system requirements is well understood, but the details
of product or system extensions have yet to be defined. In these and similar situations, you need a process model
that has been explicitly designed to accommodate a product that evolves over time.

Iterative models are characterized in a manner that enables you to develop increasingly more complete versions of
the software.

REFERENCE

Software Engineering: A Practitioner's Approach


Roger S. Pressman
[Link]

You might also like