2. What is Software Development Life Cycle
(SDLC)?
• Software development lifecycle (SDLC) is a framework that defines the
steps involved in the development of software. It covers the detailed plan for
building, deploying and maintaining the software.
• SDLC defines the complete cycle of development i.e. all the tasks involved in
gathering a requirement for the maintenance of a Product.
• SDLC models are following types:-
Waterfall model
Iterative model
Prototype model
Spiral model
5. Prototyping Model
• A prototyping model suggest that before carrying out the development of the
actual software, a working prototype of the system should be built.
• A prototype is a toy implementation of the system.
• Prototype is a working model of software with some limited functionality.
• Prototyping is used to allow the users evaluate the developer proposals and try
them out before implementation.
• By using this prototype, customer can understand the requirements of desired
system and also the customer can get an “actual feel” of the system. It is an
attractive idea for complex and bigger systems.
6. EXAMPLES-
• Paper Prototype- Paper
prototype is an example of
throwaway prototype created
in the form of rough or hand-
sketched drawings of the
product’s interface, front-end
design, and sometimes the
back end work.
7. EXAMPLES -
• 3D print- The latest
technology has made it possible
to print a 3d version of your
product which can actually
work. But this technique is not
feasible for mass production.
8. EXMPLES -
• Digital Prototype -A digital
prototype allows product
developers to create a virtual
model of the product which
enables them to see how the
individual components will work
together and how the product will
look once it’s completed.
That is, it lets the developers
virtually explore the complete
product before it’s actually built.
10. Steps of the prototype model-
• Requirements gathering and Analysis : A prototype model
begins with requirements analysis, and the requirements of the system are define
in detail. The user is interviewed in order to know the requirements of the
system.
• Quick design: When requirements are known, a quick design for the
system is created. It is not a detailed design , it includes the important aspects of
the system, which gives an idea of the system to the user.
• Build prototype: Information gathering from quick design is modified to
form a prototype .It represents a ‘rough’ design of the required system.
11. • Customer evaluation of prototype: The build prototype is
presented to the customer for his/her evaluation.
• Prototype refinement: Once the user evaluate the prototype, it is refined
according to the requirements . When the user is satisfied to the developed
prototype , a final system is developed based on the final prototype , which is
developed by the iterative method means we design the system according to the
final prototype , after that implement , test the product to find the error and at
last we maintain the system.
12. Need of the prototype model:-
• Prototype provides a method to examine design problems and
evaluating solutions.
• “…Prototypes are not self explanatory….Clarifying what aspects of
a prototype correspond to the eventual artifact─ and what don’t─ is
a key part of successful prototyping.”
• The development of the prototype model is expensive but is a
good model because it satisfy all the requirements of the customers.
13. Advantages and Disadvantages of Prototype
model
ADVANTAGES
• Customer satisfaction exists, because
customer can feel the product at very
early stage.
• There will be less chance of software
rejection.
• Requirement changes are allowed.
• Due to customer approval we can find the
errors at early stage.
• Customer involvement will be there in the
development where its leads to better
solutions for any confusion / complexity /
difficult functions
• The developed prototype can be re-used
by developer and test engineer.
DISADVANTAGES
• It is a time consuming if customer ask
for changes in prototype
• This methodology may increase the
system complexity as scope of the
system may expand beyond original
plans.
• The invested effort in the preparation
of prototypes may be too much if not
properly monitored.
• Customer may get confused in the
prototypes and real systems.
