ED-MEDIA 1999 Proceedings Book - Association for the ...
ED-MEDIA 1999 Proceedings Book - Association for the ...
ED-MEDIA 1999 Proceedings Book - Association for the ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Architecture of HEZINET<br />
The system has six main modules, namely, <strong>the</strong> Interface, <strong>the</strong> Auditor, <strong>the</strong> Course, <strong>the</strong> Student<br />
Model, <strong>the</strong> Intelligent Module, <strong>the</strong> Human Teacher Module and <strong>the</strong> Communication Module. In (Fig. 3) a<br />
view of <strong>the</strong> interaction between <strong>the</strong>se modules is provided. There are two well-differentiated parts: <strong>the</strong> hypermedia<br />
and <strong>the</strong> adaptive part. The Interface module controls <strong>the</strong> hypermedia part. The o<strong>the</strong>r modules<br />
<strong>for</strong>m <strong>the</strong> adaptive part, which is <strong>the</strong> one that is in charge of decision making and storing <strong>the</strong> evolution of <strong>the</strong><br />
student evolution with <strong>the</strong> system. The modules have been implemented using Java, Orbixweb and SQL<br />
Server.<br />
Figure 3: General architecture of HEZINET<br />
The interface module consists of a series of screens developed specially <strong>for</strong> each part of <strong>the</strong> system.<br />
The screen design has been taken seriously so that <strong>the</strong> student motivation gets promoted and he does<br />
not get bored, as stated in (Landow, 1997) "if <strong>the</strong> user gets lost or bored, <strong>the</strong> system is bound to fail". The<br />
screens contain very intuitive buttons and are very easy to use (Baker, 1993): "<strong>the</strong> interface should be<br />
structured such that <strong>the</strong> student is learning <strong>the</strong> subject domain, not <strong>the</strong> program interface". The Interface<br />
interacts directly with <strong>the</strong> student. It obtains user reactions and sends relevant ones to <strong>the</strong> Auditor. The latter<br />
processes that in<strong>for</strong>mation and returns back to <strong>the</strong> <strong>for</strong>mer new data to be displayed. The interface has<br />
been divided into five functional spaces (Fig. 4). Area 1 contains buttons offering functionality always<br />
available during <strong>the</strong> student interaction with <strong>the</strong> system. It basically contains contextual help <strong>for</strong> new users;<br />
a grammar book; a dictionary; tools to contact a human teacher or to talk with o<strong>the</strong>r students working with<br />
<strong>the</strong> system at that moment; and a tool to review <strong>the</strong> steps followed previously. Area 2 contains buttons that<br />
will not always be active. Some of <strong>the</strong>m depend on <strong>the</strong> type of activity <strong>the</strong> student works on. Area 3 is a<br />
navigation area that offers <strong>the</strong> possibility to go back through previous steps of navigation. Area 4 is only<br />
in<strong>for</strong>mative and provides in<strong>for</strong>mation about <strong>the</strong> task being done by <strong>the</strong> student and <strong>the</strong> location in <strong>the</strong> hypermedia<br />
where is <strong>the</strong> user. Finally, area 5 is <strong>the</strong> workspace. It shows <strong>the</strong> activities and provides places to<br />
write or construct answers to questions.<br />
Figure 4: The interface is divided into five functional areas