|
Article Excerpt Explanations are essential in the teaching process. Tracers are one possibility to provide students with explanations in an intelligent tutoring system. Their development can be divided into four steps: (a) the definition of the trace model, (b) the extraction of the information from this model, (c) the analysis and abstraction of the extracted information, and (d) the visualization of the result of the analysis. This article describes the architecture of a domain independent tracer developed in Visual Prolog displaying explanations in the form of a textual dialog or a graphical tree.
**********
Explanations are an integral part of any teaching process. A tutorial system should be able not only to solve problems but also to explain them. For this purpose, the steps leading to the solution must be recorded to be presented to the student in case of difficulties. Two techniques are generally used: meta-interpreters and tracers.
In meta-programming data are programs (Yalcinalp, 1991). Since Prolog code and data have the same format (i.e., Horn clauses), this language is particularly appropriate for meta-programming. Meta-interpreters are generally used to add supplementary functions to an existing interpreter. We developed several domain dependent and domain independent meta-interpreters (Ratz & Lusti, 1992; Ratz, 1993; Trapp & Lusti, 1999; Trapp, 2000). Meta-programming in standard Prolog is easy because its source code is interpreted and therefore accessible at run-time. Other Prolog systems produce compiled code, which is faster but complicates meta-programming (Lusti, 1990). FA-Tutor, for example, is an Intelligent Tutoring System for financial analysis developed in a compiled variant of Prolog (Lusti, 1995). This article describes the architecture of a tracer for AHP-Tutor, a system teaching the theoretical background of the Analytic Hierarchy Process. AHP-Tutor has been developed in Visual Prolog, a compiled Prolog (Ishizaka & Lusti, 2003).
TRACER
A tracer collects a detailed protocol (trace) of the execution of a program. To understand how a program reaches its result, we add side effects producing supplementary information on the intermediary states of the execution. This information is analysed and summarised before being presented to the user. The construction of a tracer can be divided into four steps (Ducasse & Noye, 1994):
1. definition of a trace model;
2. extraction of information from this model;
3. analysis/abstraction of the extracted information; and
4. visualisation of the result of the analysis.
These four steps are often considered neither explicitly nor separately. In AHP-Tutor (Ishizaka & Lusti, 2003), for example, the steps 2 and 3 are concomitant.
The literature is rich in tracers producing information on program execution for debugging purposes (Lakhotia, Sterling, & Bojantchev, 1995; Dichev & Du Boulay, 1989; Ducasse, 1999; Ducasse, Langevine, & Deransart, 2003). It has been noted that the produced information, with some enrichment, could be used as explanations in teaching courses. The tracers have been modified to be...
|
|

More articles from Journal of Interactive Learning Research
The nature of groups: implications for learning design., March 22, 2006
Looking for additional articles?
Search our database of over 3 million articles.
Looking for more in-depth information on this industry?
Search our complete database of Industry & Market reports by text, subject, publication
name or publication date.
About Goliath
Whether you're looking for sales prospects, competitive information, company
analysis or best practices in managing your organization,
Goliath can help you meet your business needs.
Our extensive business information databases empower business
professionals with both the breadth and depth of credible,
authoritative information they need to support their business
goals. Whether it be strategic planning, sales prospecting,
company research or defining management best practices -
Goliath is your leading source for accurate information.
|
|