ActiveMaths (Melis et al., 2001) offers to
learners a mathematical web application with
pedagogical assistance. The learner can ask for
assistance in progressive way (D in Figure 3). At the
first request, a hint is given to the learner. Then, at
the next request, the given hint is more detailed. At
the last request, the solution is given in order to
avoid blocking the learner in working on problems.
The assistance is more and more detailed and
concrete. We call this mode of articulation
progressive mode.
Some applications consult information sources to
provide suitable assistance such as the application
state, the user profile or the user’s choice. Thus, both
ActiveMaths and Hot Potatoes allow consulting the
state of the application such as a text filled by the
learner. For instance, ActiveMaths (E in Figure 3)
verifies answers of the learner and shows the result
(syntax error, incorrect/correct answer).
Consultations are therefore essential to provide a
suitable assistance. We call this mode of articulation
interactive mode.
These modes of articulation can also coexist or
be combined in assistance systems. For instance,
tutorials provide step by step assistance, but in one
step, a textual message and an enhancing can be
simultaneously performed. This is a combination of
successive and simultaneous modes.
3.2 Related Works
The modes of articulation presented in the previous
section exist in many applications. However, some
tools allow also defining these modes explicitly or
implicitly. So, we confronted these modes to tools
related to our approach.
In Marco advisor systems (Richard and
Tchounikine, 2004), the advices are represented as a
graph. The subset of graph represents the assisted
website. There is no explicit articulation between
advices because each advice is represented
independently. However, the articulation between
the elements of a same advice can be conditioned by
the navigation history of the user. This is a case of
interactive articulation of assistance but implicitly
represented. In the Astus platform (Paquette et al.,
2014), educational interventions are represented as
rules organized in a graph. The conditions of the rule
make explicit interactive articulation between
interventions. In the same way, the Epitalk system
(Paquette et al., 1996) explicitly represents the
advices through a tasks graph. These works
concentrate on the definition of assistance but do not
explicitly address the aspect of articulation.
Therefore, the articulation may be defined explicitly
or implicitly by their tools and we can’t find the
presence of progressive and successive modes of
articulation.
In another way, the Grafcet graphical language
(David, 1995) is proposed in order to represent the
sequential automation in systems decomposable into
steps. Although Grafcet is not specific to assistance
systems, the expression of sequence of steps can
inspire our work. In Grafcet, a step can be an active
step, initial step, macro-step, etc. Actions are
associated with a step. The transition between two
steps is done through a transition. A transition is one
or more logical condition (boolean). With Grafcet,
we can describe explicitly the independent,
successive, interactive, simultaneous modes but only
implicitly the progressive mode. In addition, some
elements of Grafcet are not suitable with the ones of
aLDEAS. For instance, Grafcet doesn’t distinguish
events from conditions as aLDEAS does. It contains
also useless information in our context to the phase
of specification of an assistance system such as
active state on step.
To overcome these limitations in the literature,
we proposed a model of articulation between
aLDEAS rules and implemented in SEPIA. This
model and its implementation are presented in the
following.
4 MODEL OF ARTICULATION
BETWEEN ALDEAS RULES
If aLDEAS and its implementation in SEPIA already
allow the definition of the articulation between
assistance elements such as those presented in the
section 3 with aLDEAS rules, the expression of the
articulation between the rules is implicit and can be
complex to define for the assistance designer. To
more effectively operationalize these modes of
articulation in our propositions, it is necessary to
allow defining explicitly the articulation between
aLDEAS rules.
Thus, an assistance system is currently defined
in the AGATE project by a set of aLDEAS rules
always at the same level. In the aLDEAS rules
pattern (Fig. 2), the trigger event, the end event and
the trigger condition are central elements to form the
articulation between rules. For instance, we defined
two rules R
1
and R
2
which describe two successive
steps in the tutorial of Connectify. So, these rules are
articulated in successive mode. It means that R
2
is
launched at the end of R
1
. For this order of launch,