Turning an Abstract Function into a Concrete Function

This mode of writing gives the basic structure of such a mapping but tells nothing about the details how such a function works. To transform such an abstract connection into a concrete working function one has therefore to make additional assumptions, e.g.:


$\displaystyle POP$ $\textstyle \subseteq$ $\displaystyle RealNumbers$ (3.3)
$\displaystyle ChR$ $\textstyle \subseteq$ $\displaystyle RealNumbers$ (3.4)
$\displaystyle \textbf{mul}$ $\textstyle :$ $\displaystyle RelNumbers \times RealNUmbers \longmapsto RealNumbers$ (3.5)
$\displaystyle \textbf{add}$ $\textstyle :$ $\displaystyle RelNumbers \times RealNUmbers \longmapsto RealNumbers$ (3.6)
$\displaystyle mul$ $\textstyle :=$ $\displaystyle multiplication$ (3.7)
$\displaystyle add$ $\textstyle :=$ $\displaystyle addition$ (3.8)
$\displaystyle \textbf{f1}$ $\textstyle =$ $\displaystyle add(POP, mul(POP, ChR))$ (3.9)

Figure 3.5: Turn an abstract function into a concrete function
\includegraphics[width=3.5in]{simple_dependency_constructed.eps}

This can again be represented in a diagram by opening the box of the dependency $f1$ as abstract function and filling the content of the f1-box up with already known functions like $add()$ and $mul()$. Doing this we give the abstract function $f1$ an operational meaning (cf. figure 3.5).

Gerd Doeben-Henisch 2009-12-09