doc/krempler/intro-ak.tex
changeset 2157 522ecf7b76e6
parent 2141 68133acbea17
child 2168 64f238fb00dd
equal deleted inserted replaced
2156:aa25d72a23a2 2157:522ecf7b76e6
    83 
    83 
    84 
    84 
    85 \subsection{Related Projects and Products}
    85 \subsection{Related Projects and Products}
    86 To further illustrate the concept of \isac{}, a short comparison with related projects, products and technologies will be given, highlighting common grounds and substantial differences.
    86 To further illustrate the concept of \isac{}, a short comparison with related projects, products and technologies will be given, highlighting common grounds and substantial differences.
    87 
    87 
    88 \subsubsection{Learning Software}
    88 \subsubsection{Educational Software}
    89 %educational ...
       
    90 A wealth of learning software has become available over the past decades, ranging from simple flashcard-like programs to elaborate interactive systems. An overview of readily available software is given in \cite{www:EduMath}.
    89 A wealth of learning software has become available over the past decades, ranging from simple flashcard-like programs to elaborate interactive systems. An overview of readily available software is given in \cite{www:EduMath}.
    91 
    90 
    92 \begin{description}
    91 \begin{description}
    93 \item[Common grounds:] \isac{} can be regarded as a math learning software insofar as we share the goal of extending the users' knowledge and ability to solve mathematical problems. We also share the methods of both presenting knowledge and practising examples in an interactive way.
    92 \item[Common grounds:] \isac{} can be regarded as a math learning software insofar as we share the goal of extending the users' knowledge and ability to solve mathematical problems. We also share the methods of both presenting knowledge and practising examples in an interactive way.
    94 \item[Major differences:] Most learning software works from pre-defined libraries of examples and lessons, and guides the user along didactically sophisticated, but fixed paths of interaction. \isac{} is extensible in both respects, offering support and learning experience even for user's examples not previously known to the system. Moreover, \isac{}'s paths of interaction are designed to be composed of so-called Dialog Atoms \ref{}, providing for user guidance configurable by a supporting teacher or even automatically adapting itself to the learner's behaviour.
    93 \item[Major differences:] Most learning software works from pre-defined libraries of examples and lessons, and guides the user along didactically sophisticated, but fixed paths of interaction. \isac{} is extensible in both respects, offering support and learning experience even for user's examples not previously known to the system. Moreover, \isac{}'s paths of interaction are designed to be composed of so-called Dialog Atoms \ref{}, providing for user guidance configurable by a supporting teacher or even automatically adapting itself to the learner's behaviour.
   115 A quotation from an internet-forum illustrates the problem:
   114 A quotation from an internet-forum illustrates the problem:
   116 \begin{quotation}
   115 \begin{quotation}
   117 Q: Hi, Can Mathematica show the steps that make to arrive at the answer, in a integration
   116 Q: Hi, Can Mathematica show the steps that make to arrive at the answer, in a integration
   118 
   117 
   119 A: Nope, sorry.  
   118 A: Nope, sorry.  
   120 Mathematica doesn't do integrals like humans do. You really don't want to see what route it takes to get an answer. \footnote{http://forums.wolfram.com/student-support/topics/7921, nov-2004}
   119 Mathematica doesn't do integrals like humans do. You really don't want to see what route it takes to get an answer.\footnote{http://forums.wolfram.com/student-support/topics/7921, nov-2004}
   121 \end{quotation}
   120 \end{quotation}
   122 Efforts to present intermediate results have been taken only recently. \isac{}, on the other hand, concentrates on making the process of solving transparent to the user. \isac{}'s mathematical knowledge is coded in the same rules and propositions used in teaching math and stored in a knowledge base browsable and comprehensible by the user. \isac{}'s computational algorithms are expressed using these rules and stored in so-called Methods \ref{}, which are accessible to the user as well. This provides not only for transparency, but also the flexibility to extend the knowledge used in obtaining a result and even changing the very way how a solution is obtained. \isac{}'s interactive tutoring capabilities going far beyond mere presentation of examples are based on this flexible concept.
   121 Efforts to present intermediate results have been taken only recently. \isac{}, on the other hand, concentrates on making the process of solving transparent to the user. \isac{}'s mathematical knowledge is coded in the same rules and propositions used in teaching math and stored in a knowledge base browsable and comprehensible by the user. \isac{}'s computational algorithms are expressed using these rules and stored in so-called Methods \ref{}, which are accessible to the user as well. This provides not only for transparency, but also the flexibility to extend the knowledge used in obtaining a result and even changing the very way how a solution is obtained. \isac{}'s interactive tutoring capabilities going far beyond mere presentation of examples are based on this flexible concept.
   123 
   122 
   124 In contrast to most available CAS, \isac{} is a networked application, allowing for mathematical knowledge and example libraries being shared across the internet.
   123 In contrast to most available CAS, \isac{} is a networked application, allowing for mathematical knowledge and example libraries being shared across the internet.
   125 
   124 
   128 While CAS can be used for learning purposes insofar as they facilitate exploration by taking the burden of calculation off the user, \isac{} can actively influence user interaction to achieve pedagogic goals.
   127 While CAS can be used for learning purposes insofar as they facilitate exploration by taking the burden of calculation off the user, \isac{} can actively influence user interaction to achieve pedagogic goals.
   129 \end{description}
   128 \end{description}
   130 
   129 
   131 The following programs are mentioned for their wide-spread use in educational and scientific institutions:
   130 The following programs are mentioned for their wide-spread use in educational and scientific institutions:
   132 \begin{description}
   131 \begin{description}
   133 \item[Mathematica] \cite{wolfr:mat}, \cite{www:Mathematica} boasts extensive comuputational capabilities, both symbolic and numeric. Mathematica started adding user-transparency by offering display of intermediate results and even the rules applied for differentiation.
   132 \item[Mathematica\footnote{http://www.wolfram.com/products/mathematica/index.html}] \cite{wolfr:mat} boasts extensive comuputational capabilities, both symbolic and numeric. Mathematica started adding user-transparency by offering display of intermediate results and even the rules applied for differentiation.
   134 \item[Derive] \cite{derive}, \cite{www:Derive} is a intentionally compact program running on smaller machines and even hand-held calculators. Derive started adding access to intermediate results - called display step - as of version 6.
   133 \item[Derive\footnote{http://www.derive-europe.com/main.asp}] \cite{derive} is an intentionally compact program running on smaller machines and even hand-held calculators. Derive started adding access to intermediate results - called display step - as of version 6.
   135 \item[MathCad] \cite{www:mathCAD} has its strengths in presentation and integrating a calculation with descriptive text and figures.
   134 \item[MathCad\footnote{http://www.mathcad.com}] has its strengths in presentation and integrating a calculation with descriptive text and figures.
   136 \end{description}
   135 \end{description}
   137 
   136 
   138 \subsubsection{Theorem Provers}
   137 \subsubsection{Theorem Provers}
   139 \begin{description}
   138 \begin{description}
   140 \item[Common grounds:] Theorem provers apply the abstract logic of proofs to a problem, in a step-by-step manner with a high degree of interactivity. 
   139 \item[Common grounds:] Theorem provers apply the abstract logic of proofs to a problem, in a step-by-step manner with a high degree of interactivity.  \isac{} implicitly proves that result of a calculation is correct in the sense of the original problem. \isac{} does so by constructing the result of a calculation by applying theorems proven by the theorem prover Isabelle \cite{Isa-intro}.
   141 %WN \sisac is designed to be responsible for correct results, too: it constructs the result of a calculation applying theorems proven by the theorem prover Isabelle \cite{Isa-intro}.
   140 %WN \sisac is designed to be responsible for correct results, too: it constructs the result of a calculation applying theorems proven by the theorem prover Isabelle \cite{Isa-intro}.
   142 %----
   141 %----
   143 The same logic is used by \isac{} to prove that the result of a calculation is equivalent to the originally specified problem. \isac{} uses the high-order logic (HOL) of the theorem prover Isabelle \cite{Isa-intro}.
   142 %AK The same logic is used by \isac{} to prove that the result of a calculation is equivalent to the originally specified problem. \isac{} uses the high-order logic (HOL) of the theorem prover Isabelle \cite{Isa-intro}.
   144 %----
   143 %----
   145 \item[Major differences:] A theorem prover tries to answer the question 'Is the theorem true?'. A theorem prover's answer is yes or no. 
   144 \item[Major differences:] A theorem prover tries to answer the question 'Is the theorem true?'. A theorem prover's answer is yes or no. 
   146 %WN \isac{} tries to solve a problem, i.e. \isac{}'s answer is a ...
   145 \isac{} tries to solve a problem. \isac{}'s answer is a mathematical object called result, as with a CAS.
   147 %----
       
   148 \isac{} tries to simplify the original problem. \isac{}'s answer is a mathematical object called result, as with a CAS.
       
   149 %----... nur fuer solve, simplify
       
   150 
       
   151 \end{description}
   146 \end{description}
   152 
   147 
   153 \subsubsection{Expert Systems}
   148 \subsubsection{Expert Systems}
   154 \begin{description}
   149 \begin{description}
   155 \item[Common grounds:] \isac{}'s Knowledge Base could be regarded as a simple expert system for mathematical knowledge.
   150 \item[Common grounds:] \isac{}'s Knowledge Base could be regarded as a simple expert system for mathematical knowledge.
   158 
   153 
   159 
   154 
   160 \subsubsection{Standards and Tools Used}
   155 \subsubsection{Standards and Tools Used}
   161 Several evolving technologies are used in the \isac{} system, with their development closely observed and in some cases cooperatively influenced by \isac{}:
   156 Several evolving technologies are used in the \isac{} system, with their development closely observed and in some cases cooperatively influenced by \isac{}:
   162 \begin{description}
   157 \begin{description}
   163 \item[XML]\cite{}, an open standard for desription of structured data, is used on all interfaces to the outside world. With limited resources of the \isac{} project, open standards facilitate cooperation with other projects and the use of tools already available.
   158 \item[XML\footnote{http://www.w3.org/TR/REC-xml}], an open standard for desription of structured data, is used on all interfaces to the outside world. With limited resources of the \isac{} project, open standards facilitate cooperation with other projects and the use of tools already available.
   164 \item[MathML]\cite{}, a XML language for describing mathematical objects, is used both for processing and rendering of formulae. Technology for processing MathML is not widely available at the moment, but evolving rapidly.
   159 \item[MathML\footnote{http://www.w3.org/TR/MathML2/}], a XML language for describing mathematical objects, is used both for processing and rendering of formulae. Technology for processing MathML is not widely available at the moment, but evolving rapidly.
   165 \item[MoWGLI] \cite{mowgli_home}, \cite{isac-mowgli2} aims at integrating and evolving existing standards to enhance accessibility and usability of mathematical information in the WWW.
   160 \item[MoWGLI\footnote{http://www.mowgli.cs.unibo.it/}] \cite{isac-mowgli2} aims at integrating and evolving existing standards to enhance accessibility and usability of mathematical information in the WWW.
   166 \item[Dinopolis] \cite{dino2002}, \cite{dinopolis} is a componentware framework for robust and secure distributed systems. While not being used in the current prototype, the concepts of Dinopolis influenced the design of \isac{}'s architecture and we hope to use Dinopolis for the integration of \isac{}'s components in a future release.
   161 \item[Dinopolis\footnote{http://www.dinopolis.org/}] \cite{dino2002}, is a componentware framework for robust and secure distributed systems. While not being used in the current prototype, the concepts of Dinopolis influenced the design of \isac{}'s architecture and we hope to use Dinopolis for the integration of \isac{}'s components in a future release.
   167 \item[Isabelle]. As stated before, the theorem prover Isabelle's high-order logic is used in \isac{}'s math engine.
   162 \item[Isabelle] As stated before, the theorem prover Isabelle's high-order logic is used in \isac{}'s math engine.
   168 \end{description}
   163 \end{description}
   169 
   164 
   170 
   165 
   171 \subsection{Status of the Project}
   166 \subsection{Status of the Project}
   172 %WN041008 bitte NICHT 'logic foundations' (dazu hab ich nur das allernotwendigste gemacht) und NICHT 'direction' (Du solltest das Einstandsgespraech mit dem naechsten Teammitglied mitgehoert haben!), sondern bitte Vorschlag unten ...
   167 %WN041008 bitte NICHT 'logic foundations' (dazu hab ich nur das allernotwendigste gemacht) und NICHT 'direction' (Du solltest das Einstandsgespraech mit dem naechsten Teammitglied mitgehoert haben!), sondern bitte Vorschlag unten ...
   245 
   240 
   246 
   241 
   247 
   242 
   248 \subsection{Structure of this Thesis}
   243 \subsection{Structure of this Thesis}
   249 requirements
   244 requirements
   250 choosing technology
   245 
       
   246 design and choosing technology
       
   247 
   251 implementation
   248 implementation
       
   249 
       
   250 (to be filled in after the rest is finished)
   252 
   251 
   253 
   252 
   254 \section{Introduction to Terms Used throughout this Thesis}\label{AK:intro:terms}
   253 \section{Introduction to Terms Used throughout this Thesis}\label{AK:intro:terms}
   255 In this section, terms describing basic concepts of \isac{} are explained. Please refer to the example in appendix \ref{use-expl} for a practical view, to appendix \ref{app.terms} for definitions of other terms and to \cite{wn:diss} for in-depth explanations.
   254 In this section, terms describing basic concepts of \isac{} are explained. Please refer to the example in appendix \ref{use-expl} for a practical view, to appendix \ref{app.terms} for definitions of other terms and to \cite{wn:diss} for in-depth explanations.
   256 
   255 
   257 % insert figure of the system
   256 % insert figure of the system
   258 
   257 
   259 \subsection{Logical Components of \isac{}}
   258 \subsection{System Components of \isac{}}
   260 %WN Software / Basic ... Componenets ...
   259 \subsubsection{Math Engine}
   261 \subsubsection{Math Engine or Kernel}
   260 The Math Engine takes care of all mathematical data analysis and processing. It is the only component aware of mathematical meaning of data. Several other components understand the structure of calculations, but are limited in their interpretation of data they are processing. This is due to the complexity of mathematics and the configurability of \isac{}'s concept of mathematics. While future formula editors might share the Kernel's syntactic knowledge, present components cannot check a formula for syntactic correctness or even distinguish a literal number from a variable name. 
   262 The Math Engine, occasionally referred to simply as the Kernel, 
       
   263 %WN0501 kernel = me + kb (in sml-format)
       
   264 takes care of all mathematical data analysis and processing. It is the only component aware of mathematical meaning of data. Several other components understand the structure of calculations, but are limited in their interpretation of data they are processing. The 
       
   265 %WN..
       
   266 is due to the complexity of mathematics and the configurability of \isac{}'s concept of mathematics. While future formula editors might share the Kernel's syntactic knowledge, present components cannot check a formula for syntactic correctness or even distinguish a literal number from a variable name. 
       
   267 %zB Klammerfehler werden vom Formeleditor behandelt: Syntaxfehler im FE, log Fehler (Typen, Vollst�digkeit von Model-Items etc.) im KE
   261 %zB Klammerfehler werden vom Formeleditor behandelt: Syntaxfehler im FE, log Fehler (Typen, Vollst�digkeit von Model-Items etc.) im KE
       
   262 %wenn, wie angedeutet, selbst die assoziativiaet von operatoren in isabelle programmierbar ist, kann der FE fuer sich nicht einmal klammern ueberpruefen
   268 \subsubsection{Knowledge Base}
   263 \subsubsection{Knowledge Base}
   269 The Knowledge Base stores \isac{}'s knowledge about mathematics. This knowledge is used by the Math Engine for calculations, but the same knowledge is intended to be accessible to the user for reference or for learning purposes. 
   264 The Knowledge Base stores \isac{}'s knowledge about mathematics. This knowledge is used by the Math Engine for calculations, but a human-readable copy of the same knowledge is intended to be accessible to the user for reference or for learning purposes. 
   270 %(Math-)Authoring SML, math-knowledge exported to an XML-representation -- this accessed by the user (explanations added to XML-representation).
   265 \subsubsection{Kernel}
       
   266 The Math Engine and the Knowledge Base together are referred to as the Kernel.
   271 \subsubsection{Knowledge Browser}
   267 \subsubsection{Knowledge Browser}
   272 The Knowledge Browser is the tool for searching and displaying knowledge from the Knowledge Base.
   268 The Knowledge Browser is the tool for searching and displaying knowledge from the Knowledge Base.
   273 \subsubsection{Worksheet}
   269 \subsubsection{Worksheet}
   274 The Worksheet is an abstraction of the traditional paper-and-pencil interface to calculations. It is the user's tool for viewing and manipulating calculations.
   270 The Worksheet is an abstraction of the traditional paper-and-pencil interface to calculations. It is the user's tool for viewing and manipulating calculations.
   275 \subsubsection{Dialog}
   271 \subsubsection{Dialog}
   276 The Dialog is the didactic part of the system. It manages the user's interaction with the system in a conceptual way. It makes decisions about which data to present and which options to offer to the user depending on the current learning situation.
   272 From the user's point of view, the Dialog is the didactic part of the system. It manages the user's interaction with the system in a conceptual way. It makes decisions about which data to present and which options to offer to the user depending on the current learning situation.
   277 \subsubsection{Dialog Atom}
       
   278 %WN\subparagraph{Dialog Atom}
       
   279 Dialog Atoms are basic building blocks of user interaction when doing calculations in a learning context. Examples for Dialog Atoms are \emph{having the user calculate a step in a calculation}, \emph{calculating a step automatically} or \emph{asking questions}.
       
   280 \subsubsection{Dialog Activity}
       
   281 Dialog Activity denotes a measure for the system's responsibility for the work being done. While in calculating a step automatically \isac{} takes all responsibilty for the result, having the user enter the step leaves most of the responsibility, challenge and learning effect with the user.
       
   282 \subsubsection{Dialog Strategy}
       
   283 Dialog Strategies are sequences of Dialog Atoms guiding a user through the learning process, distinguished by different levels of Dialog Activity and different didactic backgrounds.
       
   284 \subsubsection{User Model}
   273 \subsubsection{User Model}
   285 The User Model is an abstraction of \isac{}'s experience with an individual user based on the history of interaction. In particular, the User Model keeps records of knowledge viewed or used by the user, the Dialog Atoms used and the user's success in this process.
   274 The User Model is an abstraction of \isac{}'s experience with an individual user based on the history of interaction. In particular, the User Model keeps records of knowledge viewed or used by the user, the Dialog Atoms used and the user's success in this process.
   286 Based on these data, the Dialog makes assumptions about the user's familiarity with mathematical concepts and guides him accordingly.
   275 Based on these data, the Dialog makes assumptions about the user's familiarity with mathematical concepts and guides him accordingly.
       
   276 
       
   277 \subsection{Abstraction Levels of Dialog Behaviour}
       
   278 \subsubsection{Dialog Atom}
       
   279 Dialog Atoms are basic building blocks of user interaction when doing calculations in a learning context. Examples for Dialog Atoms are \emph{having the user calculate a step in a calculation}, \emph{calculating a step automatically} or \emph{asking questions}.
       
   280 \subsubsection{Dialog Strategy}
       
   281 Dialog Strategies are sequences of Dialog Atoms guiding a user through the learning process, distinguished by different levels of Dialog Activity and different didactic backgrounds.
       
   282 \subsubsection{Dialog Activity}
       
   283 Dialog Activity denotes a measure for the system's responsibility for the work being done. While in calculating a step automatically, \isac{} takes all responsibilty for the result, having the user enter the step leaves most of the responsibility, challenge and learning effect with the user.
   287 
   284 
   288 
   285 
   289 \subsection{Key Elements in Calculations}
   286 \subsection{Key Elements in Calculations}
   290 \subsubsection{Formula}
   287 \subsubsection{Formula}
   291 A Formula is a formal text describing mathematical objects. From a practical point of view, a Formula in \isac{} is very much what you expect it to be.
   288 A Formula is a formal text describing mathematical objects. From a practical point of view, a Formula in \isac{} is very much what you expect it to be.
   297 \subsection{\isac{}'s Concept of Calculations}
   294 \subsection{\isac{}'s Concept of Calculations}
   298 \subsubsection{Calc Tree}
   295 \subsubsection{Calc Tree}
   299 \isac{} organizes calculations in Calculation Trees. The normal flow of an calculation alternates Formulas and Tactics transforming one Formula into the next one. This list-like structure branches where independent calculations have to be made to obtain intermediate results, such as finding the roots of the first derivative of a function to solve an optimization problem or to obtain several cases in a case-split.
   296 \isac{} organizes calculations in Calculation Trees. The normal flow of an calculation alternates Formulas and Tactics transforming one Formula into the next one. This list-like structure branches where independent calculations have to be made to obtain intermediate results, such as finding the roots of the first derivative of a function to solve an optimization problem or to obtain several cases in a case-split.
   300  
   297  
   301 \subsubsection{Subproblem}
   298 \subsubsection{Subproblem}
   302 Independent calculations to obtain intermediate results are called Subproblems. Independent means that they are fully specified by a Calc Head and could be processed as calculations on their own.
   299 Independent calculations to obtain intermediate results are called Subproblems. Independent means that they are fully specified by a Calc Head and could be processed as calculations of their own.
   303 %                     of
   300 
   304 
   301 
   305 \subsubsection{Calc Head}
   302 \subsubsection{Calc Head}
   306 A Calculation Header details all inputs, constraints and desired results necessary to start a calculation. 
   303 A Calculation Header details all inputs, constraints and desired results necessary to start a calculation. 
   307 Every Calc Tree has at least one Calc Head at its start, but may contain additional Calc Heads where Subproblems are started.
   304 Every Calc Tree has at least one Calc Head at its start, but may contain additional Calc Heads where Subproblems are started.
   308 \subsubsection{Specifiying Phase}
   305 \subsubsection{Specifiying Phase}
   309 The process of specifying all information necessary to start a calculation is called the Specifying Phase. Apart from the necessity of providing the information to the system, the Specifying Phase trains gaining insight into the nature of a mathematical problem before searching for a solution.
   306 The process of specifying all information necessary to start a calculation is called the Specifying Phase. Apart from the necessity of providing the information to the system, the Specifying Phase trains gaining insight into the nature of a mathematical problem before searching for a solution.
   310 \subsubsection{Solving Phase}
   307 \subsubsection{Solving Phase}
   311 In the Solving Phase, Formulas are repeatedly transformed into other Formulas by applying Tactics until eventually a solution is reached.
   308 In the Solving Phase, Formulas are repeatedly transformed into other Formulas by applying Tactics until eventually a solution is reached.
   312 
   309 
   313 \subsection{Mathematical Knowledge}
   310 \subsection{Mathematical Knowledge}
   314 \subsubsection{Model}
   311 Mathematical knowledge stored in \isac{}'s Knowledge Base is categorised as follows:
   315 %WN0501
       
   316 %AK040916: da brauch' ich ein wenig hilfe. was war das nochmal?oder verzichtma auf das wort?
       
   317 %WN041012 ... ja, wenn ich wuesste wie: Model = CalcHead - Specification - Headline ? oder anders rum: Model = Given + Where + Find + Relate ? siehe auch 'terms.txt'
       
   318 
       
   319 %wuerde ich zu 'Describing a Calculation Task' geben: A Model is a Problem instantiated by a Formalization. Thus a Model contains the items required ('give', the input-items) to solve the Problem, the constraints to these items ('where', or the 'precondition'), the names of the objects ('find', the output-items) in order to solve the Problem and the 'relations' between input- and output-items.
       
   320 % model = problem instantiated by formalization
       
   321 
   312 
   322 \subsubsection{Problem}
   313 \subsubsection{Problem}
   323 A Problem describes the abstract common properties of a class of examples. A Problem describes the goal - what are we looking for - and which information has to be given to find a solution. Finding the roots of an equation is one Problem, finding the maximum of a function is another.
   314 A Problem describes the abstract common properties of a class of examples. A Problem describes the goal - what are we looking for - and which information has to be given to find a solution. Finding the roots of an equation is one Problem, finding the maximum of a function is another.
   324 Problems are contained in a hierarchy \isac{} uses for mechanical refinement of a problem (e.g. a type of equation, say 'univariate equation') to a more appropriate problem (say 'rational univariate equation').
   315 Problems are contained in a hierarchy \isac{} uses for mechanical refinement of a problem (e.g. a type of equation, say 'univariate equation') to a more appropriate problem (say 'rational univariate equation').
   325 
   316 
   339 \subsubsection{Formalization}
   330 \subsubsection{Formalization}
   340 A Formalization is a description of a real-world problem, which is normally stated in natural language, expressed in purely mathematical terms. 
   331 A Formalization is a description of a real-world problem, which is normally stated in natural language, expressed in purely mathematical terms. 
   341 %Statt dem obigen Satz (wobei die subsubsec auf Example folgt): A Formalization is the formal representation of an example; the representation is more general than the structure of a Model in order to be able to instantiate more than one Problem with the Formalization.
   332 %Statt dem obigen Satz (wobei die subsubsec auf Example folgt): A Formalization is the formal representation of an example; the representation is more general than the structure of a Model in order to be able to instantiate more than one Problem with the Formalization.
   342 A Formalization could consist of a formula, a indication of the solution sought and optionally additional formulas indicating contraints applying to valid solutions.% 'contraints' nein, diese werden im Zuge des 'instantiierens' aus dem Problem hinzugefuegt.
   333 A Formalization could consist of a formula, a indication of the solution sought and optionally additional formulas indicating contraints applying to valid solutions.% 'contraints' nein, diese werden im Zuge des 'instantiierens' aus dem Problem hinzugefuegt.
   343 
   334 
   344 %\subsubsection{Model}
   335 \subsubsection{Model}
       
   336 A Model is an abstract Problem instantiated by concrete data as obtained from the Formalization of an Example or from user input.
       
   337 %WN0501
       
   338 %AK040916: da brauch' ich ein wenig hilfe. was war das nochmal?oder verzichtma auf das wort?
       
   339 %WN041012 ... ja, wenn ich wuesste wie: Model = CalcHead - Specification - Headline ? oder anders rum: Model = Given + Where + Find + Relate ? siehe auch 'terms.txt'
       
   340 
       
   341 %wuerde ich zu 'Describing a Calculation Task' geben: A Model is a Problem instantiated by a Formalization. Thus a Model contains the items required ('give', the input-items) to solve the Problem, the constraints to these items ('where', or the 'precondition'), the names of the objects ('find', the output-items) in order to solve the Problem and the 'relations' between input- and output-items.
       
   342 % model = problem instantiated by formalization
   345 
   343 
   346 \subsubsection{Specification}
   344 \subsubsection{Specification}
   347 Given a Formalization, a Specification specifies the Problem to be solved, the Theory where to search for solutions and a Method to be used in solving the example. If a student recognises two examples as being "essentially the same, just the numbers are different", it is the Specifications he recognised as being "the same" and the Formalizations as being "different".
   345 Given a Formalization, a Specification specifies the Problem to be solved, the Theory where to search for solutions and a Method to be used in solving the example. If a student recognises two examples as being "essentially the same thing to calculate, only the numbers are different", it is the Specifications he recognised as being "the same" and the Models as being "different".
   348 %... letzteres wurde sich auch auf das Model beziehen.
   346 
   349 
   347 
   350 
   348 
   351 \subsubsection{Description}
   349 \subsubsection{Description}
   352 In the context of \isac{}, the term Description applies only to descriptions of Examples, comprising text, formulas and figures, such a given in traditional math textbooks.
   350 In the context of \isac{}, the term Description applies only to descriptions of Examples, comprising text, formulas and figures, such a given in traditional math textbooks.
   353 
   351