Scribd
Upload
11 views3 pages

Swapnil Dutta Assignment

The document discusses three software development models: the classical waterfall model, the iterative waterfall model, and the prototyping model. The classical model is linear and inflexible, while the iterative model introduces feedback loops for better adaptability. The prototyping model emphasizes user involvement and iterative feedback to refine requirements, making it suitable for projects with unclear or changing requirements.

Uploaded by

Swapnil Dutta
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
11 views3 pages

Swapnil Dutta Assignment

The document discusses three software development models: the classical waterfall model, the iterative waterfall model, and the prototyping model. The classical model is linear and inflexible, while the iterative model introduces feedback loops for better adaptability. The prototyping model emphasizes user involvement and iterative feedback to refine requirements, making it suitable for projects with unclear or changing requirements.

Uploaded by

Swapnil Dutta
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/ 3

• NAME – SWAPNIL DUTTA

• B.B.A (DIGITAL MARKETING)


• STUDENT ID. – 2211203003026
• REGISTRATION NO. – 220030532057
• SECTION – 3
• SUBJECT – MIS & E-COMMERCE
• BATCH – ( 2022 to 2025 )
• SISTER NIVEDITA UNIVERSITY
• SEMESTER – 6 TH

[ ASSIGNMENT ]

Q.1) What is classical waterfall model ?

ANS :- Classical Waterfall Model:

The classical waterfall model is a linear and sequential software development methodology. It
consists of distinct phases: Requirements Analysis, System Design, Implementation, Testing,
Deployment, and Maintenance. Each phase must be completed before the next begins, and there
is minimal overlap or feedback between the stages. It is called the “waterfall” model because it
flows downward through these phases like a waterfall.

This model is simple and easy to understand, which makes it suitable for smaller projects with
well-defined requirements. However, it has several limitations. The main drawback is its
inflexibility—once a phase is completed, revisiting it is difficult. This model assumes that all
requirements can be gathered upfront, which is rarely practical in real-world projects.

Q.2) Why iterative waterfall model is more advance?

ANS :- Iterative Waterfall Model:

The iterative waterfall model is an improvement over the classical version. While it maintains the
same linear structure of phases, it introduces feedback loops. These loops allow developers to
revisit and revise previous phases if issues or changes arise later in the development cycle.
This model is more advanced because it provides more flexibility. If testing reveals issues,
developers can return to the design or requirements phase to make corrections. This reduces the
risk of project failure due to early-stage errors and adapts better to changing customer needs. It
bridges the gap between rigid planning and real-world unpredictability.

Q.3) Explain Prototyping model and the significance of this model?


ANS :- Prototyping Model:

The prototyping model is a software development approach where a working prototype (a


simplified version of the final product) is built early in the development process. This prototype
is presented to the user for feedback, which is then used to refine the requirements and design.
This cycle continues until the prototype evolves into the final product.

There are different types of prototyping such as throwaway (rapid) prototyping and evolutionary
prototyping. In rapid prototyping, the prototype is discarded after gathering feedback, while in
evolutionary prototyping, the prototype is continuously improved and becomes the final system.

• Significance of the Prototyping Model:

- Better Requirement Understanding: Users interact with the prototype, leading to clearer and
more accurate requirements.

- Improved User Involvement: Continuous feedback keeps users involved, ensuring the product
aligns with their expectations.
- Reduced Risk: Early visibility of the product helps identify and fix issues in the initial stages,
reducing the cost and effort later.

- Faster Development: The iterative nature of this model helps speed up the development and
delivery of the final system.

• Overall, the prototyping model is especially useful in projects where the requirements are
not clearly defined from the beginning or are expected to change frequently.

You might also like