1. TELOS Architecture Presentation TELOS TELearning Operating System Architecture Presentation _________________________________ LORNET Research Network Montreal, November 19, 2003

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

3. Architecture Research Team Project Ochestrator: G. Paquette Principal 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. Banville Technology Watch:K. Lundgren-Cayrol Research professionals:S. Mihaila M. Vézeau Graduate student:A. Masmoudi

4. TELOS Position Statement Organizations need to respond to the huge challenges of the knowledge society and the new economy The exponential growth of information resources on the Internet demands computer systems with knowledge representation and inference capabilities for semantic search, processing and use. TELOS is positioned at the intersection of three major IT trends: LORs making available information resources, referenced by metadata and ontologies within the Semantic Web, to support knowledge management and learning.

5. Architecture Methodology Pre- Competitive R&D focus Operational Prototype Each Year

6. Architecture Documentation Implementation and Deployment (ID) Test Process (TP) Iteration 1Iteration 2 Iteration 3 Requirements Conceptual framework (CF) Software Architecture (SA) Analysis & Design Implementation Deployment Test Vision and Orientation (VO) Use case and specification (UC) Business Modeling Glossary of Terms (GT) LORNET Initial Proposal UC 0.2 UC 0.3UC 1.0 CF 0.2CF 0.3 VO 0.4 GT 0.4 VO 1.0 GT 1.0 CF 1.0 TELOS 0 TELOS 1

7. Orientation Principles Embedding models within DL and KM support systems Instructional engineering viewpoint compatible with international standards: LOM, CP, DRI, IMS-LD A semantic level view: Actors, operations, resources associated to knowledge using an ontology editor An approach to resource (LO) aggregation for emergent, planned/advised or directed activities Adapting, integrating, interacting with external LMSs and LCMSs components (reuse and interoperate)

8. Technology Orientations RUP iterative incremental architecture method based on user’s needs - UML diagrams Model Driven Architecture (PIM, PSM, Code) 3-levels Component Integration Browser Integration Web Services Communication Components Encapsulation, Scripting, Fusion on a Service Bus XML as main data exchange format) Interoperate components from different platforms: J2EE,.NET, … Open Source product Free of charge for public research and education Licensed to LORNET industrial partners

9. Cascade of TELOS Products TELOS CORE SYSTEM System Engineers 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

10. Main Use Cases Facilitator Helps Request/Provide services Participant TELOS Kernel Explore LKMA and LKMEs Design LKMA enables Builds LKMS use Engineer TELOS Core use LearnerDesignerTechnologist Engineer 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

11. TELOS core TELOS service client KNOWLEDGEKNOWLEDGE RESSOURCERESSOURCE AGGREGATEAGGREGATE SUPPORTSUPPORT CONTROlCONTROl Core systems (n) KNOWLEDGEKNOWLEDGE RESSOURCERESSOURCE AGGREGATEAGGREGATE SUPPORTSUPPORT CONTROlCONTROl KNOWLEDGEKNOWLEDGE RESSOURCERESSOURCE AGGREGATEAGGREGATE SUPPORTSUPPORT CONTROlCONTROl Core libraries TELOS Kernel : Agent coordination+ User connection + Object control Conceptual Framework Technologist Agent Engineer Agent External User Agent Designer Agent Learner Agent Participant Agent Core Administrator Agent LKMS Administrator Agent LKMA Administrator Agents LKMP Administrator Agent Facilitator Agents LKMS library LKMA libraryLKMP library KRSA C Embedded LKMS KRSA C KRSA C KRSA C KRSA C KRSA C Embedded LKMA KRSA C Embedded LKMS KRSA C KRSA C Embedded LKMP s1 s3 s5 s2 s4 s6 Requestor /provider System(s) s7

12. 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 Provide Support Facilitator Aggregate Resources Composer Reference And Manage LORs Content Analyst Install, Test Prepare Instances Administrator 1 2 3 4 5 2 6 5 1 2 Search Find and Use Resources Explorer

13. TELOS Use Cases (flow 1) Do a Federated Search ECL Orders results and Select DataM Builds a LKMA’s Sub-library ResMan Designer Composes a LKMA with 1 Learner’s Env. LKMA and one LKME Extends Learner’s LKME EnvB Technologist Prepares Designer’s Environments Core Components LKMS-1 Explora 2.1 Search for Resources 3DNav Learner navigates his LKME IHelp Builds a Collection (LKMP) RAgg Annotate Resources (LKMP) ResMan IMS-LD Community of Practice

14. TELOS Use Cases (flow 2) Technologist Prepares Designer’s Environments Core Components Explora 2.1 LKMS-3 Designer Generate Environments Designer Composes a LKMA with 3 Actor’s Env. Bind resources to operations ActEd Create a K-competency referential K-CEd Bind activities and competencies K-CEd Create a tree-function aggregate ActEd LKMA and 3 LKMEs Actors Navigate LKMEs Produce Products (LKMP) ProgT Learner’s and Facilitator’s Assessment AutoD Learner gets advice ProgT On-line Course on Nutrition

15. Summarizing Actual Potential Open, multi-actor and multi-model Telelearning system Resource-oriented management of courses Function as a tree structure (Activities/Resources + knowledge) Embedded assistance to operations International Standards integration (LOM, DRI, LD) Limitations to overcome Not yet a large control on resources Superficial interoperability (URLs and some web services) Actors not coordinated by visible processes Limited adaptive assistance, hard to integrate Interoperability between platforms is limited Workflows (Meta-functions) based on methods to integrate design, development, delivery operations are mainly lacking

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

17. TELOS-0 TELOS-0 Demonstration _________________________________ Explor@-based Prototype Montreal, November 19, 2003