Scribd
Upload
14 views4 pages

Prototyping

Prototyping is an early mockup of software used to visualize the system's design and functionality, primarily focusing on user interface aspects. There are several types of prototyping, including incremental, evolutionary, and throwaway/rapid prototyping, each with its own approach to gathering client feedback and refining requirements. While prototyping allows for early identification of issues and user involvement, it can also lead to rushed requirements analysis and potential feature creep.

Uploaded by

Jerome k-Jerome
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
14 views4 pages

Prototyping

Prototyping is an early mockup of software used to visualize the system's design and functionality, primarily focusing on user interface aspects. There are several types of prototyping, including incremental, evolutionary, and throwaway/rapid prototyping, each with its own approach to gathering client feedback and refining requirements. While prototyping allows for early identification of issues and user involvement, it can also lead to rushed requirements analysis and potential feature creep.

Uploaded by

Jerome k-Jerome
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/ 4

Prototyping

A prototype is a mockup of a software in its earliest form. It is


mainly used in the design stage to show how a system will look
and work.
● It is usually focused on the user interface, rather than any
data structures
● It used so that the client can get a feel for the system
before it is developed
● The client is able to compare the prototype with the
requirements specifications
● The client can also describe their requirements more
clearly since they can see how the system essentially
looks like
Prototyping has several types:

Incremental prototyping
This type takes an iterative approach in that order:
1. requirements are specified
2. an initial prototype is developed
3. the prototype is reviewed
4. the requirements are clarified
5. the prototype is improved based on feedback.

● Each prototype will build upon the previous one and


include more functionality until a final product is built
● At each stage, only clearly understood requirements are
developed
● Each prototype can can be functional and used by the
client until the next iteration is ready, therefore allows the
client to make suggestions on what features to add to the
prototype

Evolutionary prototyping
This follows a similar pattern to incremental prototyping in
that it is iterative. However, there is no requirements
specification but rather a goal or aim:
● Both the analyst and the developer begin the project
by brainstorming ideas
● The developer will start working on some of the best
ideas so far, whilst the analyst discusses with the
client
● After a few days, the analyst and developer will
compare notes: the developer will demonstrate how
they have implemented ideas, and the analyst will
talk about what the client has said
● Following the discussion, the developer will continue
with development, focusing on the client’s needs that
are understood most clearly, while the analyst will get
feedback from the client and get more clarifications
● These steps will continue until the product evolves
from a goal, to a usable software
This method is mainly used in startups or when new ideas are
being experimented with.
Throwaway/rapid prototyping
Here, the prototype will never become part of the final model,
but instead will be discarded.
● A loosely working model is created following a short
investigation, with the aim being getting something real to
the client asap for feedback to assess how the
requirements are being met
● This enables the requirements to be fine-tuned early in the
process, which is more cost effective than trying to make
changes later

The advantages and disadvantages of


prototyping
Advantages Disadvantages
Problems can be identified Requirements analysis may
earlier before it becomes very be rushed, meaning that the
costly to make changes prototype doesn’t reflect much
of what the end user was
expecting
Requirements can be With rapid prototyping, the
modified as the clients will be process might be rushed,
giving feedback cafeteria which leads to design flaws or
each prototype errors that may be carried
forward to the final system
The end users will be involved When users see the
more in the process prototypes, they often might
get lots of ideas about
features they want to be
added, which leads to
disappointment if these
features are not implemented.
This is known as feature
creep
If the prototype is The costs of developing a
evolutionary, this means that prototype are often high
it is easier to get used to
using parts of the system
before having to use the
whole system

You might also like