[use_cases] Proposed framework for organizing use cases

Dear Payments IG (Use Cases Task Force),

I have an action item [1] to review use case 3.1 (in [2]) and propose changes (to the template).

I’ve not done my action, but I’ve done something else that I would like to present to the group at the 25 February call, 
a first draft of:

   Organizing Web Payments Use Cases
   http://www.w3.org/2015/Talks/ij-usecases/

While I was working on a revision to 3.1, I found that I wanted to make explicit the relationship between this use 
case and other use cases. I believe others have felt similarly since the document already says things like
"For more information on what happens next, see the choosing a payment instrument use case.”

I also found that in order to keep the use case simple, I wanted to write down a description of a payment
flow as a sort of complementary explanation.

In the end I decided to spend my time on a framework for organizing the use cases that would (ideally):

 * Make it easier to understand the use cases because they would be understood as part of a (simple) payment model.
 * Make it easier to see how all the use cases fit together
 * Make it easier to determine whether use cases overlap ways that are not useful.
 * Make it easier to spot gaps in our use cases.

Manu let me know that there had already been some work on something like this [3] but I was not aware of
that work. 

I look forward to sharing the ideas with you and getting your feedback. If this framework proves useful and gains
support, then I will return to my action item. 

Thank you,

Ian

[1] https://www.w3.org/Payments/IG/track/actions/69
[2] https://dvcs.w3.org/hg/webpayments/raw-file/default/latest/use-cases/index.html
[3] https://lists.w3.org/Archives/Public/public-webpayments-ig/2015Jan/0006.html

[ACTION-69]

--
Ian Jacobs <ij@w3.org>      http://www.w3.org/People/Jacobs
Tel:                       +1 718 260 9447

Received on Wednesday, 25 February 2015 23:52:16 UTC