< Previous | Contents | Next >
1.2. Run-Time Environment Overview
This book defines the SCORM RTE model, which details the requirements for launching content objects, establishing communication between LMSs and SCOs, and managing the tracking information that can be communicated between SCOs and LMSs. In the context of SCORM, content objects are either:
SCOs, which communicate during run-time, or
Assets, which do not communicate during run-time.
The SCORM RTE book describes a common content object launch mechanism, a common communication mechanism between content objects and LMSs, and a common data model for tracking a learner’s experience with content objects. These aspects create an environment where several of the ADL “-ilities” are satisfied. For example, content objects that communicate through the standardized communication mechanism can be moved from LMS to LMS without modification to their communication attempts; this increases learning object portability and durability, thereby lowering the cost of development, installation and maintenance.
The SCORM RTE defines a model that picks up at the point when a specific content object has been identified for launch. The actual identification of the content object to be launched is out of scope of this book and can be found in the SCORM SN book [11].
This book only deals with the management of the run-time environment, which includes:
The delivery of a content object to the learner’s Web browser (i.e., launch)
If necessary, how a content object communicates with the LMS
What information is tracked for a content object and how the LMS manages that information
The following sections explain the relationships between the SCORM RTE book and the remaining SCORM books. In addition, frequently used terminology will be introduced at a high level to eliminate the need for the reader to become an expert in the entire SCORM to understand this book. This, however, is not an effective method to learn and apply SCORM and its concepts as a whole. It is strongly recommended that each SCORM book be read to more fully understand the purpose, details, relationships and advantages of all of the SCORM concepts.
SCORM was developed to enable the development of content objects that are reusable and interoperable across multiple LMSs. For this to be possible, there must be a common way to launch and manage content objects, a common mechanism for content objects to communicate with an LMS and a predefined language or vocabulary forming the basis of the communication.
The Launch process defines a common way for LMSs to start Web-based content objects. The term “content object” is used generically here to describe any piece of content that can be launched for a learner. In SCORM, there are two types of content objects: SCOs and Assets. The launch process defines procedures and responsibilities for the establishment of communication between the launched content object and the LMS. The communication mechanism is standardized with a common API.
The API is the communication mechanism for informing the LMS of the conceptual communication state between a content object and an LMS (e.g., initialized, terminated and/or in an error condition), and is used for retrieving and storing data (e.g., score, time limits, etc.) between the LMS and the SCO.
A Data Model is a standard set of data model elements used to define the information being tracked for a SCO, such as the SCO’s completion status or a score from an assessment such as a quiz or a test. In its simplest form, the data model defines data model elements that both the LMS and SCO are expected to “know about.” The LMS must maintain the state of SCO’s data model elements across learner sessions, and the SCO must utilize only these predefined data model elements to ensure reuse across multiple systems.
This page intentionally left blank.