- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 Jun 2015 08:37:47 +0000
- To: public-secondscreen@w3.org
Separating use cases and requirements is indeed not an uncommon pattern, @louaybassbouss. The easiest way to find examples is probably to browse the list of published [technical reports](http://www.w3.org/TR/#w3c_all) and search for "use case" or "requirement". A few other examples for inspiration: * The [Packaged Web Apps (Widgets)](http://www.w3.org/TR/widgets/) spec has a separate [landscape](http://www.w3.org/TR/widgets-land/) and a separate [requirements](http://www.w3.org/TR/widgets-reqs/) document * [Use cases and requirements for Standardizing Responsive Images](http://www.w3.org/TR/respimg-usecases/) * [Web Audio Processing: Use Cases and Requirements](http://www.w3.org/TR/webaudio-usecases/) -- GitHub Notif of comment by tidoust See https://github.com/w3c/presentation-api/issues/68#issuecomment-107364539
Received on Monday, 1 June 2015 08:37:48 UTC