W3C home > Mailing lists > Public > public-xg-socialweb@w3.org > July 2009

Re: User Stories "pre-conditions" profiles

From: Harry Halpin <hhalpin@ibiblio.org>
Date: Wed, 15 Jul 2009 13:53:22 +0100
Message-ID: <b3be92a00907150553x4b89f86eq7751d79991bbdf90@mail.gmail.com>
To: Christine Perey <cperey@perey.com>
Cc: public-xg-socialweb@w3.org
Since the text looks well-deeloped, I'd throw this somewhere in the wiki at:

http://www.w3.org/2005/Incubator/socialweb/wiki/RequirementsAndUseCases

under a section called "Preconditions and Profiles"


On Wed, Jul 15, 2009 at 1:45 PM, Christine Perey<cperey@perey.com> wrote:
> Hello,
>
> Soren and I have exchanged a few e-mails and the text below is ready for
> review/discussion/comments.
>
> Harry or Tim Anglade: Is there a particular place/page on the wiki on which
> this should be posted for editing and future use?
>
>
> Christine
>
> Spime Wrangler
>
> cperey@perey.com
>
> mobile (Swiss): +41 79 436 68 69
>
> from US: +1 (617) 848 8159
>
> from anywhere (Skype): Christine_perey
>
>
>
>
> PRE-CONDITION PROFILES:
>
> To fully describe a user story/use case, we need to include the “properties”
> or conditions of the actors involved and the infrastructure between them and
> their objectives.
>
> Each user story should have some information about the device and
> infrastructure the actors use, respectively, and the data input and outputs
> available for each actor involved.
>
> Abbreviations may be used to refer to generic pre-condition profiles, namely
> we propose these two profiles abbreviations and their definitions:
>
> ''desktop''
>
> the user has access to a machine on which he/she:
>
> can freely install software as standalone applications, in-browser
> applications, widgets or otherwise;
> the machine has unlimited computational power, storage capacity, and
> uninterrupted, high-bandwidth, low-cost, and potentially secure Internet
> connectivity;
> keyboard and mouse are used as input devices and a large user display is
> available;
> the ''desktop'' machine typically supports multiple accounts and may be used
> by several members of a household or business;
> it is not continuously attached to the user which is described in the use
> case
>
> ''mobile''
>
> the user has access to a machine on which he/she can:
>
> ·         run restricted applications in a browser (which do not always
> comply with W3C MWI guidelines) or as sandboxed applications;
>
> ·         in addition to the social network use case, the device may be used
> (designed) for telephony and SMS as well and provides an integrated software
> infrastructure for calendar and contact management;
>
> ·         the machine has limited computational power, limited storage,
> intermittent, low-bandwidth, typically tariffed/pay as you go, and
> potentially secure Internet connectivity;
>
> ·         when using an IP-based service between this user and another user
> or service provider there may one or more mobile network operators whose
> infrastructures and policies may including transcoding web pages, filtering
> for age-appropriate content, and blocking of certain Web services;
>
> ·         the user inputs through a restricted keyboard, with gestures or
> via a touch screen;
>
> ·         the output device is highly variable ranging from a small,
> low-resolution screen to a pico-projector or sound / vibration alarm;
>
> ·         through embedded sensors, the device can relate itself, the user,
> and the environment to one another, and makes the readings such as,
> potentially, location, temperature, pollution, activity, proximity of other
> users or devices available to the application layer;
>
> ·         the ''mobile'' machine is typically engineered to suit a single
> user who is carrying the device continuously
>
>
Received on Wednesday, 15 July 2009 12:54:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:39:08 UTC