%\includegraphics[width=110mm]{fig/math-universe-small}

     \includegraphics[width=110mm]{../../fig/jrocnik/math-universe-small}

   \>postcond \>: TODO - (Mind the following remark)\\ \end{tabbing}}

   \>postcond \>: TODO\\ \end{tabbing}}

 \begin{remark}

 %JR wie besprochen, kein remark, keine begründung, nur simples "nicht behandelt"

    Defining the postcondition requires a high amount mathematical 

    knowledge, the difficult part in our case is not to set up this condition 

 % \begin{remark}

    nor it is more to define it in a way the interpreter is able to handle it. 

 %    Defining the postcondition requires a high amount mathematical 

    Due the fact that implementing that mechanisms is quite the same amount as 

 %    knowledge, the difficult part in our case is not to set up this condition 

    creating the programm itself, it is not avaible in our prototype.

 %    nor it is more to define it in a way the interpreter is able to handle it. 

    \label{rm:postcond}

 %    Due the fact that implementing that mechanisms is quite the same amount as 

 \end{remark}

 %    creating the programm itself, it is not avaible in our prototype.

 %    \label{rm:postcond}

 % \end{remark}

 \paragraph{After specifieing the problem} we start to implement the method(s) of

 The methods represent the different ways a problem can be solved. This can

 the problem. The methods represent the different ways a problem can be solved,

 include mathematical tactics as well as tactics taught in different courses.

 this can include different mathematical tactics as well as different tactics

 Declaring the Method itself gives us the possibilities to describe the way of 

 taught in different courses.

 calculation in deep, as well we get the oppertunities to build in different

 rulesets.

 {\small

 07    rls'= e_rls, 

 07    rls = rls, 

 14   "empty_programm"

 14   "empty_program"

 }

 The above code is again very technical and goes hard in detail. But to document

 and present the neccessary steps follow up the description of the above code:

 The above code is again very technical and goes hard in detail. Unfortunataly

 most declerations are not essential for a basic programm but leads us to a huge

 range of powerful possibilities.

 \item[01..02] stores the method with the given name into the system under a global

 \item[01-02] this to lines store the method with the given name into the system

 reference.

 \item[03] here, the path is specifiet; which capitel this method is belonging to

 \item[03] specifies the topic under which the method can be used.

 \item[04-05] as the requirements for different methods can be different we 

 \item[04..05] as the requirements for different methods can deviant we 

 specify again the \emph{given} and the \emph{find} element.

 declare what is \emph{given} and and what to \emph{find} for this specific method.

 \item[06]

 \item[06] \emph{rewrite order} is the order of this rls, which one theorem of is

 \item[07]

 used for rewriting one single step.

 \item[08]

 \item[07] \texttt{rls} is the currently used ruleset for this method,

 \item[09]

 \texttt{e\_rls} specifies a

 \item[10]

 ruleset where conditions can be used within it.

 \item[11]

 \item[08] we can add this method to a predefined tree of calculations ore leave

 \item[12]

 it independend.

 \item[13]

 \item[09] \texttt{srls}, can be used to evaluate list expressions in the source

 \item[10] \texttt{prls} indicates predicates which can be used in model patterns.

 \item[11] \texttt{crls}, gives us the possibility for checking formulas 

 lementwise

 \item[12] \emph{error patterns} which are expected in this kind of method can be

 specified.

 \item[13] \texttt{crls}, declares the canonical simplifier for the specific method