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_Guidelines

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 14:59:00 UTC