Math-Bridge Event Systems

1. Math-Bridge
Education Solution

2. EVENT FRAMEWORK OF
MATH-BRIDGE
Dr. Giorgi Goguadze

3. Math-Bridge Architecture (VERY simplified)
CAS
Tutorial
Component
Student
Model
Knowledge
Base
Exercise
Subsystem
Client
Presen
tation
Engine
Search
Index
Books
Views
External
Diagnosis
Systems

4. Math-Bridge Event Framework
• Each action in the system produces an event as a means of
communication of components
• An event is a message specifying
• what action was performed (type of event)
• which component was the source of this action (source)
• when was this action performed (timestamp)
• Some components of the system are interested what the others are
doing
• In order to find out about the actions of each other components are
listening to the events produced by others

5. Math-Bridge Event Framework
• Events have tags to specify the type
• Interested components have to subscribe for the needed tag
• For example, User event tag indicates that the event is tied to a
specific user
• It has a userId attribute (anonymous if not logged in)

6. Event Listener and Subscription for Events
• A Listener Interface defines methods to listen to events
• A Subscription Interface subscribes listeners to selected events (or
to all events)
• A component can also unsubscribe for event, if not interested any
more at some point
• A Publisher Interface defines method for publishing events in the
System to be further reviewed and exported to the logging device

7. <ActivemathEvent type="PagePresented" ts="1106913433214"
source="org.activemath.webapp.controller.ViewBook">
<User id="Eva"/>
<Session id="EAB428520EFF6570171766BC2A23513D"/>
<Book id="analysisIndividuellComplete"/>
<PagePresented page="1"/>
</ActivemathEvent>
XML Representation of Events
When events are represented linearized in a file, an XML representation
similar to the one below can be used:

8. • UrlRequested (Attr: url, referrer) [Tags: Application, User, Session]
An URL has been requested. This is tracked by all controllers.
• PagePresented (Attr: pageId) [Tags: InteractionBook]
User requests a page in a book.
• ItemPresented (Attr: none) [Tags: Interaction, Item]
A content item is delivered to the user.
• ItemSeen (Attr: duration) [Tags: Interaction, Item]
User has seen a content item for a certain duration (seconds).
• UserBookCreated (Attr: title, grouping, goals, scenario) [Tags:
InteractionBook]
User has planned a new book.
• UserBookRenamed (Attr: oldTitle, newTitle) [Tags: InteractionBook]
User is renaming a user book.
• UserBookDeleted (Attr: none) [Tags: InteractionBook]
User has deleted a user book.
Examples of Math-Bridge Events

9. • ExerciseStarted (bookId, itemId)
An Exercise was started
• ExerciseRun(itemId, durationMillis, endState, successRate, numHints,
numSteps)
An Exercise has been run. Collects information about the duration, success
hints presented etc.
• ExerciseFinished(bookId, itemId, successRate)
An Exercise was finished. Includes success rate
• ExerciseStep(bookId, confidence, itemId, stepDuration, successRate,
userInputDelay, userInputRaw, userInput)
An exercise step has been performed. This event includes parameters like user
confidence value, step duration in milliseconds, success rate, user input delay,
the user input represented as a mathematical object
Exercise Events
Exercise Events are major means for updating the Student Model with
information on learner progress

10. Thank you.
The Mathematical Bridge, Cambridge, England