Analysis of “An improved interface for tutorial dialogues: browsing a visual dialogue history”
Summary:
“Thus, we observed that both the tutor and the student refer to
prior utterances: the tutor refers to past explanations in order
to point out similarities or differences to a prior problemsolving
situation. The student refers to prior explanations
in order to ask questions about how prior problem-solving
steps relate to the current step. These observations led us to
provide facilities that allow both the system and the user to
make use of the dialogue history.”
Has a set of features or “facets” that is uses to determine if problems are the same or similar. The application can then automatically refer back to them whenever the user steps through a problem to review it with the application (done after each problem is completed).
“Reminding students of all the instances of a
principle and stating this principle should promote better
understanding of the principle and when it can be applied
than repeatedly stating the principle as each instance of it
arises.”
Discussion:
It is an interesting idea to reinforce and allow review/query from the dialogue history that has been recorded between a computer and a human. It helps to “drive the point home” and allows the interaction to feel like that of a normal tutor/student session.
How can this be applied to sketch recognition? We are able to pull features out of strokes quite easily, but none that really deal with the user’s intention. We can give them a task to create some primitive or collection of shapes, when it goes into the realm of what I’m trying to do (an application that can assist you in drawing), it would appear to be tougher? The system might have some knowledge (e.g. “You need to draw the corners on the right eye like you drew them on the left eye.”), but I’m failing to see an example where the steps would be redundant (except when drawing reference lines).
Good idea, better for systems that deal with natural language processing.