A Catalogue of Primitive Scenario-Types

The First Step to the Automation of Learning Scenarios

A. Rius, M.A. Sicilia, E. García

Outline

Introduction

The main catalogue Example: composition of primitive scenarios

Conclusions and future work

Outline

IntroductionFinal goal and related workSpecifications and related standards

The main catalogue Example: composition of primitive scenarios

Conclusions and future work

Final goal and related work

Introduction

Catalogue of learning

scenarios

Automate specifications of learning scenarios independently of….

Specification technique oriented

to automation

SCP-BPMN-BPEL

Ontology based on learning scenarios

specification

Introduction

Specifications and related standards

IMS DRI (IMS-Digital Repository Interoperability)

• Reference model for the communication among service providers and learning resources through the LMS

• Some interchange functions based on repositories

Introduction

Specifications and related standards

LORI (CEN-Learning Object Repository Interoperability)

• API as a simple query interface to access learning resources provided by LMS

• Two scenario-types of inquiry between entities

Introducton

Specifications and related standards

IEEE-LTSA (IEEE-Learning Technology System Architecture)

• Framework to understand systems like the LMS

• Interactions among the LMS systems and sub-systems and other related systems

Outline

Introduction

The main catalogue Primitive scenario-type concept Catalogue of primitive scenario-types

Example: composition of primitive scenarios

Conclusions and future work

The main catalogue

Primitive scenario-type concept

Scenario-type (or specification of scenario) - Consistent description of the behaviour of the entities involved in a process and the different states of the system in order to achieve an objective

As the goal is to obtain executable specifications we have tried to define primitive scenario-types as simple as possible with the aim to combine them to achieve new complex scenario-types

The main catalogue

Catalogue of primitive scenario-types

Name IMS DRI LORI LTSC

Send Submit/Store Assertion

Receive Retrieve (If the source is a repository)

Send-Receive Query

The set of primitive scenario-types is presented in four groups according their functionality

Group 1: Transfer scenarios

The main catalogue

Catalogue of primitive scenario-types

Group 2: Preparing transfer scenarios

Name IMS DRI LORI LTSC

Translation Translator

Aggregation Aggregator (only for metadata)

As part of a query

Disaggregation As part of Federator function

As part of a query

Distribution As part of Federator function (information restricted to a query and including the management of responses)

The main catalogue

Catalogue of primitive scenario-types

Group 3: Repository management scenarios

Name IMS DRI LORI LTSC

Save_in_repository Submit/Store Store

Search_repository Search/Expose(the result restricted to metadata)

Retrieve

Search_repositories Gather/Expose(new metadata is obtained by aggregation)

Query

Retreive_from_repository Request/Deliver Retrieve

Erase_LR

Update_LR

The main catalogue

Catalogue of primitive scenario-types

Group 4: Support to learning process scenarios

Name IMS DRI LORI LTSC

Acquire_LR

Assembly_LR

Desassembly_LR

Detect_platform

Publish_LR

Evaluate_LR

Outline

Introduction

The main catalogue Example: composition of primitive scenarios

A composed scenario-typeDiagram of composition

Conclusions and future work

Example of scenario-type

Save_composed_LR - Create a new learning resource from the other two primitive scenario-types knowing their resource identifiers

SCPThe semantic conformance profile is used to obtain a scenario-types specification in an oriented way to automation:

A composed scenario-type

Name_scenario Preconditions Restrictions Post-conditions

Save_composed_LR id_LR1id_repo_1id_LR2,id_repo2comp_modeid_repository

Repositories availableSemantic coherence composition

The learning resource is composed in the repositorySaving justification

Example of scenario-type

Search_repository Search_repository

Retrieve_from_repository

Aggregation

Save_in_repository

Retrieve_from_repository

id_repository

composition_mode

id_repo1

id_LR1

url_resource_1

resource_1

resource

id_LR2

url_resource_2

id_repo2

resource_2

Diagram of composition

Conclusions and future work

Conclusions

There is not a cataloguing of learning scenarios available

A set of primitive scenario-types inspired on IMS-DRI, LORI and IEEE-LTSC is created

Some other scenario-types can be constructed using rules and combining other primitive scenario-types

Every scenario-type can be specified using semantic conformance profiles in order to obtain a specification oriented to automation

Conclusions and future work

Future work

Increase the catalogue defining new scenario-types and new composition rules

Create an ontology to support the specification of learning scenarios in order to define them in a formal way

Use the ontology to validate new scenario-types in order to assure their correct and consistent behaviour in the system

From the formal specifications of learning scenario-types executable specifications can be achieved

Thanks for your attention!

Feel free to contact me:mriusg@uoc.edu