A Late Modelling Approach for the Definition of Computer-Supported Learning Process

1. A Late Modelling Approach for the Definition of Computer-Supported Learning Process Telmo Zarraonandia, Camino Fernández, Juan Manuel Dodero tzarraon@inf.uc3m.es Universidad Carlos III de Madrid Departamento de Informática Escuela Politécnica Superior Av. Universidad 30 Leganés, Madrid, España 28911

2. Overview • Objectives • Late Modelling Lifecycle • Adaptation Mechanism • LD Player Architecture • Validation Mechanism • Notations • Conclusions and Future Work • Objectives • Late Modelling Lifecycle • Adaptation Mechanism • LD Player Architecture • Validation Mechanism • Notations • Conclusions and Future Work

3. Objectives • Bring together the way teachers work in real life and the way they work in a computer supported environment Late modelling • Focused on IMS Learning Design • Supervised process • Increase: • Teacher’s degree of freedom when applying a Learning Design process • Teacher’s control over the process • Facilitate the implementation of the late modelling lifecycle

4. Overview • Objectives • Late Modelling Lifecycle • Adaptation Mechanism • LD Player Architecture • Validation Mechanism • Notations • Conclusions and Future Work • Objectives • Late Modelling Lifecycle • Adaptation Mechanism • LD Player Architecture • Validation Mechanism • Notations • Conclusions and Future Work

5. Late Modelling Lifecycle

6. Late Modelling Phases • Monitor Execution • Observe learner’s reactions, interests, resources availability, context.... • Adaptation Introduction • Modify process execution “on the fly” • Evaluation of Adaptations • Process Evaluation • Adaptation Integration • Select adaptations which mean an improvement • Make changes permanent

7. IMS Learning Desing: What do we need? • A notation to specify the monitorizations • A notation to specify the adaptations • A notation to specify the learning objectives evaluations • Create a evaluation profile for the UoL • A mechanism to modify the process “on the fly” • Introduce the adaptations... • To observe process evolution at any time....

8. Overview • Objectives • Late Modelling Lifecycle • Adaptation Mechanism • LD Player Architecture • Validation Mechanism • Notations • Conclusions and Future Work • Objectives • Late Modelling Lifecycle • Adaptation Mechanism • LD Player Architecture • Validation Mechanism • Notations • Conclusions and Future Work

9. Adaptation Mechanism (I) • Superimpose IMS LD fragments on top of an existing manifest definition .... Environments: Activities: Learner Activities Resource Activity 1 <= What_Is_Internet.pdf Activity 2 <= Web_Browsers Activity 3 <= Search_Engines Activity 4 <= Mail_Programs Activity 5 <= Messenger_Programs Support Activities Roles: Learners: Student Role Staff: Environments: Activities: Learner Activities Resource Activity 1 <= What_Is_Internet.pdf Activity 2 <= Web_Browsers Activity 3 <= Search_Engines Activity 4 <= Mail_Programs Activity 5 <= Messenger_Programs Support Activities Activity Structure Internet Lessons (Structure = Sequence) 1. Activity 1 2. Activity 2 3. Activity 3 4. Activity 4 ......... Method .............. Internet_Basics.html SearchEnginesTheory.pdf Mail_Programs_Theory.pdf

10. Adaptation Mechanism (II)

11. Adaptation Mechanism (III) • An architecture for extending existing players with runtime adaptation capabilities: • Non intrusive • Flexible • Validate the definition of the modified manifest

12. Overview • Objectives • Late Modelling Lifecycle • Adaptation Mechanism • LD Player Architecture • Validation Mechanism • Notations • Conclusions and Future Work • Objectives • Late Modelling Lifecycle • Adaptation Mechanism • LD Player Architecture • Validation Mechanism • Notations • Conclusions and Future Work

13. LD Player Implementation: Visitor Pattern

14. LD Player Implementation:Visitor Pattern + Aspects • We need an “accept” operation on the Learning Design elements • Aspect Oriented Programming approach: • ASPECT : Operations (adaptation, monitorization..) • POINTCUT : Condition of application of the operation • ASPECT and POINTCUTS defined separately from the rest of the components

15. Overview • Objectives • Late Modelling Lifecycle • Adaptation Mechanism • LD Player Architecture • Validation Mechanism • Notations • Conclusions and Future Work • Objectives • Late Modelling Lifecycle • Adaptation Mechanism • LD Player Architecture • Validation Mechanism • Notations • Conclusions and Future Work

16. Validation Mechanism (I) • Guarantee UoL definition remains compliant with the IMS LD specification after the adaptation • IMS LD Ontology [University of Santiago de Compostela]: • Taxonomy of concepts • Restrictions represented as axioms declared in First Order Logic • Implementation: F-logic

17. Adaptation is introduced • Manifest definition is changed • Manifest translation: • F-logic description of the LD obtained • Flora-2 reasoner invoked • Axiom restrictions checked Validation Mechanism (II): Process

18. Overview • Objectives • Late Modelling Lifecycle • Adaptation Mechanism • LD Player Architecture • Validation Mechanism • Notations • Conclusions and Future Work • Objectives • Late Modelling Lifecycle • Adaptation Mechanism • LD Player Architecture • Validation Mechanism • Notations • Conclusions and Future Work

19. Notation for the Adaptations Description • Three types of files : • Adaptation command • Adaptation manifests • Resource files

20. Notation for the Monitorizations Definition • Peeks can be concatenated • Refer to different UoL instances • Used as conditions of the adaptations • Base for the evaluations

21. Notation for the Evaluations Definition

22. Overview • Objectives • Late Modelling Lifecycle • Adaptation Mechanism • LD Player Architecture • Validation Mechanism • Notations • Conclusions and Future Work • Objectives • Late Modelling Lifecycle • Adaptation Mechanism • LD Player Architecture • Validation Mechanism • Notations • Conclusions and Future Work

23. Conclusions and Future Work • Alternative / Complement IMS Lerning Design adaptation and monitorization mechanisms: • Introduction “on the fly” • Ontology Level B and C • Tools: • Done: • CopperCore Engine Extension for Adaptation • Off-line validation • Next: • Tools for the adaptation, monitorization and evaluation definition • Assemble everything...

24. Thanks for you attention!!