|
|
 |
|
|
|
PROTOTYPINGArchitects make blueprints. The rest of us we pretend we know how to read them, and we can make out the basics, but architects realize that most people cannot properly envision the building from a technical document. Balsa wood models are much better, but they are hard to make. Why do architects bother with them? Because it's makes it possible for their clients to grasp what the finished building will look like. Nowadays, computer renderings are common for the same purpose. For software projects, I don't think there's any better way to explain the product than with a prototype. I also think that once the design is tangible, it is more likely to survive the software development process. It's one thing to cite a spec, and quite another to show a picture. People remember pictures better than a thousand words. Since my background is programming, it is easier for me to create prototypes than it is for other designers, especially HTML prototypes for websites or web applications. Even with a programming background, sometimes I just use graphics software to get the point across. Prototypes are quickly understood, and are just one reason my approach to user interface design gets results quickly.
|
|
NEW STUFF
ABOUT ADDUCIVE
CONSULTING SERVICES
|
You may also be
interested in this article,