We should have some guidelines for the next version of this document: Each use case shoul have: a) Intro: What is this ABOUT, this paragraph should make clear why this use case is distinct from the other use cases. b) Senario: What is the narrative STORY of this use case Each scenario should be required from have at least two example rules, no more than 5 c) Conclusion: I would also find a concluding paragraph which contains some natural language requirements as a conclusion I think this would give the whole document a more consistent look-and-feel. I will send a second mail with the concrete objections about 1.1,1.4,1.5, since this is a separate issue. best,axel -- Dr. Axel Polleres email: axel@polleres.net url: http://www.polleres.net/Received on Tuesday, 14 March 2006 17:09:39 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:33:27 GMT