Prototyping Model in Software Engineering: Methodology, Process, Approach

Prototyping Model in Software Engineering
Prototyping Model in Software Engineering

In this tutorial, you will learn

Software engineering prototyping model

Prototyping Model in Software Engineering: The prototype requires that prior to doing the development of actual software, a working prototype of the system ought to be built. A prototype is a toy execution of the system. A prototype as a rule ends up being an extremely crude version of the actual system, conceivable displaying limited functional abilities, low reliability, and wasteful execution when compared with actual software. In numerous occurrences, the customer just has an overall perspective on what is generally anticipated from the software product. In such a situation where there is an absence of point by point data regarding to the input to the system, the processing needs, and the output prerequisite, the prototyping model might be employed.

What is Prototyping Model?

Software engineering Prototyping Model is a software development model in which prototype is built, tried, and reworked until a satisfactory prototype is accomplished. It likewise creates base to produce the last framework or software. It works best in situations where the project’s necessities are not known exhaustively. It’s an iterative, trial and error technique which happens among developer and client.

Prototyping Model Phases

Prototyping Model has following six SDLC stages as follow:

Stage 1: Requirements gathering and analysis

A prototyping model beginnings with prerequisite analysis. In this stage, the prerequisites of the system are defined exhaustively. During the process, the users of the framework are met to interviewed what is their expectation from the system.

Stage 2: Quick design

The subsequent stage is a preliminary design or a quick design. In this stage, a straightforward design of the framework is created. Be that as it may, it’s not a complete design. It gives a brief idea of the framework to the user. The quick design helps in developing the prototype.

Stage 3: Build a Prototype

In this stage, an actual prototype is designed dependent on the data assembled from quick design. It’s a small working model of the necessary system.

Stage 4: Initial user evaluation

In this stage, the proposed framework is introduced to the customer for an initial evaluation. It assists with discovering the strength and weakness of the functioning model. Comments and idea are gathered from the client and gave to the developer.

Stage 5: Refining prototype

On the off chance that the user isn’t happy with the current prototype, you need to refine the prototype as indicated by the user’s feedback and ideas.

This stage won’t over until every one of the necessities indicated by the user are met. When the user is happy with the developed prototype, a last framework is developed dependent on the approved last prototype.

Stage 6: Implement Product and Maintain

When the last system is developed dependent on the last prototype, it is altogether tried and conveyed to production. The system goes through routine maintenance for minimizing downtime and prevent large-scale failures.

Types of Prototyping Models

Four types of Prototyping models are:

  1. Rapid Throwaway prototypes
  2. Evolutionary prototype
  3. Incremental prototype
  4. Extreme prototype

Rapid Throwaway Prototype

Rapid throwaway depends on the preliminary necessity. It is quickly developed to show how the necessity will look outwardly. The client’s feedback helps drives changes to the necessity, and the prototype is again created until the prerequisite is baselined.

In this strategy, a developed prototype will be discarded and won’t be a piece of the at last acknowledged prototype. This procedure is valuable for exploring thoughts and getting moment feedback for client prerequisites.

Evolutionary Prototyping

Here, the prototype developed is steadily refined dependent on client’s feedback until it is at last acknowledged. It assists you with saving time just as exertion. That is on the grounds that developing a prototype without any preparation for each interaction of the process can at times be disappointing.

This model is useful for a project which uses a new technology that isn’t surely known. It is likewise used for an unpredictable task where each usefulness should be checked once. It is useful when the prerequisite isn’t steady or not understood clearly at the underlying stage.

Incremental Prototyping

In incremental Prototyping, the eventual product is decimated into various small prototypes and developed individually. In the end, the various prototypes are merged into a single product. This strategy is useful to decrease the feedback time between the user and the application development team.

Extreme Prototyping:

Extreme prototyping technique is for the most part used for web development. It is comprises of three sequential stages.

  1. Basic prototype with all the existing page is available in the HTML format.
  2. You can simulate data process using a prototype services layer.
  3. The services are carried out and integrated into the last prototype.

Best practices of Prototyping

Here, are a couple of things which you should look for during the prototyping interaction:

• You should use Prototyping when the necessities are unclear

• It is essential to perform arranged and controlled Prototyping.

• Regular gatherings are essential to keep the project on schedule and stay away from expensive delays.

• The users and the designers ought to know about the prototyping issues and pitfalls.

• At a beginning phase, you need to approve a prototype and only at that time allow the team to move to the next stage.

• In software prototyping technique, you ought to never be afraid to change prior choices if new thoughts should be deployed.

• You should choose the proper step size for every version.

• Implement significant highlights early on that in the event that you run out of the time, you actually have a beneficial system

Advantages of the Prototyping Model

Here, are significant pros/advantages of using Prototyping models:

• Users are actively associated with development. Consequently, errors can be recognized in the underlying phase of the software development process.

• Missing usefulness can be identified, which assists with decreasing the risk of failure as Prototyping is additionally considered as a risk decrease activity.

• Helps colleague to communicate effectively

• Customer satisfaction exists because the client can feel the product at a beginning phase.

• There will be not really any possibility of software rejection.

• Quicker client feedback assists you with accomplishing better software development solutions.

• Allows the customer to analyze if the software code coordinates with the software particular.

• It assists you with discovering the missing usefulness in the framework.

• It additionally identifies the complex or difficult functions.

• Encourages innovation and flexible designing.

• It is a direct model, so it is straightforward.

• No need for specific specialists to build the model

• The prototype serves in as a reason for deriving a framework particular.

• The model assists with acquiring a superior comprehension of the client’s requirements.

• Prototypes can be changed and even discarded.

• A prototype likewise serves in as the reason for operational particulars.

• Prototypes may offer early preparing for future clients of the software system.

Disadvantages of the Prototyping Model

Here, are significant cons/disadvantages of Software engineering prototyping model:

• Prototyping is a lethargic and time taking process.

• The cost of developing a prototype is a total waste as the prototype is at last discarded.

• Prototyping may energize inordinate change demands.

• Some times clients may not be willing to participate in the iteration cycle for the more drawn out time term.

• There might be far numerous varieties in software necessities when each time the prototype is assessed by the client.

• Poor documentation because the prerequisites of the clients are changing.

• It is extremely hard for software developers to accommodate every one of the progressions demanded by the customers.

• After seeing an early prototype, the clients may think that the actual product will be conveyed to him soon.

• The customer may lose interest in the eventual outcome when the person isn’t happy with the underlying prototype.

• Developers who need to build prototypes quickly may end up building sub-standard development solutions.


• In Software Engineering, Prototype approach is a software development model in which a prototype is built, test and afterward revamped when required until an adequate prototype is accomplished.

• 1) Requirements gathering and analysis, 2) Quick design, 3) Build a Prototype, 4) Initial user evaluation, 5) Refining prototype, 6)Implement Product and Maintain; are 6 stages of the prototyping process

• Type of prototyping models are 1) Rapid Throwaway prototypes 2) Evolutionary prototype 3) Incremental prototype 4) Extreme prototype

• Regular gatherings are crucial for keep the task on schedule and stay away from costly delays in prototyping approach.

• Missing usefulness can be recognized, which assists with diminishing the risk of failure as Prototyping is additionally considered as a risk decrease activity in SDLC.

• Prototyping may encourage excessive change demands.


Software Engineering Tutorial for Beginners: Learn in 7 Days

What is Software Engineering? Definition, Basics, Characteristics

10 Steps to Become a Software Engineer/Developer

Software Engineer vs Software Developer: What’s The Difference?

SDLC: Phases & Models of Software Development Life Cycle

Thanks for reading! We hope you found this tutorial helpful and we would love to hear your feedback in the Comments section below. And show us what you’ve learned by sharing your projects with us.

salman khan

Written by worldofitech

Leave a Reply

RAD Model

What is RAD Model? Phases, Advantages and Disadvantages

Waterfall vs. Incremental vs. Spiral vs. Rad Model

Waterfall vs. Incremental vs. Spiral vs. Rad Model: Key Difference