Scribd
Upload
6 views10 pages

Presentation 1

Uploaded by

surajitgiri1203
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
6 views10 pages

Presentation 1

Uploaded by

surajitgiri1203
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/ 10

Basics of Software

development Life Cycle


& Prototyping model
 INTRODUCTION:

Software development life cycle


(SDLC) is a structured process that
is used to design, develop, and test
good-quality software. SDLC, or
software development life cycle, is
a methodology that defines the
entire procedure of software
development step-by-step.The goal
of the SDLC life cycle model is to
deliver high-quality, maintainable
software that meets the user’s
requirements. SDLC in software
engineering models outlines the
plan for each stage so that each
stage of the software development
model can perform its task
efficiently to deliver the software at
a low cost within a given time
frame that meets users’
requirements.
 What is Software Development Life Cycle
(SDLC)?

SDLC is a process followed for software building within a software organization. SDLC
consists of a precise plan that describes how to develop, maintain, replace, and enhance
specific software. The life cycle defines a method for improving the quality of software and the
all-around development process.
 Stages of the Software
Development Life Cycle

SDLC specifies the task(s) to be performed at various stages by a software engineer or


developer. It ensures that the end product is able to meet the customer’s expectations and
fits within the overall budget. Hence, it’s vital for a software developer to have prior
knowledge of this software development process.
Prototyping Model

The Prototyping Model is one of the most popularly used


Software Development Life Cycle Models (SDLC models). This model is used
when the customers do not know the exact project requirements beforehand.
In this model, a prototype of the end product is first developed, tested, and
refined as per customer feedback repeatedly till a final acceptable prototype
is achieved which forms the basis for developing the final product.
Steps of Prototyping Model

Requirement Gathering: Collect user and stakeholder requirements.


Define Prototype Scope: Determine the focus areas for the prototype.
Develop Initial Prototype: Create a simple version highlighting key features.
User Evaluation: Present the prototype to users and gather feedback.
Refinement and Iteration: Improve the prototype based on feedback,
iterating as needed.
Formalize Requirements: Finalize and document system requirements using
insights from the prototype.
Develop Final Product: Build the complete system according to the finalized
requirements.
Testing and Validation: Test the system for compliance with requirements
and functionality.
Deployment and Maintenance: Deploy the system and provide ongoing
support.
Concept Of Prototyping Model
Advantages of Prototyping
Model

•Thecustomers get to see the partial product early in the life cycle. This ensures a
greater level of customer satisfaction and comfort.
•New requirements can be easily accommodated as there is scope for refinement.
•Missing functionalities can be easily figured out.
•Errors
can be detected much earlier thereby saving a lot of effort and cost, besides
enhancing the quality of the software.
•The developed prototype can be reused by the developer for more complicated
projects in the future.
•Flexibility in design.
•Earlyfeedback from customers and stakeholders can help guide the development
process and ensure that the final product meets their needs and expectations.
Disadvantages of Prototyping
Model

•Costly concerning time as well as money.


•Theremay be too much variation in requirements each time the prototype is
evaluated by the customer.
•Poor Documentation due to continuously changing customer requirements.
•It
is very difficult for developers to accommodate all the changes demanded by the
customer.
•There is uncertainty in determining the number of iterations that would be required
before the prototype is finally accepted by the customer.
•Afterseeing an early prototype, the customers sometimes demand the actual product
to be delivered soon.
•Developers in a hurry to build prototypes may end up with sub-optimal solutions.
The prototyping model should be
used when the requirements of
the product are not clearly
understood or are unstable.
The prototyping model can also
be used if requirements are
changing quickly.
Applications This model can be successfully
used for developing user
of Prototyping interfaces, high-technology
software-intensive systems, and

Model
systems with complex algorithms
and interfaces.
The prototyping model is also a
very good choice to demonstrate
the technical feasibility of the
product.

You might also like