Edge-Case Scenario


Of course, there is a third type of scenario: the edge case. Programmers will naturally emphasize edge cases, but they can largely be ignored during the product's design. This doesn't mean that the function can be omitted from the program, but it does mean that the interaction needed for them can be designed roughly and pushed way into the background of the interface. Although the code may succeed or fail in its ability to handle edge cases, the product will succeed or fail in its ability to handle daily use and necessary cases.

If a user performs a task frequently, its interaction must be well crafted. Likewise, if a task is necessary but performed infrequently, its interaction, although designed with different objectives, must still be well designed. Tasks that are neither necessary nor frequent simply don't require careful design. Time and money are never available in unlimited quantities, so this is the place to conserve our resources safely and concentrate them where they do the most good. We must provide for all scenarios, but we need to design only for those that are important or that will occur frequently.

graphics/kolam.gif

Personas, goals, and scenarios are the heavy hitters in our design corner. Before moving on to a scenario case study, I'd like to mention a few other useful design concepts: inflecting the interface, perpetual intermediates, vocabulary, brainstorming, and lateral thinking.



Inmates Are Running the Asylum, The. Why High-Tech Products Drive Us Crazy and How to Restore the Sanity
The Inmates Are Running the Asylum Why High Tech Products Drive Us Crazy &How to Restore the Sanity - 2004 publication
ISBN: B0036HJY9M
EAN: N/A
Year: 2003
Pages: 170

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net