network for data exchange in agriculture

It seems usefull to have some guidelines for introducing new use cases on our website. The discussion in Helsinki shows, that some questions are still open.

From my point of view, one of the important issue is the aim of the discussion about the use cases.
Do we only make a presentation of uses case to give the community a domain of discussion or do we intervent into the discussion and make some proposals?

This question affect the presentation of a use case too. The technique with wich we describe the processes and data models have an not negligible influence on the implementation. These goes from BPMN (made for SOA) to UML-Class-Diagramms (made for object-oriented programming).

Nevertheless we need tools the visualize the processes, and the representation should be understood by people with no technical background. So in one hand we have to fix several basic approachs how we want to descripe a use case, on the other hand, we have to give everybody enough room for outlining his ideas.

Based on these issues I make 2 proposals:

1) introduce in the use case template the field "State of Implementation":
These text field should make clear, how an existing implementation looks like and what are the ideas to improve or introduce a information flow. These field could make the border between description and the implementation of a use case clear.

2) establish guideline for use case
The guidelines should make different thinks clear:

- What are the basic facts?
- Who is the target audience?
- What is the aim of the presentation of a use case on our web side?
- What are the recommended tools