The purpose of a prototype is to allow CLients of the software to evaluate developers’ proposals for the design of the eventual product by actually trying them out, rather than having to interpret and evaluate the design based on descriptions. Software prototyping provides an understanding of the software’s functions and potential threats or issues. Prototyping can also be used by end users to describe and prove requirements that have not been considered, and that can be a key factor in the commercial relationship between developers and their clients. Interaction design in particular makes heavy use of prototyping with that goal.
The process of prototyping involves the following steps:
Identify basic requirements
Determine basic requirements including the input and output information desired. Details, such as security, can typically be ignored.
Develop initial prototype
The initial prototype is developed that includes only user interfaces. (See Horizontal Prototype, below)
The customers, including end-users, examine the prototype and provide feedback on potential additions or changes.
Revise and enhance the prototype
Using the feedback both the specifications and the prototype can be improved. Negotiation about what is within the scope of the contract/product may be necessary. If changes are introduced then a repeat of steps #3 and #4 may be needed.
How we do it?
Identification of requirements, meeting or workshop
We value contact with potential clients, preliminary analysis of needs names for the right good of our services.
Present concept of the solution
After the initial analysis, there is time for a preparation of the highlevel concept of the solution, which becomes a basis fundamental for the Application Growth and will evaluate later.
The proof of concept is an introduction to the offer of detailed product design and build.
Product development and maintenance
Last but not least is the process of building the solution followed by Agile methodologies which ends with the product handover or maintenance.