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.
Choquet, C., & Corbière, A. (<strong>2006</strong>). Reengineering Framework for Systems in Education. Educational Technology &<br />
Society, 9 (4), 228-241.<br />
Reengineering Framework for Systems in Education<br />
Christophe Choquet and Alain Corbière<br />
LIUM Laboratory, University of Maine, IUT of Laval, 53020 Laval Cedex 9, France<br />
christophe.choquet@lium.univ-lemans.fr<br />
alain.corbiere@lium.univ-lemans.fr<br />
ABSTRACT<br />
Specifications recently proposed as standards in the domain of Technology Enhanced Learning (TEL),<br />
question the designers of TEL systems on how to put them into practice. Recent studies in Model Driven<br />
Engineering have highlighted the need for a framework which could formalize the use of these<br />
specifications as well as enhance the quality of the developments. This paper deals with the opportunity for<br />
the TEL community to adopt such a model to express and formalize the design organization and the<br />
engineering process of a TEL system. This kind of model could provide a set of concepts allowing the<br />
description of specifying, modeling and analyzing tasks one needs to perform for defining the negotiation<br />
and the communication between actors in such a community. In a first part, we stress the need for the<br />
instantiation of this framework so as to integrate recent results as well as taking into account the evolution<br />
of software reengineering. In a second part, we propose two instances of this framework; the first concerns<br />
the reverse engineering of a TEL system and the second its reengineering.<br />
Keywords<br />
TEL engineering, TEL reengineering, TEL development process, Model driven engineering<br />
Introduction<br />
The design of TEL (Technology Enhanced Learning) systems calls for the communication and sharing of<br />
information about the users of these systems. In recent studies, the standards and specifications proposed by the<br />
TEL community have provided interoperable languages for the specification of the learning session’s<br />
progression, in order to enhance the communication between the actors of the development. These proposals are<br />
mainly focused on the a priori specification of the system’s behavior. But (Wenger, 1987; Bruillard & Vivet,<br />
1994; Hummel et al., 2004; Tchounikine et al., 2004) for instance, have shown that the design methodology of a<br />
TEL system cannot be reduced to the specification but must also instrument the tasks of recording and analyzing<br />
the uses of the system. Our objective is to merge TEL community results on standards and specifications, and<br />
proposals made by the software engineering community. In this way, we aim to support the communication<br />
between actors of development in a general reengineering framework, as Chikofsky (1990) for who<br />
"reengineering, also known as both renovation and reclamation, is the examination and alteration of a subject<br />
system to reconstitute it in a new form and the subsequent implementation of the new form".<br />
Recent proposals of TEL standards and specifications lead to the adoption of new design practices and<br />
methodologies, but they don’t provide designers with a set of concepts allowing the explicitation of the<br />
organization and the implemented engineering. Some development solutions are provided by the Object Oriented<br />
Software Engineering community, especially in the domain of software reengineering. With an empiric approach<br />
first, the open source and free software communities have had to develop specific and effective tools which<br />
support the structured communication around a design artifact. At the same time, the research community on<br />
software engineering has provided methodological developments as well as a standardized and shared<br />
vocabulary for software reengineering focused on the interoperability and reusability points of view. Chikofsky<br />
(1990) for instance, proposed a first terminology dedicated to the definition of the tasks of reverse engineering<br />
and reengineering. More recently, and based on this taxonomy, the European project ESPRIT 21975 (Bär et al.,<br />
1999) has provided a set of patterns and pattern languages which define and standardize both methodological<br />
concepts – such as “capture model details” or “negotiate a design” – and vocabulary – such as “process” or<br />
“structure”.<br />
The aim of this paper is to show how these results from the software engineering community could be used to<br />
define a general framework, able to support a set of designers, considered as a community, involved in the<br />
reengineering process of a TEL system. We propose to make an instance of the RM-ODP (Reference Model of<br />
Open Distributed Processing) framework on the reengineering process of a TEL system. This reference model is<br />
considered as a framework which coordinates and standardizes open distributed processes by the fine definition<br />
of a set of concepts on engineering practices. Aims and motivations of this RM-ODP standard are detailed in the<br />
document ISO/IEC 10746-1 (ISO/IEC 10746-1, 1998).<br />
ISSN 1436-4522 (online) and 1176-3647 (print). © International Forum of Educational Technology & Society (IFETS). The authors and the forum jointly retain the<br />
copyright of the articles. Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies<br />
are not made or distributed for profit or commercial advantage and that copies bear the full citation on the first page. Copyrights for components of this work owned by<br />
others than IFETS must be honoured. Abstracting with credit is permitted. To copy otherwise, to republish, to post on servers, or to redistribute to lists, requires prior<br />
specific permission and/or a fee. Request permissions from the editors at kinshuk@ieee.org.<br />
228