October 2006 Volume 9 Number 4
October 2006 Volume 9 Number 4
October 2006 Volume 9 Number 4
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
The activity "Going into the Matter" is supported by a HTML document, composed of texts and figures<br />
which describe the main web protocols a web server has to support, and the programming tools needed to<br />
operate them.<br />
The activity "Linking Concepts and Methods" is supported by two slide shows, one presenting the relevant<br />
concepts, and the other describing, step by step, the execution of the Java code of a server.<br />
The activity "Training to Understand" is supported by several exercises on the HTTP server programming.<br />
The activity "Learning by Doing" is supported by a simulation where the learner, helped by a Java editor<br />
and a compiler, should modify existing code in order to make a functional web server.<br />
The activity "Evaluating the acquisition" is supported by two multiple choice questionnaires.<br />
As we have defined before, the enterprise viewpoint of a TEL system is composed by six processes (design,<br />
software engineering, learning, analysis, resources management and learners profiles management). Each of<br />
them should use software such as the open software projects – referenced in the Table 1 – as we have used for<br />
our test.<br />
Process<br />
Table 1: Open Software Projects Used in the Test<br />
Open software products<br />
Design Process Mozilla (Mozilla, 2005), OpenOffice (OpenOffice, 2005), OpenUSS<br />
(OpenUSS, 2005), FreeStyle Learning (FSL, 2005)<br />
Software Engineering Process Eclipse (Eclipse, 2005), AndroMDA (AndroMDA, 2005),<br />
PoseidonCE (PoseidonCE, 2005)<br />
Learning Process Mozilla, OpenUSS, FreeStyle Learning<br />
Analysis Process Weka (Weka, 2005), WUM (WUM, 2005)<br />
Resources Management Process GForge (GForge, 2005), CVS (CVS, 2005)<br />
Learners Profiles Management Process OpendLDAP (OpenLDAP, 2005)<br />
The Use Case of a Reverse Engineering of an Educational System<br />
On page 15 of Chikofsky (1990), the reverse engineering is defined as "the process of analyzing a subject system<br />
with two goals in mind: 1) to identify the system's components and their interrelationships; and, 2) to create<br />
representations of the system in another form or at a higher level of abstraction". We will here present a typical<br />
use case of reverse engineering which explains how the RM-ODP framework could guide the software<br />
engineering process when it tries to implement the specification (a representation of the TEL system from the<br />
information viewpoint) provided the design process. The interaction between these two processes produces an<br />
artifact which is a representation of the TEL system from the technology viewpoint. This use case is structured in<br />
five steps, as shown in figure 3.<br />
Foundations<br />
<br />
Information viewpoint<br />
<br />
<br />
Enterprise viewpoint<br />
Engineering viewpoint<br />
Technology viewpoint<br />
Computational viewpoint<br />
<br />
<br />
Figure 3: The five steps of the Reverse Engineering Use Case<br />
233