Strengths, Weaknesses and 6 Stages of the Model
Strengths, Weaknesses and 6 Stages of the Model

Strengths, Weaknesses and 6 Stages of the Model

Posted on

Prototype method is a system development technique that uses a prototype to describe the system so that the owner of the system has a specific picture of the system that will be created by the development team.

A prototype in Indonesian is called a prototype (prototype), and a prototype is the initial appearance of a system that describes the final appearance of the system.

An easy example, when you are building a house, the potential owner usually makes a drawing or even a small house that clearly explains what the house to be built later looks like. Well, this is an analogy of a prototype made.

The typical software development method is used when the customer is unable to explain or translate the system to be built.

Using the prototype, customers can discuss it with the development team (developers) to balance the realization or understanding of the system to be made, so that there is no misunderstanding in the process of creating the system / application / software later.

Want to know more details, just read the discussion Prototype method: strengths, defects, and stages of the prototype next.

About the prototype method

The prototype method is a development method by testing how a new application works.

The prototype becomes the initial description of the system and what the desired end result of the system will be.

In general, this method uses a continuous reaction process so that the system can function properly.

Whereas the prototype method according to Pressman (2002:40) is a customer and developer who communicate directly to explain the overall program goals and identify needs in its development.

Starting with the input, output format and the interface used, so that the design can be done easily, then the testing and evaluation stages are carried out.

The prototype method is able to avoid misunderstandings in the system development process between developers and users.

Because often the user cannot explain the big picture of the system to be built well.

With this method, users can easily discuss the system and standardize perceptions with the development team.

This corresponds to the purpose of the prototype method that you want to develop the model until it becomes a complete system.

Using this method, the system can be developed more easily and quickly and the costs are not very expensive.

Prototype method

Prototype method

The prototype method has three cycles as follows:

1. Listen to customers

This stage is the identification of the user’s needs, and this must be done so that the developers have information about the desires or problems that they encounter.

The obtained data information can be used as a basis for finding and developing methods for the next stage.

2. Build and review the mockup

When the need to create a system is collected, the next process is to make a prototype design according to the user’s needs, by following

The stages are as follows:

  • Design for the process flow on the system, starting with the inputs and outputs suggested by the customer.
  • Unified Modeling Language Design, or UMl for short, is a design that aims to define what systems are required and how to achieve them.
  • Interface design or interface display and various features requested by the customer.

3. Customer test drive models

This phase aims to test the system prototype and evaluate whether the system prototype is made according to the user’s needs.

If the results of the prototype test still do not meet the user’s needs, the developer must reformulate the prototype.

So that the prototype can be realized in the final system according to the target user.

Also Read: Understanding Globalization: Causes, Theories, 4 Characteristics and Effects

4. Prototype method stages

There are several stages in this prototype method, and some sources say that the prototype contains 3,4,5,6 or 7 stages.

It has at least 6 stages as follows.

The first stage: requirements gathering and analysis

The stages of this prototype start with a needs analysis, at this stage the system requirements are defined in detail.

In the process, the customer and development team will meet to explain in detail what kind of system the user wants.

The second stage: rapid design

The second stage is a simple design work that gives a brief description of the system to be built, and this builds on the discussion from step 1 at the outset.

Stage 3: Build a prototype (Build a prototype)

After the design is approved, the next step is to develop a prototype that will be used as a reference for the programmer team to make software or applications.

Stage 4: User evaluation (initial user evaluation)

At this point, the system made in the form of a prototype will be presented to the customer for evaluation.

Moreover, the customer will give comments and suggestions about what was previously provided.

Fifth stage: purification of the prototype

If the customer has no review history of the prototype made, the team can proceed to the next stage or stage six, but if the customer has a history of system improvement, stages 4-5 will continue to iterate until the customer agrees with the system to be made.

Stage 6: Product implementation and maintenance

In this final stage, the product will be created by programmers based on the final prototype, the system will be tested and delivered to the customer.

The next step is to enter into the maintenance phase so that the system runs smoothly without problems.

Advantages and disadvantages of the prototype method

There are several advantages in the method of developing an elementary-type system, among which are:

1. Advantages of the prototype method

This is it:

  • Save development time and cost
  • Involve the owner of the system so that system errors can be overcome from the beginning of the process
  • Helping team members communicate effectively
  • Customers are satisfied because they already have an overview of the system to be made
  • Implementation or use of the system is easier because the customer already knows the description of the system in advance
  • Ease of predicting the next evolution of the system
  • Allows customers to set up software that matches the system they are going to build

2. Disadvantages of the prototype method

Here are six disadvantages of the prototype method, which are:

  • Prototyping becomes a time-consuming method if the customer is not satisfied in the early stages
  • The customer continues to add to the system requirements, something like this will be done, which further complicates the making of the system.
  • The system will be impeded if communication between the two parties is not done effectively.
  • The prototype method can waste a lot of time when the customer is not satisfied at the first stage.
  • Customers can add requirements to the system, which further complicates system development.
  • System work can be delayed if the communication between the developer team and the customer is not good.

Read also: List of 4 countries in the Asian continent and their new capitals


The prototype method is a development method by testing how a new application works.

Using the prototype, customers can discuss with the development team (developers) the equation of perceptions or understanding of the system to be made, so that there is no misunderstanding in the process of creating the system / application / software later.

There are many methods that can be used to make this prototype, and the full discussion is as shown Prototype method: strengths, defects, and stages of the prototype on me.

Read :   Sword Master Youngest Son Capitulo 30 Espanol Webtoon
Gravatar Image
I am a person who likes to write and make information related to fruits, because I like and have a mango garden.