SCORM Developers Blog

The SCORM Developer blog contains information pertaining to SCORM development, including experiences of SCORM developers, tips-and-tricks, and best-practices.

Friday, July 6, 2007

SCORM Shareable Content Objects (SCOs)

A Shareable Content Object (SCO) is a launchable learning object (resource) that communicates with the run-time environment that launched it. A SCO must be designed so that it can be launched in a standalone web window, or in a frame in a HTML frameset.

A SCO is special because when launched for a learner, in the learner's web-browser, it will communicate information back to the LMS that launched it, often a remote server. This communication allows the LMS to track information pertaining the learner's experience.

Typical SCO Lifecycle:

  1. SCO is launched by a SCORM Run-Time Environment (RTE) (often an LMS)
  2. SCO finds RTE provided API
  3. SCO begins communication with the RTE API (via a call to Initialize())
  4. Learner begins interaction with the SCO
  5. SCO sends and retreives data via the RTE API (via calls to Get/SetValue())
  6. Learner ends interaction with the SCO
  7. SCO ends communication with the RTE API (via a call to Terminate())

Learn more about Shareable Content Objects (SCOs) at Redbird DevNet, the SCORM Developer Network, by clicking here...

0 comments: