IT Education : SCORM for E-Learning Standard Content

Background

• Creation and deployment of high-quality eLearning content
• Different Learning Management Systems have very different delivery environments and tracking tools
• Need for interoperable content : Durable, portable between systems and reusable in amodular fashion

Overview

A collection of specifications adapted from multiple sources to provide a comprehensive suite of e-learning capabilities that enable interoperability, accessibility and reusability of Web-based learning content. It's developed by the Advanced Distributed Learning initiative (ADL). LMS also implement SCORM API (API Adapter). The communication is over API Adapter (Java Script) and there is nothing for User Interface standard.

SCORM 2004 introduced a complex idea called sequencing, which is a set of rules that specifies the order in which a learner may experience content objects. In simple terms, they constrain a learner to a fixed set of paths through the training material, permit the learner to "bookmark" their progress when taking breaks, and assure the acceptability of test scores achieved by the learner. The standard uses XML, and it is based on the results of work done by AICC, IMS Global, IEEE, and Ariadne.

Concepts

Reusable

Content is independent of learning context. It can be used in numerous training situations or for many different learners with any number of development tools or delivery platforms.

Example : Content developed by a refinery to train its employees to respond to a petroleum spill could be reused by the fire department as part of a hazardous materials training program.

Interoperable  

Content will function in multiple application, environment, and hardware & software configurations regardless of the tools used to create it and the platform on which it is delivered.

Example : Content developed in one authoring system where the delivery platform is a CD on a non-networked Macintosh will also operate over the web on a PC using booth internet explorer and Netscape equally well.

Durable

Content does not require modification to operate as software systems and platforms are changed or upgrade.

Example : Upgrading an operating system from Windows NT to Windows 2000 has no impact on the delivery of content to the learner.

Accessible 

Content can be identified and located when it is needed to meet training and education requirements.

Example : A manager can conduct an online search for training on sexual harassement and identify appropriate materials for her specific organizational needs base on information provided in the content metadata.

SCORM Version

1. SCORM 1.0
• The first version: proof of concept only
• Introduced the notion of Shareable Content Object (SCO) and the API model in which the burden of managing communication latency across the Internet is handled by the runtime environment, not by the content objects


2. SCORM 1.1
• The first release: a “trial balloon”, not fully functional
• Used a Course Structure Format XML file to describe content structure, but lacked a robust packaging manifest and support for metadata
• Quickly abandoned in favor of SCORM 1.2


3. SCORM 1.2
• The first “real” release, with a real conformance test in the form of a test suite
• Uses IMS Content Packaging specification with full content manifest and support for metadata describing the course
• Lacks sequencing
• No longer maintained or supported by ADL


4. SCORM 2004 (formerly SCORM 1.3)
• The current version 
• Includes ability to specify adaptive sequencing of activities that use the content objects
• Includes ability to share and use information about success status for multiple learning objectives or competencies across content objects and across courses for the same learner
• A more robust test suite

SCORM Specifies

1. The aggregations of content objects for portability
• How reusable web-based content objects can be aggregated into a portable package that includes a manifest to form a larger self contained content object
• A SCORM manifest provides a detailed description of the content of the SCORM package


2. Unless the activity prescription forbids it, the user can also navigate from SCO to SCO through controls provided in the runtime environment's user interface


3. The SCO must establish a communication session with the runtime environment, with a standard set of data elements


4. This includes tracking data that allows the SCO to report success and progress, as well as other information about the status of content objectives, results of interactions.


5. Content aggregation package vs. Content resource package


6. Content aggregation package
• Contains a manifest element named organization, that is a special section which describes how the content objects are organized for delivery
• An organization element defines a tree of activities and sub-activities that use the content objects


7. Content resource package
• Does not include any organization information 
• Not intended for delivery to a learner
• Used to move amorphous collections of content objects from one system to another, or to archive a collection of content objects


8. Adaptive sequencing behaviors for activities
• By default, no sequencing information associated with the activity tree 
• The runtime environment shows all the activities and let the learner choose what to do