Scribd
Upload
13 views6 pages

L 03

The iterative waterfall model overcomes shortcomings of the classical waterfall model by allowing for feedback loops between phases to detect and correct errors. Having working versions early enables functional and design flaws to be identified and addressed at lower cost. However, this model is best suited to large, complex projects where it is possible to break the system into incremental modules. Prototyping involves building crude, initial versions of the system using shortcuts to illustrate key aspects like interfaces, outputs, and interactions for customer understanding and technical issue resolution. Prototypes are preferable when requirements are uncertain or technical solutions unclear, as they provide experience to help develop the final product.

Uploaded by

jamesboss207
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
13 views6 pages

L 03

The iterative waterfall model overcomes shortcomings of the classical waterfall model by allowing for feedback loops between phases to detect and correct errors. Having working versions early enables functional and design flaws to be identified and addressed at lower cost. However, this model is best suited to large, complex projects where it is possible to break the system into incremental modules. Prototyping involves building crude, initial versions of the system using shortcuts to illustrate key aspects like interfaces, outputs, and interactions for customer understanding and technical issue resolution. Prototypes are preferable when requirements are uncertain or technical solutions unclear, as they provide experience to help develop the final product.

Uploaded by

jamesboss207
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/ 6

ITERATIVE WATERFALL MODEL

• To overcome the major shortcomings of the classical waterfall model,


we come up with the iterative waterfall model.
• Here, we provide feedback paths for error correction as & when detected later in
a phase. Though errors are inevitable, but it is desirable to detect them in the
same phase in which they occur. If so, this can reduce the effort to correct the
bug.
• The advantage of this model is that there is a working model of the system at a
very early stage of development which makes it easier to find functional or
design flaws. Finding issues at an early stage of development enables to take
corrective measures in a limited budget.
• The disadvantage with this SDLC model is that it is applicable only to large and
bulky software development projects. This is because it is hard to break a small
software system into further small serviceable increments/modules.
PRTOTYPING MODEL

• Prototype
• A prototype is a toy implementation of the system. A prototype usually
exhibits limited functional capabilities, low reliability, and inefficient
performance compared to the actual software. A prototype is usually
built using several shortcuts. The shortcuts might involve using
inefficient, inaccurate, or dummy functions. The shortcut
implementation of a function, for example, may produce the desired
results by using a table look-up instead of performing the actual
computations. A prototype usually turns out to be a very crude version
of the actual system.
• Need for a prototype in software development
• There are several uses of a prototype. An important purpose is to illustrate the input data formats, messages,
reports, and the interactive dialogues to the customer. This is a valuable mechanism for gaining better
understanding of the customer’s needs:
• how the screens might look like
• how the user interface would behave
• how the system would produce outputs

• Another reason for developing a prototype is that it is impossible to get the perfect product in the first attempt.
Many researchers and engineers advocate that if you want to develop a good product you must plan to throw away
the first version. The experience gained in developing the prototype can be used to develop the final product.
• A prototyping model can be used when technical solutions are unclear to the development team. A developed
prototype can help engineers to critically examine the technical issues associated with the product development.
Often, major design decisions depend on issues like the response time of a hardware controller, or the efficiency of
a sorting algorithm, etc. In such circumstances, a prototype may be the best or the only way to resolve the technical
issues.
• A prototype of the actual product is preferred in situations such as:
• User requirements are not complete
• Technical issues are not clear

You might also like