Prototypin G: Gattani Neha Brijmohan ROLL NO.14081 MBA-1

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 11

PROTOTYPIN

G
GATTANI NEHA BRIJMOHAN
ROLL NO.14081
MBA-1

What is Prototype?

Prototyping is the process of


quickly putting together a working
model (a prototype) in order to test
various aspects of a design,
illustrate ideas or features and
gather early user feedback.-

Prototyping
Prototyping

is an informationgathering technique

Prototypes

are useful in seeking user


reactions, suggestions, innovations,
and revision plans

Prototyping

may be used as an
alternative to the systems
development life cycle

Prototyping Objectives
The

objective of evolutionary
prototyping is to deliver a working
system to end-users
The development starts with those

requirements which are best understood.

The

objective of throw-away
prototyping is to validate or derive
the system requirements
The prototyping process starts with those

requirements which are poorly understood

Developing a Prototype:

Outline of the prototyping process


1.Requirement Gathering & Analysis
The user is interviewed in order to
know the requirements of the system.
2.Quick design
It is not a detailed design and
includes only important aspects of the
system which gives an idea of system to the
users.

Continued.
3.Build prototype
Information gathered from
quick design is modified to form the first
prototype which represents the working
model of the required system.
4.User Evaluation
Here , the proposed system is
presented to the user. To recognise its
strength & weakness.

Continued
5.Refining Prototype
Once the user evaluates the
prototype & if he is not satisfied, current
prototype is refined according to the
requirements.
6.Engineer product
Thus, user lastly accepts the
final prototype

THE PROTOTYPING PROCESS

Advantages
Reduces development time.
Reduces development costs.
Requires user involvement.
Developers
receive
quantifiable
user
feedback.
Facilitates system implementation since
users know what to expect.
Results in higher user satisfaction.
Exposes developers to potential future
system enhancements.

Disadvantages

This method can be used to avoid


documenting the requirements of the
system.

Management is required

Long term maintenance can be expensive

Uncertain design ideas

Information can be lost through so many

You might also like