numbering, design doc naming

I do. I very much like using numbered steps (1, 2, 3) to quickly identify
interaction processes in the beginning of a design project, with exceptions
and sub-cases pointed out along the way (1a, 2a, 3a). I do call them "use
cases", probably because of the time I've spent as a programmer.

It's a great way to get some initial thoughts going about how something will
actually work, before you even start with wireframes or anything. It's also
nice because you can collaborate with other people on them, and get things
worked out based on several different perspectives.

-r-

On 1/24/06, jackbellis.com <jackbellis at hotmail.com> wrote:
>
> [Please voluntarily trim replies to include only relevant quoted
> material.]
>
> A two part question:
> Does anyone else work with design documents that include steps with
> numbering such as "8-9a.3-9a.1"?
> Do you call the documents "use cases?"
> Thanks,
> www.jackbellis.com, www.usabilityInstitute.com
> ________________________________________________________________
> Welcome to the Interaction Design Association (IxDA)!
> To post to this list ....... discuss at ixda.org
> List Guidelines ............ http://listguide.ixda.org/
> List Help .................. http://listhelp.ixda.org/
> (Un)Subscription Options ... http://subscription-options.ixda.org/
> Announcements List ......... http://subscribe-announce.ixda.org/
> Questions .................. lists at ixda.org
> Home ....................... http://ixda.org/
> Resource Library ........... http://resources.ixda.org
>