- From: Bohdan Andriyiv <bohdan.andriyiv@validbook.org>
- Date: Fri, 25 May 2018 15:23:58 +0300
- To: public-credentials@w3.org
- Message-ID: <CALqw9pUhnsjLkoyhojrXYd=duDyZC3im6HdzNjD0s8Ymue8AwQ@mail.gmail.com>
On the last CCG meetings, it was raised that there is a need to contribute Use Cases and User Stories for DIDs and VCs . I want to contribute a few (it will simultaneously help me discover more issues, Use Cases and User Stories for Validbook), but want to clarify a few things first. - Are there strict requirements to Use Case, User Story? I see there is an example for Use Case <https://docs.google.com/document/d/1wz8sakevXzO2OSMP341w7M2LjAMZfEQaTQEm_AOs3_Q/edit?usp=sharing>, is there a preferred way to write User Story (see templates *https://en.wikipedia.org/wiki/User_story#Common_templates <https://en.wikipedia.org/wiki/User_story#Common_templates>*)? When to write Use Case and when User Story? Is User Story in essence, a small, not detailed Use Case? Can we first write User Story and then it will grow into Use Case? - Is there priority between: - DID UCs - DID USs - VC UCs - VC USs? - What is the best way to contribute UCs/USs? After the recent wonderful training on editing ReSpec I can contribute right in this specification format, but maybe something like google sheet with links to google docs (a quick example - https://docs.google.com/spreadsheets/d/1ypQiNJKM5Kv2cDeK_dZVz5QX8_z_1WS8K7GnBCedzPs/edit?usp=sharing) will be better? Thanks, Bohdan -- Bohdan Andriyiv Chief Maintainer at Validbook Foundation
Received on Friday, 25 May 2018 12:24:26 UTC