The document outlines a proposed Simulation Tracking Object (STORM) model that allows embedded interactive simulations to be tracked by learning management systems (LMS) at runtime. STORM addresses limitations of SCORM, which does not allow direct communication between simulations and the LMS. STORM includes an objective model defined using XML, an RTI ambassador for routing events between the simulation and LMS, and an assessment module for evaluating objective completion status. It aims to provide a complete design for integrating simulation tracking capabilities into SCORM-compliant e-learning systems.

1. Simulation Tracking Object
Reference Model
(STORM)

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

3. Introduction
E-Learning
Content
Learner
E-Learning
Systems

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

5. Sharable Content Object (SCO)
Content Structure
SCOs & Assets

6. Asset

7. Run-Time Environment (RTE)

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

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

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

11. HLA Functionality

12. 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)

13. HLA-SCORM Integration
• A prototype system that integrates HLA compliant
simulation with SCORM compliant instruction.

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

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

16. SRML

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

18. BOM

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

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

21. ECS Model

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

23. So, What are the Problems?

24. Most LMSs are SCORM-compliant

25. SCORM-Compliant LMS

26. Simulation must be modeled

27. HLA - OMT

28. OMT-Modeled Simulation

29. Objectives must be modeled

30. Objective Model

31. Objective Model formally
described using Z Language

32. Simulation with Objectives

33. Responsibilities of
Run-Time Environment
must be defined

34. Run-Time Environment

35. Complete View

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

37. Objective Model Design
• The simulation has an ordered sequence of objectives,
and must be done sequentially.

38. Objectives
• Each objective has an ordered sequence of tasks,
and must be done sequentially.

39. Tasks
• Each task has a collection of the following items:
 Event
A specific event with specific parameters and count.
 Panel
A specific orderedunordered collection of Events, Panels or Pools.
 Pool
A specific set of Events or Panels with a specific maximum.

40. Tasks

41. Document Type Definition (DTD)
<!-- Elements --> <!-- pool's attributes-->
<!ELEMENT simulationObjectives (objective+)> <!ATTLIST pool id CDATA #REQUIRED>
<!ELEMENT objective (task+)> <!ATTLIST pool name CDATA #IMPLIED>
<!ELEMENT task (panel)> <!ATTLIST pool description CDATA #IMPLIED>
<!ELEMENT panel (panel|pool|event)+> <!ATTLIST pool count CDATA #IMPLIED>
<!ELEMENT pool (panel|event)+>
<!ELEMENT event (parameter*)> <!-- event's attributes-->
<!ELEMENT parameter EMPTY> <!ATTLIST event id CDATA #REQUIRED>
<!ATTLIST event interactionClassName CDATA #REQUIRED>
<!-- objective's attributes--> <!ATTLIST event description CDATA #IMPLIED>
<!ATTLIST objective id CDATA #REQUIRED> <!ATTLIST event count CDATA "1">
<!ATTLIST objective name CDATA #IMPLIED>
<!ATTLIST objective description CDATA #IMPLIED> <!-- parameter's attributes-->
<!ATTLIST parameter id CDATA #IMPLIED>
<!-- task's attributes--> <!ATTLIST parameter parameterName CDATA #REQUIRED>
<!ATTLIST task id CDATA #REQUIRED> <!ATTLIST parameter description CDATA #IMPLIED>
<!ATTLIST task name CDATA #IMPLIED> <!ATTLIST parameter restriction 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>

42. STORM RTE Design

43. RTI Ambassador

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

45. Assessment Module

46. Assessment Module
• Responsible for objectives evaluation.
• Uses the Objective Model XML file.
• Implements the following APIs:
- initializeModule()
- updateObjectiveStatus()
- getObjectiveCompletionStatus()
- getCurrentObjectiveCompletionStatus()
- getTaskCompletionStatus()
- getCurrentTaskCompletionStatus()

47. LMS Communicator

48. LMS Communicator
• Responsible for communicating with LMS.
• Uses the SCORM APIs and Data Model Elements.
• Implements the following APIs:
- setInteraction()
- getInteraction()
- setObjective()
- getObjective()

49. RTE Manager

50. SRTE Manager
• Responsible for:
- Managing the SRTE workflow.
- Responsible of SRTE initialization.
• Implements the following APIs:
- initialize()
- resume()

51. Services

52. Services
• Provides facilities to other SRTE components in order to
function well.
• These services include:
– XML files management.
– String manipulation.
– Calculative operations.
– Other services.

53. SRTE Workflow
Events
1 RTI Interactions LMS Data
Simulation
Communicator
LMS
Orders Ambassador 2 3
7
Reactions Actions
6 4
Objective
Status
Assessment 5
Module

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

55. 1
3
6
5
4
2