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

2. 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

3. 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

4. Concept (idea) PI Level PS Level eLS 1 eLS 2 eLS n … mapping Middleware level mapping

5. Our Approach Functional Level Agent & Service Level Scenarios Level Control Model FAM SAM

6. 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

7. 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

8. 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

9. 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

10. 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

11. InfoStation Architecture

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

13. Scenario example ( No Change Scenario – Service Delivery Alternatives)

14. Scenario example (No Change Scenario – Service Termination)

15. Scenario example (Change of Device Scenario)

16. Scenario example (Change of InfoStation Scenario)

17. Scenario example (Change of Device & InfoStation Scenario)

18. Control Models Can we provide formalized control and management models? –For different levels Policy-based Models?

19. 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

20. 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

21. 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

22. Thank you !