The importance of software prototyping

Luís Filipe

Managing Partner YouX

What is software prototyping

In a generic way, we can define software prototyping as the process that allows you to create a visual model of the product or system whose development you intend to carry out.

Revisiting the history of software development helps us understand the use of prototyping. In the 60s of the last century, a development model was created that has remained popular to this day, the SLDC – Software Development Life Cycle.

The SDLC presented as a great advantage the segmentation of software production into different individual phases, which would work in a systemic way, with their inputs, processing and results that would pass to the next phase, after being verified and validated.

Its use revealed its limitations: it started from the wrong assumption that the development process is linear and that interactions between phases are exceptions.

This approach meant that the tangible components of the system were only available very late. On the other hand, any change that became necessary, for example, requested by the client, became difficult to meet without the expenditure of enormous resources.

It is in this context that in the 80s the Prototyping-Oriented Software Live Cycle emerged. This model does not introduce a break with the previous one, but rather complements it, making it more iterative. Prototyping starts to assume a central role.

As Connell and Shafer state, “ A software prototype is a dynamic visual model providing a communication tool for customer and developer that is far more effective than either narrative prose or static visual models for portraying functionality. It has been described as:

functional after a minimal amount of effort
a means for providing users of a proposed application with a physical representation of key parts of the system before system implementation.
flexible modifications require minimal effort
not necessarily representative of a complete system.”

(Connell JL, Shafer LB.: Structured Rapid Prototyping. Prentice Hall International, Yourdon Press, 1989)

The role of prototyping in software development is particularly important in cases where the client does not have well-defined project requirements, protyping allows creating a first prototype of the final product, testing it and improving it until its approval. From that moment on, the prototype developed becomes the basis of development for the final product.

“As some developers like to say, “If a picture is worth a thousand words, then a prototype is worth a thousand meetings.” “

John Doe

in, What is Prototyping in Software Development (and Why It's Important)

Advantages of software prototyping

Test and validate earlier: have a representation of the product without any code. Iterating with the prototype allows you to quickly and efficiently arrive at the best possible design.
Lets Impress investors and early adopters: a prototype clearly demonstrates an idea.
Easy, fast and cheap: prototypes are easy to develop, allowing you to explore different ideas without spending a lot of time or effort. When we move to code, we do so with confidence.
It also allows you to get feedback from the beginning of the development process which allows you to identify system problems before the coding phase begins.
Major usability problems can be identified even before the code, allowing them to be fixed at a very low cost.
Additionally, prototyping also stimulates creativity.
Interaction Foundation Design says :

Types of prototyping

There are several types of prototypes in software development and various nomenclatures as well. Looking to structure a little, we can say that they differ according to two major axes: the scope (how much they represent of the final system) and their degree of realism:

scope

Vertical prototypes: only some features are included but they are functional and can be tested under very realistic conditions, including real data binding) with the execution of real tasks.
Horizontal prototypes: they are not as functional as the first ones but include the entire system and therefore allow you to see how the different functionalities are articulated in the system.
Scenarios: has a reduced scope and functionalities, allows you to test the system by going through a certain script.

Realism

Low fidelity: little functionality and interaction, they are usually used to show the concept, layouts or design alternatives.
High fidelity: They are designed to demonstrate the interaction with the system, having a high degree of realism.

Prototyping Models

4 Types of Prototyping Templates

Rapid prototype: used to explore ideas and get feedback from the customer, rather than compromising the customer, the aim is to avoid necessary developments.
Evolutionary prototype: consists of a refinement of the initial prototype, which is improved and developed until it is finally accepted by the customer.
Incremental prototype: the final product is divided into several parts and prototyped individually. In the end they are put together neatly. This process reduces complexity.
Extreme prototypes: it is mainly used in web development and consists of 3 sequential phases:
1. a prototype is presented with all static pages in html
2. functional screens are made to simulate the process
3. All services are implemented and associated in the final portico.

Are you thinking of developing new interfaces or products or looking to improve existing solutions? Proceed safely. See our services .

The importance of software prototyping

Luís Filipe

What is software prototyping

Advantages of software prototyping

Types of prototyping

scope

Realism

Prototyping Models

RESEARCH | IDEATION

EXECUTION

MEMBER

RESEARCH
/IDEATION

EXECUTION

MEMBER

The importance of software prototyping

Luís Filipe

What is software prototyping

Advantages of software prototyping

Types of prototyping

scope

Realism

Prototyping Models

RESEARCH | IDEATION

EXECUTION

MEMBER

RESEARCH /IDEATION

EXECUTION

MEMBER

RESEARCH
/IDEATION