## Please put instances of this page in the appropriate task folder, e.g. Tasks/X/Y/DesignDocumentation
## Headline such as "Design of X.Y Backup Requirements"
= Design of "Uncover needed changes from the users perspective" Task =
## Add detailed explanation of the solution to this task. That is, how things are meant to work.

## This may include UML diagrams, schematics describing architecture etc. attached like this:
## Link to original: [http://merkur/svn/doms/trunk/MODULE/docs/MyPackageDiagram.dia]
## png on the wiki page: http://merkur/svn/doms/trunk/MODULE/docs/MyPackageDiagram.png

The analysis will be carried out using open ended questions, the overall goal is to leverage the superior knowledge of work flow that is inherent in the user-base.

== Prerequisites and Design Decisions ==
## Describe any prerequisites are important for this design, e.g.:
## Requirements that must be met by other systems, users, etc.
## Description and background/reason for non-trivial design decisions.

Access to the users as a partner in the design process, the idea is to let the user describe and design what they need.

Time end manpower to evolve the design in an iterative fassion.


=== Required Software and Modules ===
## Describe any required 3rd party software, libraries, other code modules in the project to make this design work.

Maybe a mock-up tool for the later stages of the process, otherwise pen and paper.

== Resources ==
## List links to documents, wiki pages etc. that are relevant to this design document.
## * [:LinkToMyRessource:Use class diagram xx]
## * [:LinkToMyVersionControlledDocument:Link to 3rd party library documentation.]