I picked only basics of prototype and spiral their Advantage , pros , cons , conclusions etc

1. SRI SIIM
VASANT KUNJ , DELHI
Assignments on MIS
Submitted To-
Ruchika Takker Sharma
Submitted By-
SHUBHAM JAISWAL
PGDM ( 2019-2021)

2. • What is SDLC and it’s Type.
• What is Spiral & Prototype Model.
• Need & Advantage of both.
• Pros & Cons of Both.

5. INFO -:
 The Spiral Model was Defined in his 1988 Article.
This Model was not the first Model to discuss
iterative development, but it was the first model to
explain why the iteration matter.

6. Spiral Model
Spiral Model is a combination of a waterfall model and
iterative model. Each phase in spiral model begins with a
design goal and ends with the client reviewing the
progress.
The development team in Spiral-SDLC model starts with a
small set of requirement and goes through each
development phase for those set of requirements. The
software engineering team adds functionality for the
additional requirement in every-increasing spirals until
the application is ready for the production phase.

7. Spiral Model

8. When to use Spiral Methodology?
When to use Spiral Methodology?
1. When project is large
2. When releases are required to be frequent
3. When creation of a prototype is applicable
4. When risk and costs evaluation is important
5. For medium to high-risk projects
6. When changes may require at any time
7. When long term project commitment is not feasible
due to changes in economic priorities

10. It is mainly used by large and mission
critical projects. As per my
understanding, NASA is one of the good
example which is using spiral model.

11. PROTOTYPE :-
• Prototyping is a general approach to develop an
effective replica of any idea or software or system
which needs further engineering for making it the
ultimate product. The prototype model will present a
mini-sized duplicate copy of your target end product
which requires precise customer feedback for
crafting accordingly.

12. MODERN PROTOTYPE
• The Prototyping Model is a methodology that is
treated as a model for software development
where a prototype - which is a premature
approximated sample of the final product, is
constructed and then tested. After that rework is
done on that unfinished product as per
requirement in anticipation of building a suitable
prototype that is, at last, attain after the entire
software is developed and then it is delivered to
the customer.

13. • Rapid Throwaway Prototyping: In this method,
developers can explore the ideas as well as get
proper customer feedback.
• Evolutionary Prototyping: Here your developed
prototype will primarily be incremented for
refining on the foundation of customer opinion
until the final one gets accepted.

15. The customers get to see the partial product early
in the life cycle. This ensures a greater level of
customer satisfaction and comfort.
Missing functionalities can be easily figured out.
New requirements can be easily accommodated as
there is scope for refinement.
Flexibility in design.

16. CONS :-
Developers in a hurry to build prototypes may end
up with sub-optimal solutions.
After seeing an early prototype, the customers
sometimes demand the actual product to be
delivered soon.
Costly w.r.t time as well as money.
It is very difficult for the developers to
accommodate all the changes demanded by the
customer.

17. CONCLUSION
As per my understanding the Prototyping
Model should be used when the requirements
of the product are not clearly understood or
are unstable. It can also be used if
requirements are changing quickly (think
zappos)

18. .