Cognitive Tutor Authoring Tools 2.6 > Using the Tools > Example-tracing TutorsThis section will walk you through the main phases of authoring an Example-tracing Tutor with CTAT. For a full, example-based tutorial, see the tutorials section of the CTAT web site.
There are four main phases for authoring an Example-tracing tutor:
Demonstrate: in the student interface (typically Java or Flash), demonstrate examples of correct and incorrect behavior for each problem for which students will be tutored. Alternate ways of solving a problem are recorded as separate paths in the graph.
Generalize: in the Behavior Recorder, define ways in which the tutor can recognize a broader range of behavior. Methods for this include specifying ordering constraints so that students can solve a problem in orders other than the one in which the problem was demonstrated; enhancing 'matching' to generalize the conditions under which a demonstrated step is matched; and marking certain steps (links) in the graph as optional.
Annotate: define hints for correct student actions, feedback for student errors, and success messages for correct actions. Associate knowledge components, pieces of acquired knowledge, with steps in the graph, and view a knowledge component matrix of knowledge component occurrence by problem.
Test: use the tutor, playing the role of student attempting to solve the problem. If possible, field the tutor with a user or number of users to get feedback early and often.
![[Note]](images/note.gif) | Note |
|---|---|
When working with an Example-tracing tutor, set Tutor Type to . |
Authoring a single problem is done by demonstrating (performing) problem-solving actions. During this phase of authoring, you will commonly have the Behavior Recorder window showing in CTAT along with a student interface with which you'll interact.
To set an initial problem state (the start state):
Set Author Mode to .
In the student interface, enter values and/or manipulate the interface to represent the starting state for that problem.
Select > .
To demonstrate problem-solving steps:
After creating a start state for the problem, you can demonstrate problem-solving steps.
Set Author Mode to .
Interact with the student interface. Each action will be recorded as a step in the behavior graph displayed in the Behavior Recorder.
To set an arbitrary state as the student start state:
(Windows) or Control+ (Mac) on a state in the behavior graph that represents a point in the problem where the student should start working.
Select . This state, as it appears in the student interface, will be the state the student sees when they start the problem.
Generally, you will demonstrate a preferred, correct solution path, and revisit states in the graph to add common student misconceptions in the form of both incorrect and suboptimal actions, as well as alternative correct paths. To jump to a state in the graph, click the state node.
| Note |
|---|---|
When demonstrating steps, links are always added to the current state (the state in the graph with the bold text and outline). |
When in Demonstrate mode, all steps are initially created as Correct Action links. To mark an action as incorrect or suboptimal, right-click the link's label and select an option from the menu .
The last step of a demonstration should be a done step, that is, a step where the student signals completion of the problem by pressing a Done button.
Save your graph by selecting .