lunes, 11 de mayo de 2015

Prototyping

A prototype is NOT a demo!

A prototype is a representation of all or part of a system that, although constrained in some way such as user confusion between the prototype and the final system, can be used for evaluation in the iterative development which is largely based on this tool.
Let's remember the step where we are [Evaluate the designs] within the iterative process watching the graph below:



Prototypes can help designers refine their ideas (implementation, "look and feel" and so on) and discover previously unknown issues. Also they can build empathy for users and they communicate to clients, users and designers.
This tool is really good in the process for design human-computer interfaces serving user needs. "One of the most productive uses of rapid prototyping to date has been as a tool for iterative user requirements engineering and human-computer interface design." [1]
We can distinguish between two types of prototypes:
  • Low fidelity prototypes, how can it be the Paper prototypes. These kind of prototypes are very cheap, easy and quick to make; and comply perfectly with the objectives of the task to be tested with the user. 
 
The one we did during the course

To simulate the interaction can be used what is known as chauffeured prototype, that implies to use a paper prototype in a given scenario and the designer manually demonstrates how the interface would respond to user actions.

  • High fidelity prototypes, how can it be Mock-ups (throw-away) and Software prototypes (not throw-away). There are different mock-ups tools availables depending on your target: Mobile [Justinmind, FLuidUI]; Web [Dreamweaver, Photoshop]; Multiplatform [Balsamiq]; Multipurpose [Powerpoint, Visio].
  • As our project is a mobile application, it is used Justinmind. It is a nice and easy to use tool (drag&drop tool) which allows to display a running prototype in a simulator or on the device itself.

Getting started with the tool :)


On the other hand, Software prototypes are not thrown away, they serve as a base container that gets extended with real content. They are done in an IDE such as Eclipse, Xcode, Visual Studio... 




[1] S. P. Overmyer: Revolutionary vs. Evolutionary Rapid Prototyping: Balancing Software Productivity and HCI Design Concerns. Center of Excellence in Command, Control, Communications and Intelligence (C3I), George Mason University, 4400 University Drive, Fairfax, Virginia.

No hay comentarios:

Publicar un comentario