W3C home > Mailing lists > Public > public-indie-ui@w3.org > June 2012

Use Cases and Requirements

From: Doug Schepers <schepers@w3.org>
Date: Wed, 13 Jun 2012 15:59:40 -0400
Message-ID: <4FD8F12C.9030304@w3.org>
To: Arthur Barstow <art.barstow@nokia.com>
CC: public-indie-ui@w3.org
Hi, folks-

As mentioned on today's telcon, I have taken the liberty to model the 
IndieUI WG's Use Cases and Requirements document on that of the Audio WG.

This model includes separate scenarios with priorities and derived 
requirements, and through the process of building up multiple scenarios, 
we consolidate and refine requirements that are shared across scenarios.

I put in a template page [1] earlier, and have now updated it to start a 
strawman example of a scenario (use case), to get the ball rolling (I 
tried to be realistic, but the scenario still needs work and 
discussion).  While I think it's best that we ultimately have a single 
person responsible for this document (where that person is not me...), 
at the start everyone should feel free to add scenarios and requirements 
themselves (e.g. please edit the wiki!).  I am happy to talk to anyone 
who needs some help getting started on this process.

Please note that requirements are derived from scenarios... don't put in 
requirements that do not have their basis in a scenario! Scenarios are 
useful for illustrating and evaluating the real-world needs of the spec, 
and for focusing us on pragmatic outcomes.

[1] http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requirements

Regards-
-Doug Schepers
W3C Developer Relations
Project Coordinator, SVG, WebApps, Web Events, and Audio WGs


On 6/13/12 3:07 PM, Arthur Barstow wrote:
>
> use cases
>
> <shepazu>
> [11]http://www.w3.org/2011/audio/wiki/Use_Cases_and_Requirement
> s
>
> [11] http://www.w3.org/2011/audio/wiki/Use_Cases_and_Requirements
>
> DS: I am working on the UCs wiki
>
> … based on the Audio WG's UCs work
>
> Rich: I like the priorities
>
> … who sets them?
>
> DS: the Audio WG decides, on calls
>
> … about the priorities over discussion related to versions
>
> … and this helps us identify the highest priority for v1
>
> … v1 is aimed at something that can be broadly implemented ASAP
>
> … This WG may choose to do something else
>
> <shepazu>
> [12]http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requiremen
> ts
>
> [12] http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requirements
>
> AB: UCs work with Touch Events spec was very useful
>
> … for capturing priorities
>
> … and to have a place to log UC and Reqs for v.next
>
> DS:
> [13]http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requiremen
> ts
>
> [13] http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requirements
>
> … Let me talk about Audio WG's UC work
>
> … We give each UC an ID
>
> … and then describe a story
>
> … For each UC we include some Notes as well as a Priority
>
> … For each UC we also document the related Requirements
>
> <andy> can't get back in
>
> <andy> The conference is restricted at this time
>
> … A UC's Notes can include some points of the group's consensus
> on the UC
>
> <andy> ok - I'll watch IRC then
>
> DS: we have noticed that some requirements can span more than
> one UC
>
> Rich: I like this
>
> Janina: I agree; this is awesome
>
> DS: Rich, can your UCs map to this structure?
>
> Rich: yes; thanks very much
>
> DS: well, it's the Audio WG that we need to thank ;-)
>
> Janina: yes, I like this a lot
>
> DS: I will try to fill out at least one UC and some Reqs before
> the next call
>
> … and include "real" data
>
> Janina: ok; great please do that
>
> … and Michael will continue to do the Hg work
>
> … I will try to get a draft CfP to Doug, Mike and Art by end of
> this week
>
> … Thanks all for a productive meeting!
>
> Summary of Action Items
>
> [End of minutes]
>
>
>
>
Received on Wednesday, 13 June 2012 19:59:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 13 June 2012 19:59:51 GMT