Example SCORM courses

Sample SCORM course screenshotThe Golf Examples are a set of sample SCORM packages that illustrate the technical principles of SCORM. The SCORM examples offset with a set of basic HTML pages that contain instructional information virtually the game of golf. The instructional content is mediocre at best (information technology'south just text pulled from Wikipedia and Wikihow), but that'due south not the signal. These examples are most the technical guts of SCORM.

The SCORM package examples showtime elementary and then build on each other to create a fully functional SCORM conformant grade. Examples are provided in different versions of the standards as needed. For example, the unproblematic content packaging examples are provided for all versions of SCORM so that they tin can be used as templates. However afterwards examples, which build on the previous examples are but provided in limited versions because the differences betwixt versions are negligible.

If you're just looking for the most general example, download the SCORM 2004 Basic Run-time Package. Or feel free to Download All Golf Examples.

SCORM Content Packaging Examples

These first examples demonstrate the content packaging aspect of SCORM. They are not intended to be fully functional courses, rather they simply demonstrate the proper way to create an imsmanifest.xml file, add metadata and package the course.

Simple Single SCO

This example demonstrates the most bones content packet. Information technology simply considers all of the files within the grade to be part of a unmarried SCO that is listed in the manifest and packaged up. This example is provided for all versions of SCORM. They are useful as templates for creating more complicated manifests for each standard. Notice the differences in the SCORM manifests for each SCORM version:

This example demonstrates the nigh basic content package. It simply considers all of the files inside the course to be role of a single SCO that is listed in the manifest and packaged up. This example is provided for all versions of SCORM. They are useful as templates for creating more complicated manifests for each standard. Notice the differences in the SCORM manifests for each SCORM version:

  • The XML proper name space information (xmlns) in the manifest tag is different for each SCORM version. These differences are related to the [intlink id="xml-schema-definition-files"]XML schema definition files[/intlink] that are included with each form.
  • The schema and schema version elements in the manifest's metadata tag have different values in each version of the standard. In SCORM 2004, these values are required to have specific values.
  • The adlcp:scormType attribute on the resource element is slightly different between SCORM i.two and SCORM 2004. In SCORM 1.2, the aspect is named "adlcp:scormtype", whereas in SCORM 2004, the aspect is named "adlcp:scormType" (note the example of the letter "T").
  • SCORM 1.one uses a completely different content packaging format known as "content construction format" or "CSF".

When more than than 1 HTML page is office of a SCO, the SCO is responsible for providing the navigation interface for navigation within the SCO. This case is missing that navigation, it will exist added afterwards in the run-time examples.

Download (not functional)
SCORM 1.i [Complete Example] [View Manifest]

SCORM ane.2 [Complete Example] [View Manifest]

SCORM 2004 second Edition [Complete Example] [View Manifest]

SCORM 2004 3rd Edition [Consummate Example] [View Manifest]

The Metadata Example

The example builds upon the Simple Unmarried SCO example by adding descriptive metadata to the manifest file. Every metadata element inside LOM is used in an advisable context. Metadata may exist divers at many levels within the manifest. It can be attached to the manifest itself, an arrangement, an item, a resources or a file. This example demonstrates metadata in all locations. Metadata can also exist included directly within the manifest (in-line) or in a separate external file referenced from within the manifest. Both methods of defining metadata are included in this instance.

Download (not functional)
SCORM 2004 3rd Edition [Consummate Example] [View Manifest] [View Form Metadata]

Multi-SCO Example (Ane Folio Per SCO)

In this instance, each HTML file is treated as a separate SCO. The SCOs are aggregated into four items that correspond the unlike topics covered inside the course. Some things to notice in this example:

  • Use of aggregations to class a logical class bureaucracy.
  • Use of the parameters attribute to pass querystring parameters into the shared quiz resource.
  • The utilise of resource typed as assets instead of SCOs because they do non communicate with the LMS.
  • The use of a common shared asset containing files that are reused across many SCOs. This asset is referenced through dependencies on the other resources.

Since this case relies on the LMS for navigation, it is the showtime functional instance that can be launched and run in an LMS. To be a complete and fully-functional course, it still needs some more work. That volition come afterwards. For now, attempt importing it into the [intlink id="scorm-cloud"]SCORM Deject[/intlink] to see how information technology looks.

Download (only partially functional)
SCORM 1.two [Complete Example] [View Manifest]
SCORM 2004 3rd Edition [Complete Case] [View Manifest]

Back to top

SCORM Run-Time Examples

These examples demonstrate the improver of SCORM run-time calls to the prior examples.

Minimum Run-Time Calls

This example builds on the Multi-SCO Case (One Folio Per SCO) to demonstrate the minimal required SCORM API calls. In this example:

  • All of the resources are marked as SCOs instead of Assets because they communicate with the LMS.
  • Each SCO will locate the SCORM API using the ADL-provided API discovery algorithm.
  • The SCOs simply phone call Initialize when they load and Terminate when they unload.
  • The run-time calls demonstrate bones SCORM fault handling.

Download
SCORM ane.2 [Complete Example] [View Manifest]
SCORM 2004 tertiary Edition [Complete Example] [View Manifest]

Basic Run-Fourth dimension Calls

This instance builds on the Uncomplicated Single SCO to demonstrate the proper utilize of the bones SCORM run-time data model elements. In this example:

  • A JavaScript controller is added to handle navigation within the SCO.
  • The controller bookmarks the learner'due south current location. (cmi.location)
  • The controller reports completion as the user progresses through the content. (cmi.completion_status)
  • The controller reports success status and score based on the learner's quiz results (cmi.success_status, cmi.score.scaled, cmi.score.raw, cmi.score, max and cmi.score.min).
  • The controller will tape the total fourth dimension the learner spent in the training (cmi.session_time).
  • The controller demonstrates options for exiting the form (cmi.go out and adl.nav.request)
  • The manifest includes some bones sequencing information to override some counter-intuitive default values.

Download
SCORM one.2 [Consummate Instance] [View Manifest]
SCORM 2004 3rd Edition [Complete Example] [View Manifest]

Avant-garde Run-Time Calls

This example builds on the Bones Run-Time Calls case to show more in-depth use of the SCORM run-time data model elements. Specifically, this example:

  • Defines four specific learning objectives for this course.
  • Reports individual question results (cmi.interactions).
  • Associates question results with learning objectives (cmi.interactions.due north.objectives).
  • Reports the learner'south progress towards completing each learning objective (cmi.objectives.n.progress_measure and cmi.objectives.due north.completion_status).
  • Breaks down the test results into results for each learning objective (cmi.objectives.score).
  • Records the learner's progress towards completion of the SCO (cmi.progress_measure).
  • Defines the passing score in the manifest rather than difficult coding it inside the SCO.
  • Demonstrates how to work with SCORM sequencing collections.

Download
SCORM 2004 tertiary Edition [Consummate Example] [View Manifest]

Back to top

Sequencing Examples

These examples demonstrate the employ of sequencing and navigation to combine the golf game content into sequenced courses. Several common and simple sequencing strategies are demonstrated. These examples demonstrate both the sequencing of the learner through the content likewise as strategies for rollup of status information.

Forced Sequential Society (Prerequisites)

Sequencing Strategy

This example demonstrates a sequencing strategy that requires the learner to visit all SCOs in order. Once a SCO has been visited, the learner can leap backwards to review cloth, simply the learner cannot jump alee until the prerequisites are met.

Rollup Strategy

  • Completion: All activities must exist completed for the course to exist completed.
  • Satisfaction: All activities must be satisfied for the course to be satisfied. Activities without an cess are satisfied when they are completed. Activities with an assessment measure out satisfaction based on the outcome of the assessment.
  • Score: No score is rolled up, all activities accept an objective measure weight of zero.

Also Notice:

  • The use of a sequencing collection to define sequencing rules that are common to every activity.
  • The use of global objectives to track satisfaction of learning objectives (which are likewise the prerequisites).
  • The sometimes counter-intuitive use of the "non" operator.
  • The use of precondition sequencing rules to disable activities until their prerequisites are met.

Download
SCORM 2004 tertiary Edition [Complete Example] [View Manifest]

Post Test Rollup

Sequencing Strategy

This example maintains the sequencing strategy from the Forced Sequential Order example. All SCOs must be visited in lodge initially, just once a SCO is completed, the learner may jump back to it at any time.

Rollup Strategy

The class can only exist completed and satisfied by completing and satisfying the post test. Because of the sequencing strategy that requires all other activities to exist completed before the mail service test can exist accessed, by implication, all activities must be completed for the course to exist completed. The score for the form is entirely dependent on the score from the post examination. This rollup strategy is implemented by setting every activeness except for the mail exam to non contribute to whatever rollup. When there is just 1 activity that contributes to rollup in a cluster, then cluster will receive that action'southward status by default during rollup.

Download
SCORM 2004 3rd Edition [Complete Case] [View Manifest]

Back to top

SCORM 2004 quaternary Edition Features

This case demonstrates some of the powerful new features available in SCORM 2004 quaternary Edition:

Sequencing Strategy

This instance maintains the sequencing strategy from the Forced Sequential Order and Mail Test Rollup examples. All SCOs must exist visited in order initially, just in one case a SCO is completed, the learner may jump dorsum to it at whatever time.

  • To demonstrate the new fourth Edition "spring" navigation request, the learner can at present skip straight to the test at anytime from within a SCO, bypassing all sequencing rules. If the learner is taking the content though, it still must be taken in lodge.
  • To demonstrate the boosted data that can be stored on global objectives, this example uses completion status equally the driver for prerequisites. In prior editions of SCORM 2004, merely success status was available on global objectives. In this instance, nosotros simply need the learner to complete the SCO not necessarily satisfy it.

Rollup Strategy

  • This example maintains the rollup strategy from the Forced Sequential Order and Post Test Rollup examples. It still works even though the sequencing strategy at present allows for jump request considering the rollup is entirely dependent on the post test.
  • To demonstrate the new rollup of progress measure, this example now includes weights on each SCO that represent their overall contribution to completion.

Also Detect

  • To demonstrate the value of the new shared data buckets in quaternary Edition, we added a notes feature that allows the learner to have brief notes and have them be bachelor in whatever SCO.

Download
SCORM 2004 4th Edition [Complete Example] [View Manifest]

Pretest or Mail service Test Rollup (Testing out)

Sequencing Strategy

  • The learner tin freely navigate through all activities in the course.
  • The pretest can only be attempted one time.
  • In one case whatever test is passed, all tests are disabled.
  • The mail service test can not be attempted until all content is completed.

Rollup Strategy

  • Completion, satisfaction and score are all tied to the most recently completed exam.
  • The learner tin "test out" past completing the pretest.
  • If the learner doesn't test out, achieving completion requires completing all SCOs. This is done implicitly past putting in sequencing rules that don't allow another test to be taken until all SCOs are completed.

Also Notice:

  • The apply of an invisible dummy clusters to simplify sequencing and rollup rules.
  • The utilise of the try limit sequencing aspect in conjunction with a precondition rule to disable the pretest after i attempt. Note how this requires setting cmi.get out to normal instead of suspend to end the endeavour.
  • The use of a global objective shared between the pre and mail tests to record satisfaction and score.

Download
SCORM 2004 3rd Edition [Complete Example] [View Manifest]

Randomized Testing (Test/Question Banking)

Sequencing Strategy

  • Content can be taken in any order.
  • The post test tin non exist accessed until all of the content is completed.
  • The mail examination is actually a test bank of 4 possible tests.
  • On each new try of the post test, one of the possible tests is randomly selected.
  • The learner gets two attempts to pass the mail test.
  • After the offset failed exam try, the learner immediately retries the test.
  • In one case the mail exam has been passed or attempted twice, the learner immediately exits.

Rollup Strategy

  • Overall form status is determined solely by the status of the post examination.
  • The post exam cluster is the only action that contributes to completion and satisfaction rollup. The mail service exam cluster's status is determined by rollup rules that say if any of the tests are satisfied, information technology is satisfied and completed.
  • Overall course score is read from a global objective (since we can't ready the score for the post examination cluster using a rollup dominion). The score of the last test attempted is the score for the course.

Also Detect:

  • The retry post condition on the post test cluster to attempt some other test subsequently failing.
  • The two separate retry rules on the post test cluster to achieve the logic (not satisfied AND not attempt limit exceeded) OR (unknown satisfaction AND non attempt limit exceeded). Combining AND and OR weather condition requires separate rules.
  • The exitAll rule to go out the grade once the post examination has been satisfied or the attempt limit has been reached.
  • Randomization controls to randomly select a new test.
  • The exitParent rule on each individual test to ensure that the mail examination cluster'south post condition sequencing rules are evaluated whenever a examination is completed.
  • The use of hideLMSUI to ensure that a examination is not exited with a suspendAll request. A suspendAll when the test is still active volition prevent the attempt count on the Post Exam aggregation from beingness incremented.

Download
SCORM 2004 3rd Edition [Complete Example] [View Manifest]

Elementary Remediation

Sequencing Strategy

  • Simply flow navigation is allowed.
  • There are iv learning objectives for this course. For each learning object, there is an associated content SCO and a test SCO.
  • Passing a test will satisfy the associated learning objective.
  • When a learning objective is satisfied, both the associated content SCO and exam SCO are skipped.
  • When the learner completes the course without satisfying all learning objectives, he is remediated back through the class merely skips all content/test that accept already been mastered.

Rollup Strategy

  • But the tests count towards rollup.
  • Each exam counts equally towards all rollup metrics.

As well Observe:

  • The dummy wrapper around the content to enable retry with retrying the root activity which would reset all of the global objective data.
  • The utilize of control choice get out on the retry wrapper to prevent access to selection requests on the root action (which would brainstorm a new try and reset data).
  • The rollup consideration of ifNotSkipped to ensure that tests that are skipped during remediation don't affect overall completion condition. (Satisfaction and measure aren't an issue because these are stored in the global objectives which are not reset.)
  • For more information about this sequencing strategy, see these web log posts:
    • Remediation is Hard, Part 1 – "Retry All Resets Everything"
    • Remediation is Hard, Part 2 – "If _____ then skip"

Download
SCORM 2004 tertiary Edition [Complete Example] [View Manifest]

Back to height

Have questions about SCORM? Ask us anything. We're here to help.