[Sigia-l] Re: Sigia-l digest, Vol 1 #381 - 21 msgs

[Katrina]

I agree with Laura with respect to use cases: I have
found them to be very helpful in figuring out the
"nitty gritty of how the interaction design actually
works"--once you've mapped out the general
pages/screens of a site or application, there is still
a lot of work to do--and information/behavior that may
have been forgotten or left out, that doesn't become
apparent until you've gone through the sort of
rigorous thinking and detail that use cases demand. 

So perhaps it is not necessarily a question of
creating lighter use cases, but of developing them
later in the process to figure out missing details of
a proposed design (you can also use annotated process
flow diagrams to work out some of these details,
depending on the needs/requirements/style of the
team).

kpm


>Subject: Re: [Sigia-l] RE: Use cases and user
>centric design (was sitepath diagramming)
>Date: Wed, 22 Jan 2003 16:45:26 -0500
>From: "Laura Scheirer Quinn" 

>I find use cases invaluable, however, for the nitty
gritty of how the interaction design actually works. 
There's many things in a detailed site that aren't
easily spec-able in a page format (either in
wireframes or a description of a wireframe, for
instance).  Take a checkout process, for instance--
when you hit the buy button, there's still a whole lot
of user experience to go.  What happens if they've
given an invalid field entry?  Or the credit card
doesn't go through?  Or the item is out of stock after
all, now that you check it?  Use cases are great for
this stuff.  And it tends to be stuff that I take
responsibility for, that doesn't depend heavily on
client or user review.



__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com