TELOSTELOS TELearning Operating System

Architecture PresentationArchitecture Presentation _________________________________

LORNETResearch Network

Montreal, November 19, 2003

Theme 6 Projects and Objectives

6.1 Build the Architecture of a TeleLearning

Operating System (TELOS)

6.2 Develop the TELOS System Kernel and integrate

tools, components and services from theme 1 to 5

6.3 Provide an Instructional Engineering Methodology

Adapted to Learning Object Repositories Network

6.4 Provide an Evaluation and Validation

Methodology and test TELOS products

ArchitectureResearch Team

Project Ochestrator: G. PaquettePrincipal Investigators: M. Hatala (theme 1)

I. Rosca (theme 2)C. Brooks (theme 3)O. Basir (theme 4) A. El Saddik (theme 5)S. Pierre (theme 6)

Project Manager: C. BanvilleTechnology Watch: K. Lundgren-CayrolResearch professionals: S. Mihaila

M. Vézeau Graduate student: A. Masmoudi

TELOS Position StatementOrganizations need to respond to the huge challenges of Organizations need to respond to the huge challenges of the knowledge society and the new economy the knowledge society and the new economy

The exponential growth of information resources on the The exponential growth of information resources on the Internet demands computer systems with knowledge Internet demands computer systems with knowledge representation and inference capabilities for semantic representation and inference capabilities for semantic search, processing and use. search, processing and use.

TELOS is positioned at the intersection of three major IT TELOS is positioned at the intersection of three major IT trends: trends:

LORs making available information resources, LORs making available information resources,

referenced by metadata and ontologies within the referenced by metadata and ontologies within the Semantic Web, Semantic Web,

to support knowledge management and learning. to support knowledge management and learning.

Architecture Methodology

Pre-CompetitiveR&D focus

Operational Prototype Each Year

Architecture Documentation

Implementation and Deployment (ID)

Test Process (TP)

Iteration 1 Iteration 2 Iteration 3

Requirements

Conceptual framework (CF)

Software Architecture (SA)

Analysis& Design

ImplementationDeployment

Test

Vision and Orientation (VO)Use case and specification (UC)

BusinessModeling

Glossary of Terms (GT) LORNET Initial Proposal

UC 0.2 UC 0.3 UC 1.0

CF 0.2 CF 0.3

VO 0.4

GT 0.4

VO 1.0

GT 1.0

CF 1.0

TELOS 0

TELOS 1

Orientation Principles

Embedding models within DL and KM support systemsEmbedding models within DL and KM support systems

Instructional engineering viewpoint compatible with Instructional engineering viewpoint compatible with international standards: LOM, CP, DRI, IMS-LDinternational standards: LOM, CP, DRI, IMS-LD

A semantic level view: Actors, operations, resources A semantic level view: Actors, operations, resources associated to knowledge using an ontology editorassociated to knowledge using an ontology editor

An approach to resource (LO) aggregation for An approach to resource (LO) aggregation for emergent, planned/advised or directed activitiesemergent, planned/advised or directed activities

Adapting, integrating, interacting with external LMSs Adapting, integrating, interacting with external LMSs and LCMSs components (reuse and interoperate)and LCMSs components (reuse and interoperate)

Technology OrientationsRUP iterative incremental architecture method RUP iterative incremental architecture method based on user’s needs - UML diagramsbased on user’s needs - UML diagramsModel Driven Architecture (PIM, PSM, Code)Model Driven Architecture (PIM, PSM, Code)3-levels Component Integration3-levels Component Integration

Browser IntegrationBrowser IntegrationWeb Services CommunicationWeb Services CommunicationComponents Encapsulation, Scripting, Fusion on a Service Components Encapsulation, Scripting, Fusion on a Service BusBus

XML as main data exchange format)XML as main data exchange format)Interoperate components from different platforms: Interoperate components from different platforms: J2EE, .NET, …J2EE, .NET, …Open Source productOpen Source product

Free of charge for public research and educationFree of charge for public research and educationLicensed to LORNET industrial partnersLicensed to LORNET industrial partners

Cascade of TELOS Products

TELOSCORE

SYSTEM

SystemEngineers

Level IV

LKMS 1

LKMS 2

LKMS K

Technologists

Level III

LKMA 2.1

LKMA 2.2

LKMA 2.M

Designers

LKME 2.2A

LKME 2.2B

LKME 2.2N

Level II

Learners or Facilitators

LKMP2.2A1

LKMP2.2A2

LKMP2.2A3

LKMP2.2AP

Level I

Main Use Cases

FacilitatorHelps

Request/Provide services

Participant

TELOS Kernel

Explore LKMA and LKMEs

Design LKMA

enables

Builds LKMS

use

Engineer TELOS Core

use

LearnerDesignerTechnologistEngineer

Level I Produce /Use

LKMP

Level lI Compose / Use

LKMA

Level lII Compose / Use

LKMS

Level lV Evolve / Use

LKMS

Administrates Libraries

Administrator

Uses core, LKMS, LKMA or LKMP

External requestor

Provides core, LKMS, LKMA or LKMP

External Provider

TELOS core

TELOS service client

KNOWLEDGE

RESSOURCE

AGGREGATE

SUPPORT

CONTROl

Core systems (n)

KNOWLEDGE

RESSOURCE

AGGREGATE

SUPPORT

CONTROl

Core systems (n)

KNOWLEDGE

RESSOURCE

AGGREGATE

SUPPORT

CONTROl

Core systems (n)

Core libraries

TELOS Kernel: Agent coordination+ User connection + Object control

Conceptual Framework

TechnologistAgent

EngineerAgent

External User Agent

DesignerAgent

LearnerAgent

ParticipantAgent

Core Administrator

Agent

LKMS Administrator

Agent

LKMAAdministrator

Agents

LKMPAdministrator

AgentFacilitator

Agents

LKMS library LKMA library LKMP library

K R SA C

Embedded LKMS

K R SA C

Embedded LKMS

K R SA C

Embedded LKMS

K R SA C

Embedded LKMS

K R SA C

Embedded LKMS

K R SA C

Embedded LKMA

K R SA C

Embedded LKMS

K R SA C

Embedded LKMS

K R SA C

Embedded LKMP

s1

s3 s5

s2

s4

s6Requestor/provider System(s)

s7

Cascade and Generic Use Cases

Learner

Designer

Technologist

Engineer

Level I Produce

LKMP

Level lI Compose

LKMA

Level lII Compose

LKMS

Level lV Evolve Core

ProvideSupport

Facilitator

AggregateResources

Composer

ReferenceAnd Manage

LORs

Content Analyst

Install, TestPrepare

Instances

Administrator

12 34 5 2

6

5 1 2

Search Find and Use

Resources

Explorer

TELOS Use Cases (flow 1)Do a

FederatedSearch

ECL

Orders results

and Select

DataM

Builds a LKMA’s

Sub-library

ResMan

DesignerComposes aLKMA with 1

Learner’s Env.

LKMA and one LKME

ExtendsLearner’s

LKME

EnvB

TechnologistPrepares

Designer’sEnvironments

CoreComponents

LKMS-1

Explora 2.1 Search for Resources

3DNav

Learnernavigateshis LKME IHelp

Builds aCollection

(LKMP)RAgg

Annotate Resources

(LKMP)

ResMan

IMS-LDCommunityof Practice

TELOS Use Cases (flow 2)

TechnologistPrepares

Designer’sEnvironments

CoreComponents

Explora 2.1

LKMS-3

DesignerGenerate

Environments

DesignerComposes aLKMA with 3Actor’s Env.

Bind resources tooperations ActEd

Create a K-competency

referential

K-CEd

Bind activities and competencies

K-CEd

Create a tree-function

aggregate

ActEd

LKMA and 3 LKMEs

ActorsNavigateLKMEs

Produce Products(LKMP)

ProgT

Learner’s andFacilitator’sAssessment AutoD

Learnergets advice

ProgT

On-lineCourse onNutrition

Summarizing

Actual PotentialActual PotentialOpen, multi-actor and multi-model Telelearning systemOpen, multi-actor and multi-model Telelearning system

Resource-oriented management of courses Resource-oriented management of courses

Function as a tree structure (Activities/Resources + knowledge)Function as a tree structure (Activities/Resources + knowledge)

Embedded assistance to operationsEmbedded assistance to operations

International Standards integration (LOM, DRI, LD)International Standards integration (LOM, DRI, LD)

Limitations to overcomeLimitations to overcomeNot yet a large control on resources Not yet a large control on resources

Superficial interoperability (URLs and some web services)Superficial interoperability (URLs and some web services)

Actors not coordinated by visible processesActors not coordinated by visible processes

Limited adaptive assistance, hard to integrateLimited adaptive assistance, hard to integrate

Interoperability between platforms is limitedInteroperability between platforms is limited

Workflows (Meta-functions) based on methods to integrate design, Workflows (Meta-functions) based on methods to integrate design, development, delivery operations are mainly lackingdevelopment, delivery operations are mainly lacking

R&D GoalsAutonomous resources and system components, Autonomous resources and system components, reusable in different contexts, for different actors, from reusable in different contexts, for different actors, from different systems.different systems.Encapsulation of resources in an abstract layer, to Encapsulation of resources in an abstract layer, to manipulate and enable aggregation.manipulate and enable aggregation.Integrating metadata and ontology to move the system Integrating metadata and ontology to move the system at the Semantic Web levelat the Semantic Web levelEmbedding interactive graphic models as a meaningful Embedding interactive graphic models as a meaningful context to help multi-actor coordinationcontext to help multi-actor coordinationBuilding an API to help engineers improve core libraries : Building an API to help engineers improve core libraries : aggregators, binders, controllers, translators,…aggregators, binders, controllers, translators,…Integration methodology for portals, platforms, and Integration methodology for portals, platforms, and telelearning services (distributed platforms)telelearning services (distributed platforms)Develop Innovative Design Methods for LD and KMDevelop Innovative Design Methods for LD and KMTest Bed the TELOS Product with Appropriate Users Test Bed the TELOS Product with Appropriate Users and develop and evaluation methodologyand develop and evaluation methodology

TELOS-0TELOS-0 Demonstration

_________________________________

Explor@-basedPrototype

Montreal, November 19, 2003