250 likes | 434 Views
Mark Melia & Claus Pahl Dublin City University. Towards the Validation of Adaptive Educational Hypermedia using CAVIAr. 6 th International Workshop on Authoring of Adaptive and Adaptable Hypermedia. Agenda. Courseware validation Definition Approach Modeling concerns - CAVIAr
E N D
Mark Melia & Claus Pahl Dublin City University Towards the Validation of Adaptive Educational Hypermedia using CAVIAr 6th International Workshop on Authoring of Adaptive and Adaptable Hypermedia
Agenda • Courseware validation • Definition • Approach • Modeling concerns - CAVIAr • Model interoperability – model transformations • Applying validation to AEH • Transforming LAOS to CAVIAr • Simple validation
Courseware Validation • What is Courseware Validation? • Courseware validation allows the course creator to check for certain pedagogical and non-pedagogical characteristics in constructed courseware. • What characteristics are of concern? • Literature review
Courseware Authoring Validation Information Architecture (CAVIAr) • Data models • Domain model • Concepts • Pedagogically neutral • Learning context model • Conceptual sequencing constraints • Learner Stereotypes • Presumed knowledge • Learning goals • Learning resource model • Models learning resources and metadata • Courseware model • Topics • Entry learner conditions for topics • Sequencing relationships
Courseware Authoring Validation Information Architecture (CAVIAr) • Validation model • Defines a valid courseware in terms of the data models • Constrains the allowable model configurations • Courseware model must adhere to constraints
Defined on Model Constraints CAVIAr Metamodel Must be true for Instance of CAVIArmodel A Metamodeling Approach
Defining Constraints on CAVIAr • Number of topics contained in a topic must be between 5 and 15 • Constraints defined on the metamodel – constrains the allowable structure of the model context Topic Inv more_contained_topics: relations->select(type = #CONTAINS)->size() > 5 and relations-> select(type = #CONTAINS)->size() <15
Model Interoperability – Model Transformations • Allows for model transformations • Transform from one model type to another model type • Defined using a declarative language at the metamodel level (the model schema level) • CAVIAr models can be transformed to/from any type of models as long as: • Metamodel defined for target/source model • Transformation defined between metamodels
CAVIAr Metamodel Metamodel x Instance of Instance of CAVIArmodel model x A Metamodeling Approach Transformation Definition Defined on Model Constraints Must be true for Transformation
Model Transformations - AEH -> CAVIAr Transformation Definition AEH Metamodel CAVIAr Metamodel Instance of Instance of Databases Course Databases Course Transformation
AEH Interoperability Case Study AEH - LAOS • Set of models for creating AEH – MOT (Cristea et. al.) • Domain map • Goal and constraint map • User map • Adaptive map • Presentation map • Common Adaptation Framework (CAF) • XML format • LAG • Defined in BNF format • Basic level made up of IF-THEN-ELSE rules
Transforming LAOS to CAVIAr • Transforming CAF to CAVIAr • CAF Metamodel definition • CAF metamodel CAVIAr metamodel definition • Transforming LAG to CAVIAr • LAG metamodel definition • LAG metamodel CAVIAr metamodel definition
CAF Transformation: Generating CAVIAr learning context model
CAF Transformation: Generating CAVIAr learning resources & metadata
Transforming LAOS to CAVIAr • Transforming CAF to CAVIAr • CAF Metamodel definition • CAF metamodel CAVIAr metamodel definition • Transforming LAG to CAVIAr • LAG metamodel definition • LAG metamodel CAVIAr metamodel definition
LAG Transformation • Defining LAG Metamodel
LAG Transformation • Transforming a simple LAG sequencing rule to CAVIAr courseware model constraint IF (DM.Concept.title.access == ‘true’) THEN (DM.Concept.text.show == ‘true’)
Validating the AEH • The AEH can then be validated as any other courseware using a constraint language. • LOs must be shorter than 40 mins in length • context Topic • Inv more_contained_topics: • relations->select(type = #CONTAINS) • ->size() > 5 and relations-> • select(type = #CONTAINS)->size() <15
Conclusions • Provided for a starting point in validating AEH designs • Modelling technologies allow for AEH interoperability • AEH CAVIAr • Possibility of generalising the approach to allow for a more generic approach to AEH interoperability with TEL state of the art
Questions • Questions, comments welcome • Thank you for listening. • Contact Details • Email: mark.melia@computing.dcu.ie