ELSE – eLearning in Software Engineering Stanimir Stoyanov, Distributed eLearning Center (DeLC), University of Plovdiv

eLSE – eLearning in Software Engineering

Stanimir Stoyanov,

Distributed eLearning Center (DeLC),

University of Plovdiv

Introduction

• Different definitions, approaches, models, … for IT supported education and learning – CBT – most of the current real systems– eLearning

• Personalization• Anywhere• Anytime

• Our aim– eLearning-oriented Infrastructure– Prototype application in the SE domain

• What we need (in order to ensure personalization, anywhere & anytime access to the education resources) ?– Suitable approach - MDA like– Flexible and adaptive & adaptable software architecture – Standards– Access

MDA Approach

• Creation a PIM– UML modeling

• Converting into PSM– UML modeling

• Dialects (profiles)

– Standard platforms• Standard mappings and tools

– Specialized platforms• Absence of MDA tools• Hand coding

• Generation application code itself– Different types of code

Concept (idea)

PI Level

3rd Tier: InfoStations Center

2nd Tier: WiMAX / WiFi InfoStation

2nd Tier: WiFi /Bluetooth InfoStation

2nd Tier: WiFi InfoStation

2nd Tier: Bluetooth InfoStation



1st Tier: MobileDevice (PDA)

1st Tier: MobileDevice (Laptop)

1st Tier: Mobile Device(Mobile Phone)

PS Level

eLS1 eLS2 eLSn…

mapping Middleware level

mapping

Our Approach

Functional Level

Agent & Service Level

Scenarios Level

Control Model

Control Model

Control Model

FAM

SAM

Functional level

• Aim: creation of a platform independent Virtual Information Space – Description and modeling (UML) of expected functionality– eLearning Services Model– eContent Model

• Based on: eLearning Service-Oriented Framework– JISC, DEST, IC, ADL– Common set of concepts and terms – Reference model– Defining services– Underlain infrastructure independent

• eLearning Services Model– Two levels

• Meta-model• Services models

• eContent Model– Domain model

eLearning Services Model

• Meta-model– Aims to provide a classification of the services– Classification will be used for services

searching and management during the run-time

– Ontology

• Services model– A set of models which describe the

functionality of different services

eContent Model

• Closed related with the domain model• Ontologies: present the domain structure

– Different levels• Classification• Areas• Objects

• eConent structures: SCORM compliant – SCOs– Scenarios– Models

Scenarios level

• Idea:– Presentation of access and communication

infrastructure as a set of run-time scenarios– Details hiding– Implementation on an more abstract level

• Access – Fixed

• eLearning portals

– Mobile• InfoStations

eLearning Portals

• Delphi Group reference model– Multi-layered architecture– Each layer different functionality

• Our architecture: specific layers– User, domain, pedagogical models – Intelligent search (CBR-based)– SCORM run-time engine

• Implementation– Life Ray Portal Framework

InfoStation Architecture

3rd Tier: InfoStations Center

2nd Tier: WiMAX / WiFi InfoStation

2nd Tier: WiFi /Bluetooth InfoStation





1st Tier: MobileDevice (PDA)

1st Tier: MobileDevice (Laptop)

1st Tier: Mobile Device(Mobile Phone)

Scenario example(No Change Scenario – AAA + Service Initialization)

User AAA OK; Service agent and Profile Agent generate a service

offer to user

Request for User AAA + Update Profile + Make &

Model Parameters

Request for User Authentication, Authorization and Accounting (AAA) +

Profile Updates + Mobile Devices Make & Model Parameters

Personal Assistant

(Intelligent Agent)

User

InfoStation(Intelligent Agent)

Display Info to User

Select mLecture Service. Then select specific

Lecture Content User Service Request

Forward User Service Request

InfoStation Center

(Intelligent Agent)

AAA ACK + Services Offer

AAA ACK + Services Offer

Register user in local virtual address book +

Update Profile

Initiate the service. Check for having most up-to-date

content of requested lecture in 'best' format

AAA + Service Initialization

Scenario example(No Change Scenario – Service Delivery Alternatives)

Personal Assistant

(Intelligent Agent)

User


InfoStation Center

(Intelligent Agent)

Display lecture to User

Read Lecture

eContent agent chooses desired content,CC/PP

Agent retrieves re-format information from repository

Transfer of Lecture Content in 'best' format

Display lecture to User

Read Lecture

Request for new 'best' format of lecture content

Transfer of lecture content in new 'best' format

Copy new eContent into cache


Service Delivery Alternative 1:

lecture content's format available at InfoStation

Service Delivery Alternative 2:

ecture content's format NOT available at InfoStation

Scenario example(No Change Scenario – Service Termination)

Personal Assistant

(Intelligent Agent)

User


InfoStation Center

(Intelligent Agent)

Request for Service Termination + Profiles Update

ACK

Terminate Service; Update User Profile and

User Service Profile

End of ServiceRequest for Service Termination +

Profiles Update

ACKACK

Updated User Profile and User Service Profile

Service Termination

Scenario example(Change of Device Scenario)

Change the device (e.g. from a PDA to a

laptop)

Notification of device change + User Service Profile Updates + New

Device's Make & Model Parameters

Service Agent selects new 'best' format

Display lecture content in new format

Read Lecture

Change of Device during service

delivery

Request for new 'best' format of lecture content

User

Check for having most up-to-date content in new 'best' format - FORMAT NOT

AVAILABLE


Copy new eContent into cache


Personal Assistant

(Intelligent Agent)InfoStation

(Intelligent Agent)

InfoStation Center

(Intelligent Agent)

Scenario example(Change of InfoStation Scenario)

User leaves InfoStation coverage area, but continues reading

lecture contentUser Progress throughout

lecture content is monitored

Request for User de-registration + User Service Profile Update

User

De-register user;Update casched profile

User arrives in coverage area of

another InfoStation

Personal Assistant

(Intelligent Agent)InfoStation 1

(Intelligent Agent)

InfoStation Center


(Intelligent Agent)

Request for Profile Update

Update Profile

AAA + Service Re-initialization

Continuation of Service Delivery (from the point already reached by the user)

Change of InfoStation during service delivery

Scenario example(Change of Device & InfoStation Scenario)

User

Personal Assistant


(Intelligent Agent)

InfoStation Center


(Intelligent Agent)

Change of Device during service delivery

Change of InfoStation

Change of InfoStation during service delivery

Change of Device

Control Models

• Can we provide formalized control and management models?– For different levels

• Policy-based Models?

Personalization, Flexibility & Adaptability

• eLearning Services, eContent in relation to three models:– User model– Domain model– Pedagogical model

• Using standards– SCORM– CC/PP

• Users’ personal profiles• Users’ mobile devices profiles

• Adaptive– A configuration capability– Supported by the development environment

• Adaptable – A run-time capability

Implementation remarks

• Development environments and tools– SELBO

• User-friendly tools for eContent preparing in the field of Software Engineering

• Possibilities for adaptation to new domains • Supporting adaptation

• Run-time modules– eContent access

• Fixed - eLearning portals• Mobile - InfoStation run-time system

– Supporting adaptability

Problems

• Can the InfoStation architecture be adequate presented by a set of scenarios?

• What kind of Control & Management Models?

• Precise definition of adaptive & adaptable

• Final portal architecture

• Agent & Service Level

Thank you !

Documents

ELSE – eLearning in Software Engineering Stanimir Stoyanov, Distributed eLearning Center (DeLC), University of Plovdiv