On Friday 16 May 2008 03:31:16 Sachendra Yadav wrote:
> Is there a concrete distinction between use cases and user scenarios?

A use case is a description of how a user might use an application to complete 
a specific task and can vary in the application-specific detail from 
simple "pseudo-code" descriptions to click-level interaction.  I've also 
heard them described as the "correct answer" for a task.  They are used in 
software engineering as a way of describing, documenting, and testing system 
functionality.  

Use scenarios describe the greater context of a task including the conditions, 
motivation, and environment of the task for a particular user group.  These 
usually include all the details interaction designers need to understand what 
the user is trying to do and what they need.  Most developers have never 
heard of a use scenario, but will adapt use cases to include this rich, 
contexual user information.

I've noticed that some IxDers tend to use both cases and scenarios when they 
actually mean use scenarios, usually the ones who have the most 
developer-designer experience.  I've noticed myself slip when I talk to 
developers; since they usually aren't aware of use scenarios or the 
difference between cases and scenarios, they use both interchangably.  I 
guess I unconciously switch my language so they know what I'm talking about.

-- 
Celeste 'seele' Paul
www.obso1337.org
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [EMAIL PROTECTED]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help

Reply via email to