29.03.2013 Views

October 2006 Volume 9 Number 4

October 2006 Volume 9 Number 4

October 2006 Volume 9 Number 4

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

invariant schema defines the existing links between these different objects, as it is shown in the Figure 6, with<br />

the help of the UML graphic language for a class diagram (OMG/UML, 2003).<br />

imsld:environment imsld:learning-object imscp:resource<br />

2<br />

Figure 6: Invariant Schema<br />

The dynamic schema does not exist at this state of the design. Thus, the software engineering process needs to<br />

identify and model new information objects, in order to establish the dynamic schema. One needs here to<br />

characterize the behavior of these different objects.<br />

Step 4: Instantiation of the computational viewpoint. To characterize the dynamic schema, the software<br />

engineering process needs more information on the specification provided by designers. The pattern "Capturing<br />

model details" proposed by Demeyer et al. (2002), supports such a reverse engineering approach. From the<br />

computational viewpoint, the software engineering process wants to define a functional decomposition of the<br />

system. As an example, the SCORM object proposed by the designers to support the activity "Going into the<br />

Matter" (the HTML document "author_text1.html", see figure 5) is an "asset", which is indivisible. This type of<br />

object is only provided to the learner, without any expected feedback. But a "SCO" SCORM object is linked to it<br />

(see figure 5). This type of object contains a structure of internal objects which describes its functioning. The<br />

RM-ODP framework proposes a typology of the interfaces (ISO/IEC 10746-3, 1996, Chapter 7.1) supporting the<br />

interactions between these objects, in order to model them better:<br />

a Signal Interface, in which all the interactions are signals;<br />

an Operation Interface, in which all the interactions are operations;<br />

a Stream Interface, in which all the interactions are flows.<br />

The focus of attention of the software engineering process on the signal interface leads it to adopt the event<br />

programming paradigm as deployed by the SUN Java technology Swing (2005), for the implementation of the<br />

SCORM object.<br />

W3C<br />

<br />

XHTML 1.0<br />

<br />

<br />

XHTML 1.0 Extend Track<br />

<br />

FSL<br />

Swing<br />

<br />

HTMLDocument<br />

1<br />

<br />

JTextComponent<br />

+getUI()<br />

+getText()<br />

Figure 7: The enterprise artifact produced by the reverse engineering<br />

1<br />

FLGTextStudyElementsContentPanel<br />

JTextPane JScrollPane<br />

1 1<br />

JEditorPane<br />

1 1<br />

1<br />

1<br />

<br />

JViewPort<br />

+getExtendSize()<br />

FLGHTMLObserver<br />

1<br />

1<br />

*<br />

adlcp:scormtype<br />

imscp:file<br />

* *<br />

1<br />

<br />

JScrollBar<br />

+getVerticalScrollBar()<br />

+getViewPort()<br />

1<br />

235

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!