Scribd
Upload
403 views1 page

The Waterfall Model

The Waterfall Model is an early method for structured systems development that consists of sequential phases from conceptualization to testing. Although criticized for its rigidity, it provided the theoretical basis for other process models by most closely resembling a generic software development model. The phases include system conceptualization, analysis of requirements, system design, coding, and iterative testing to ensure internal efficiency and external effectiveness according to the design.

Uploaded by

ajitkumarsahu4288
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
403 views1 page

The Waterfall Model

The Waterfall Model is an early method for structured systems development that consists of sequential phases from conceptualization to testing. Although criticized for its rigidity, it provided the theoretical basis for other process models by most closely resembling a generic software development model. The phases include system conceptualization, analysis of requirements, system design, coding, and iterative testing to ensure internal efficiency and external effectiveness according to the design.

Uploaded by

ajitkumarsahu4288
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 1

The Waterfall Model

The Waterfall Model is the earliest method of structured system development. Although it has come under attack in
recent years for being too rigid and unrealistic when it comes to quickly meeting customer's needs, the Waterfall
Model is still widely used. It is attributed with providing the theoretical basis for other Process Models, because it
most closely resembles a "generic" model for software development.

Figure 2. Waterfall Model

The Waterfall Model consists of the following steps:

• System Conceptualization. System Conceptualization refers to the


consideration of all aspects of the targeted business function or process, with the
goals of determining how each of those aspects relates with one another, and
which aspects will be incorporated into the system.
• Systems Analysis. This step refers to the gathering of system
requirements, with the goal of determining how these requirements will be
accommodated in the system. Extensive communication between the customer
and the developer is essential.
• System Design. Once the requirements have been collected and
analyzed, it is necessary to identify in detail how the system will be constructed
to perform necessary tasks. More specifically, the System Design phase is
focused on the data requirements (what information will be processed in the
system?), the software construction (how will the application be constructed?),
and the interface construction (what will the system look like? What standards
will be followed?).
• Coding. Also known as programming, this step involves the creation of
the system software. Requirements and systems specifications from the System
Design step are translated into machine readable computer code.
• Testing. As the software is created and added to the developing
system, testing is performed to ensure that it is working correctly and efficiently.
Testing is generally focused on two areas: internal efficiency and external
effectiveness. The goal of external effectiveness testing is to verify that the
software is functioning according to system design, and that it is performing all
necessary functions or sub-functions. The goal of internal testing is to make sure
that the computer code is efficient, standardized, and well documented. Testing
can be a labor-intensive process, due to its iterative nature.

You might also like