1 / 9

High fidelity prototyping

High fidelity prototyping. High-fidelity prototyping. Uses materials that you would expect to be in the final product. Prototype looks more like the final system than a low-fidelity version.

fhorvath
Télécharger la présentation

High fidelity prototyping

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. High fidelity prototyping

  2. High-fidelity prototyping • Uses materials that you would expect to be in the final product. • Prototype looks more like the final system than a low-fidelity version. • For a high-fidelity software prototype common environments include Macromedia Director, Visual Basic, and Smalltalk. • Danger that users think they have a full system

  3. High-fidelity prototyping • Can’t prototype everything • Horizontal: Look and feel of everything, but little functionality • Vertical: Few crucial pieces of functionality

  4. Mobile Hi-Fi – Tools • PC emulator • Supplied by most manufacturers (e.g. Nokia, Microsoft, etc.) • Or create your own (e.g. Flash, Java)

  5. PC – Be Warned • Text input (no keyboards) • Pointing device (no mice) • Portability (limited to lab evaluation) • Performance (PC faster than device) • Custom hardware (mobiles can have hardware not found on PC)

  6. Moving to Implementation • Evolutionary • Tidy up the prototype and release • Rarely a good idea • Revolutionary • Use the prototype as a specification • Re-implement from scratch

  7. Compromises in prototyping • All prototypes involve compromises • For software-based prototyping maybe there is a slow response? sketchy icons? limited functionality? • Two common types of compromise • ‘horizontal’: provide a wide range of functions, but with little detail • ‘vertical’: provide a lot of detail for only a few functions • Compromises in prototypes mustn’t be ignored. Product needs engineering

  8. Construction • Taking the prototypes (or learning from them) and creating a whole • Quality must be attended to: usability (of course), reliability, robustness, maintainability, integrity, portability, efficiency, etc • Product must be engineered • Evolutionary prototyping • ‘Throw-away’ prototyping

  9. Tool support - DENIM

More Related