Scribd
Upload
65 views

What Is Prototyping?

Prototyping involves creating models or simulations of a system to help define requirements and identify needed changes before development. There are different types of prototypes based on their level of functionality and whether they are intended to be part of the final system. Prototyping allows for early user involvement to provide feedback and catch issues, making it well-suited for complex systems with significant user interaction where requirements are unclear. However, it can also increase costs and complexity if the scope expands beyond the original plan.

Uploaded by

Eric Musyoki
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
65 views

What Is Prototyping?

Prototyping involves creating models or simulations of a system to help define requirements and identify needed changes before development. There are different types of prototypes based on their level of functionality and whether they are intended to be part of the final system. Prototyping allows for early user involvement to provide feedback and catch issues, making it well-suited for complex systems with significant user interaction where requirements are unclear. However, it can also increase costs and complexity if the scope expands beyond the original plan.

Uploaded by

Eric Musyoki
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Prototyping

What is Prototyping?

As mentioned earlier a prototype is like a model or a simulation of a real thing.  In systems


analysis a prototype is a model of the system (or subsystem) under analysis [2].  A system can be
anything from the food ordering system at a restaurant to the air traffic control system of a major
airport. Prototypes of these systems can take many forms. They can be paper-based or computer-
based. They can model the entire system with real data or just a few screens with sample data. 

Prototyping is the process of developing prototypes . It is a methodology in its own right and a
technique and supplemental methodology to other methodologies. In this case, we will focus on
the ways in which prototyping is used as a technique and a supplemental methodology to the
systems development life cycle (SDLC).

A survey of MIS managers in Fortune 1000 firms [3] suggests that there are four prototyping
methodologies in use today which supplement the traditional systems development life cycle: 

1. Illustrative: produces only mockups of reports and screens.

2. Simulated: simulates some system functions but does not use real data or a database,
model not implemented. 

3. Functional: performs some actual system functions and uses real data and/or a database,
model not implemented. 

4. Evolutionary/incremental: produces model(s) that become part of the final operational


system.

5. Throwaway/exploratory- Once its purpose is fulfilled it is thrown away

Others suggest such categorizations as evolutionary versus throw-away.

Evolutionary in this case is similar to #4 mentioned above (sometimes known as operational


[8] ). It produces a model that evolves throughout the development of the system and eventually
becomes the final system. Throw-away (sometimes known as exploratory [8] , or expendable
[5]) would encompass the other three methodologies previously mentioned. A throw-away
prototype is just what it sounds like.. Once its purpose is fulfilled it is thrown away Discarded

Another way that prototypes are classified is by the fidelity of the prototype, or the degree to
which the prototype represents the appearance and interaction of the system.[4]  A low-fidelity
prototype is one that is quickly constructed to depict concepts, design alternatives, and screen
layouts. Medium-fidelity prototypes partially simulate the system interaction and functionality.
High-fidelity prototypes are fully interactive, simulating much of the functionality in the final
product.
Information system applications can be best achieved with the help of the Prototyping which
helps the developer to create a working model. Prototyping helps to give an idea about the
system but it doesn’t contain all the features or it doesn’t perform the necessary functions
which are needed for the final system. Stages in the prototyping like the customer
evaluations suggest the necessary additions and modifications which are to be made in the
system to make it more useful for the users. Prototyping process is said to be an iterative
process as it helps to fulfill the needs of the users and customers. As compared with the
other models or process Prototyping process can be implemented with less amount of
capital. It can be made up using actual paper works or some computer software’s which
generate the necessary reports. Following are the steps in Prototyping

The basic idea here is that instead of freezing the requirements before a design or coding can
proceed, a throwaway prototype is built to understand the requirements. This prototype is
developed based on the currently known requirements. By using this prototype, the client can get
an “actual feel” of the system, since the interactions with prototype can enable the client to better
understand the requirements of the desired system.  Prototyping is an attractive idea for
complicated and large systems for which there is no manual process or existing system to help
determining the requirements. The prototype are usually not complete systems and many of the
details are not built in the prototype. The goal is to provide a system with overall functionality.

Diagram of Prototype model:

Advantages of Prototype model:

 Users are actively involved in the development


 Since in this methodology a working model of the system is provided, the users get a
better understanding of the system being developed.
 Errors can be detected much earlier.
 Quicker user feedback is available leading to better solutions.
 Missing functionality can be identified easily
 Confusing or difficult functions can be identified
Requirements validation, Quick implementation of, incomplete, but
functional, application.
Disadvantages of Prototype model:

 Leads to implementing and then repairing way of building systems.


 Practically, this methodology may increase the complexity of the system as scope of the
system may expand beyond original plans.
 Its time consuming in a situation where user requirments are not very clear
 Incomplete application may cause application not to be used as the
full system was designed incomplete or inadequate problem analysis.

When to use Prototype model:  

 Prototype model should be used when the desired system needs to have a lot of
interaction with the end users.
 Typically, online systems, web interfaces have a very high amount of interaction with
end users, are best suited for Prototype model. It might take a while for a system to be
built that allows ease of use and needs minimal training for the end user.
 Prototyping ensures that the end users constantly work with the system and provide a
feedback which is incorporated in the prototype to result in a useable system. They are
excellent for designing good human computer interface systems.

You might also like