Hi Marc! Although having some very experienced community members here, who are able to come up with "requirements" that help to work on the web infrastructure - let's quote one of the most famous people (in Germany) working in the requirements development domain ... the term "users" refers to us, the community, using the site.
"User's don't give requirements. They provide information". If you ask for requirements, you might end up in getting answers that lead to the same design like it is available today. Only few people might come up with suggestions what might be better ... Thus, from the "requirements engineering point-of-view", it might be better to (also) ask for the usual tasks people do. Usually, this "cognitive walk-through" enables people to state what they are comfortable with - and what's less desired. If I remember correctly, Thorsten already started to explain how graphic requests and selection might work. I referred to the pages where we collected ideas concerning "brainstorming" (the idea collection Michael talked about in another thread). Maybe this can already be a starting point ... However, thanks for the structured approach. It already feels great to see that! Cheers, Christoph Am Donnerstag, den 18.11.2010, 06:43 -0500 schrieb Marc Paré: > Needed: Please feel free to add any individual team requirements for > the final Drupal based website. All requirements should be > non-specific. > ie. Instead of "a wiki to upload documents to" try "a web based > document > control system". We care about detailed requirements here rather than > proposed solutions. -- E-mail to [email protected] for instructions on how to unsubscribe List archives are available at http://www.libreoffice.org/lists/marketing/ All messages you send to this list will be publicly archived and cannot be deleted
