W3C home > Mailing lists > Public > public-xg-prov@w3.org > January 2010

Re: requirements guidelines

From: Paul Groth <pgroth@gmail.com>
Date: Thu, 28 Jan 2010 16:30:14 +0100
Message-Id: <8EA9A48B-C2B6-4C5A-87EF-91AC50B1745F@gmail.com>
To: James Myers <jimmyers@ncsa.uiuc.edu>
Cc: "<public-xg-prov@w3.org>" <public-xg-prov@w3.org>
Sounds good to me. I'll rearrange them soon.
Paul


On Jan 28, 2010, at 16:24, "James Myers" <jimmyers@ncsa.uiuc.edu> wrote:

> Paul,
> I had suggested we start naming the requirements with an area specific
> prefix so we don't confuse them and can cross reference but I  
> haven't done
> anything to act on it. E.g. Attr-UR-1, Accs-UR1 or some such rather  
> than
> multiple UR-1's running around...
> Jim
>
> -----Original Message-----
> From: public-xg-prov-request@w3.org [mailto:public-xg-prov- 
> request@w3.org]
> On Behalf Of Paul Groth
> Sent: Thursday, January 28, 2010 8:58 AM
> To: public-xg-prov@w3.org
> Subject: requirements guidelines
>
> Hi All,
>
> I tried to distill from the minutes of last week's telecon a set of
> guidelines for requirements. These can be found here:
> http://www.w3.org/2005/Incubator/prov/wiki/Requirements#Requirements_Guide
> lines
>
> They are as follows:
> - Requirements should aim for parsimony.
> - Requirements should be specific to the dimension as possible
> - Requirements may not be illustrated in the exemplar use cases. If  
> this
> is the case the requirement should note this.
> - Technical requirements may be repeated across user requirements.  
> These
> will be collated in the end.
> - If a requirement impacts on another area please refer to that area.
>
> Are there any more suggestions for guidelines?
>
> Thanks,
> Paul
>
Received on Thursday, 28 January 2010 15:30:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 28 January 2010 15:30:03 GMT