Re: Use Cases wiki pages

I worded my sentence poorly. I meant to say that you suggested we could do 
without use cases if we have user stories.
Thanks for clarifying.
--
Arnaud  Le Hors - Senior Technical Staff Member, Open Web Standards - IBM 
Software Group




From:   "Ralph TQ [Gmail]" <rhodgson@topquadrant.com>
To:     Arnaud Le Hors/Cupertino/IBM@IBMUS
Cc:     public-data-shapes-wg@w3.org
Date:   11/04/2014 02:37 PM
Subject:        Re: Use Cases wiki pages



Arnaud,

Correction and expansion of what I said:

I don't know whether what you started should be folded into that, Ralph 
suggested at the meeting that we could not develop use cases if we have 
stories.

Stories should proceed Use Cases. A Use Case is one way to write a 
requirement but not the only one. Requirements of the MUST, SHALL, COULD, 
MAY kind are what I prefer for this kind of work. A use case is a “case of 
use of a system” and is a software development work-product, or it is 
another term for user scenario.  But if we really just intend a use case 
to be a user scenario then they are kind of like stories, but not as 
powerful as stories can be. We still need the "drama” aspect to reveal the 
pain points, challenges and happy or not outcomes. I would prefer 
therefore to have stories and requirements such as:

REQ-123: The specification language of SHAPES MUST enable constraints to 
be addressable
RATIONALE: A number of justifications can be stated: (a) to report why a 
constraint violation has failed, a reference to a constraint needs to be 
given; (b) …
EXAMPLE: 
RELATES TO: <another requirement>
WAS INFLUENCED BY: <some story>
GIVES RISE TO: <another requirement>
DECOMPOSES INTO: <sub-requirement>, ...


Ralph Hodgson, @ralphtq
TopQuadrant, Inc., www.topquadrant.com @TopQuadrant


On Nov 4, 2014, at 4:34 PM, Arnaud Le Hors <lehors@us.ibm.com> wrote:

We agreed at the meeting that we should move the User Stories that we 
captured on the piratepad during the meeting to a wiki page so everybody 
could keep working on them, I took the action item to make that move and 
have now done so: 

https://www.w3.org/2014/data-shapes/wiki/User_Stories 

I don't know whether what you started should be folded into that, Ralph 
suggested at the meeting that we could not develop use cases if we have 
stories. I'd rather we minimize the number of different documents we have 
to manage. Eventually we will want to publish one Note with all our use 
cases and requirements so I think we might as well start that way. 

I also suggest all comments be sent to the mailing list rather than using 
the Discussion tab of the wiki. Otherwise it becomes really difficult to 
keep track of everything.

Thanks. 
--
Arnaud  Le Hors - Senior Technical Staff Member, Open Web Standards - IBM 
Software Group


Holger Knublauch <holger@topquadrant.com> wrote on 11/04/2014 03:05:39 AM:

> From: Holger Knublauch <holger@topquadrant.com> 
> To: public-data-shapes-wg@w3.org 
> Date: 11/04/2014 03:08 AM 
> Subject: Use Cases wiki pages 
> 
> I took the liberty to start a couple of wiki pages to capture Use Cases
> 
>      https://www.w3.org/2014/data-shapes/wiki/Use_Cases

> 
> It currently only links to two stories, which are incomplete - I plan to 

> fill in more details tomorrow. I just thought I use this opportunity to 
> get the ball rolling.
> 
> I suggest we create one page for each of the stories collected in the 
> pirate pad during the meeting, and others that seem relevant. Having a 
> separate page for each should provide enough room to thoroughly discuss 
> and annotate each story.
> 
> I hope this makes sense... if it does, should there be a link to that 
> Use_Cases page from the main page?
> 
> Holger
> 
>