Simulation Tracking Object

Reference Model

(STORM)

Outlines • Goal

- Introduction

- SCORM

- The Goal

- Why SCORM is not enough?

- Related Works

• Modeling - What are the problems?

- Simulation Modeling

- Objective Modeling

- Run-Time Environment

• Design

- Objective Model Design

- STORM RTE Design

- OMDT

Introduction

E-Learning Systems

Learner

E-Learning Content

SCORM

• Sharable Content Object Reference Model.

• Advanced Distributed Learning (ADL) Initiative

directed by U.S. Department of Defense (DoD),

January 2000.

• A software model that defines the interrelationship of

course components, data models, and protocols such

that content “objects” are sharable across systems

that conform with the same model.

Sharable Content Object (SCO)

Content Structure

SCOs & Assets

Asset

Run-Time Environment (RTE)

The Goal

• Enabling the embedded interactive simulation in the SCO to be tracked by the LMS at run time.

Why SCORM is not enough?

• “An Asset does not communicate to the LMS via the API and data model.”

Reference

SCORM® 2004 4th Edition,

Run-Time Environment (RTE) Book, Page 26.

Related Works - HLA

• High Level Architecture.

• Defense Modeling & Simulation Office (DMSO) of the

U.S. Department of Defense (DoD), September 1996.

• Standard framework that enables simulations to be

composed of different simulation components.

HLA Functionality

HLA Components

• Federation Rules

– Ensure proper interaction of simulations in a federation.

– Describe the simulation and federate responsibilities.

• Interface Specification

– Defines Run-Time Infrastructure (RTI) services.

– Identifies “callback” functions each federate must provide.

• Object Model Template (OMT)

– Provides a standard method for simulation modeling.

– Establishes the format of key models:

• Federation Object Model (FOM)

• Simulation Object Model (SOM)

HLA-SCORM Integration

• A prototype system that integrates HLA compliant

simulation with SCORM compliant instruction.

SRML

• Simulation Reference Markup Language.

• World Wide Web Consortium (W3C), December 2002.

• An application of XML for describing simulation

models, and its runtime environment is software that

is capable of executing those models.

SRML

• The goal of SRML is to enable simulations to be

served, received, and processed in a standard fashion

using Internet technologies and the World Wide Web,

just as HTML enables that functionality for text, and

MathML enables that functionality for mathematics.

• SRML combines XML and scripts to encode both the

structure and behavior of all items comprising a

simulation.

SRML

BOM

• Base Object Model

• Simulation Interoperability Standards Organization

(SISO), January 2006

• A piece part of a conceptual model, simulation object

model (SOM), or federation object model (FOM), which

can be used as a building block in the development

and/or extension of a simulation or federation.

BOM

Mega-BOM

• A prototype model for composing BOM with SRML.

• Mapping between BOM entities and SRML elements.

• The goal of Mega-BOM is to facilitates the

development of simulation by BOM conceptual

modeling and SRML behavioral markup.

• But, there are no released specifications or standards

until now.

ECS Model

• Enables Delta3D game engine to be launched and

tracked by SCORM-compliant LMS.

• There is no need for simulation modeling, only

Delta3D simulations used.

• Translates simulation interactions into tasks and

objectives.

• Uses an Assessment Module for events tracking and

objectives evaluation.

ECS Model

Outlines • Goal

- Introduction

- SCORM

- The Goal

- Why SCORM is not enough?

- Related Works

• Modeling - What are the problems?

- Simulation Modeling

- Objective Modeling

- Run-Time Environment

• Design

- Objective Model Design

- STORM RTE Design

- OMDT

So, What are the Problems?

Most LMSs are SCORM-compliant

SCORM-Compliant LMS

Simulation must be modeled

HLA - OMT

OMT-Modeled Simulation

Objectives must be modeled

Objective Model

Objective Model formally

described using Z Language

Simulation with Objectives

Responsibilities of

Run-Time Environment

must be defined

Run-Time Environment

Complete View

Outlines • Goal

- Introduction

- SCORM

- The Goal

- Why SCORM is not enough?

- Related Works

• Modeling - What are the problems?

- Simulation Modeling

- Objective Modeling

- Run-Time Environment

• Design

- Objective Model Design

- STORM RTE Design

- OMDT

Objective Model Design

• The simulation has an ordered sequence of objectives,

and must be done sequentially.

Objectives

• Each objective has an ordered sequence of tasks,

and must be done sequentially.

Tasks

• Each task has a collection of the following items:

Event A specific event with specific parameters and count.

Panel A specific ordered\unordered collection of Events, Panels or Pools.

Pool A specific set of Events or Panels with a specific maximum.

Tasks

Document Type Definition (DTD) <!-- Elements -->

<!ELEMENT simulationObjectives (objective+)>

<!ELEMENT objective (task+)>

<!ELEMENT task (panel)>

<!ELEMENT panel (panel|pool|event)+>

<!ELEMENT pool (panel|event)+>

<!ELEMENT event (parameter*)>

<!ELEMENT parameter EMPTY>

<!-- objective's attributes-->

<!ATTLIST objective id CDATA #REQUIRED>

<!ATTLIST objective name CDATA #IMPLIED>

<!ATTLIST objective description CDATA #IMPLIED>

<!-- task's attributes-->

<!ATTLIST task id CDATA #REQUIRED>

<!ATTLIST task name CDATA #IMPLIED>

<!ATTLIST task description CDATA #IMPLIED>

<!ATTLIST task reaction CDATA #IMPLIED>

<!-- panel's attributes-->

<!ATTLIST panel id CDATA #REQUIRED>

<!ATTLIST panel name CDATA #IMPLIED>

<!ATTLIST panel description CDATA #IMPLIED>

<!ATTLIST panel ordered CDATA #REQUIRED>

<!-- pool's attributes-->

<!ATTLIST pool id CDATA #REQUIRED>

<!ATTLIST pool name CDATA #IMPLIED>

<!ATTLIST pool description CDATA #IMPLIED>

<!ATTLIST pool count CDATA #IMPLIED>

<!-- event's attributes-->

<!ATTLIST event id CDATA #REQUIRED>

<!ATTLIST event interactionClassName CDATA #REQUIRED>

<!ATTLIST event description CDATA #IMPLIED>

<!ATTLIST event count CDATA "1">

<!-- parameter's attributes-->

<!ATTLIST parameter id CDATA #IMPLIED>

<!ATTLIST parameter parameterName CDATA #REQUIRED>

<!ATTLIST parameter description CDATA #IMPLIED>

<!ATTLIST parameter restriction CDATA #IMPLIED>

STORM RTE Design

RTI Ambassador

RTI Ambassador

• Depends on HLA-RTI.

• Handles events routing to and from the simulation.

• Implements the following APIs: - sendInteraction()

- sendInteractionWithRegion()

- sendOrderToSimulation()

- The rest of HLA-APIs.

Assessment Module

Assessment Module

• Responsible for objectives evaluation.

• Uses the Objective Model XML file.

• Implements the following APIs: - initializeModule()

- updateObjectiveStatus()

- getObjectiveCompletionStatus()

- getCurrentObjectiveCompletionStatus()

- getTaskCompletionStatus()

- getCurrentTaskCompletionStatus()

LMS Communicator

LMS Communicator

• Responsible for communicating with LMS.

• Uses the SCORM APIs and Data Model Elements.

• Implements the following APIs: - setInteraction()

- getInteraction()

- setObjective()

- getObjective()

RTE Manager

SRTE Manager

• Responsible for:

- Managing the SRTE workflow.

- Responsible of SRTE initialization.

• Implements the following APIs:

- initialize()

- resume()

Services

Services

• Provides facilities to other SRTE components in order to

function well.

• These services include:

– XML files management.

– String manipulation.

– Calculative operations.

– Other services.

SRTE Workflow

RTI Ambassador

LMS Simulation LMS

Communicator

Assessment Module

Events

Orders

Interactions

Reactions Actions

Data 1

7

4 6

Objective Status

5

2 3

OMDT

• Objective Model Designing Tool

• A graphical authoring tool for building Simulation

Tracking Object (STO) that is an ordinary SCO but

contains:

- Simulation asset.

- XML file for OMT Model.

- XML file for Objective Model.

- SRTE JavaScript-implementation.

5

1

2

3

4

6