<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?xml-stylesheet type="text/xsl" href="../part2stratml.xsl"?><PerformancePlanOrReport><Name>About SCORM</Name><Description>What is SCORM?SCORM is a set of technical standards for eLearning products. It provides the communication method and data models that allow eLearning content and LMSs to work together. It tells programmers how to write code so that what they build will “play well” with other eLearning software. SCORM is the most widely used eLearning standard available.</Description><OtherInformation>Why should I use SCORM?The biggest benefit of SCORM is interoperability. If you create content, your client will need to upload that content into their LMS. If you are an LMS or Learning Platform provider, a client will want to import content from other sources. SCORM takes care of making sure content is compatible with an LMS and that an LMS can import, launch and track content.</OtherInformation><StrategicPlanCore><Organization><Name>SCORM.com</Name><Acronym>SCORMC</Acronym><Identifier>_85129640-aac6-11ec-b801-a40cf882ea00</Identifier><Description>SCORM.com is dedicated to helping you understand what SCORM is and how to use it. Whether you need to identify how it can benefit your business or uncover the technical details of adding it to your eLearning platform, SCORM.com can help. We strive to make SCORM conformance direct, simple, transparent and, in a word, easy.</Description><Stakeholder StakeholderTypeType="Organization"><Name>Rustici Software</Name><Description>Rustici Software is the company behind SCORM.com. We started this website back in 2005 as a way to help people understand and implement the SCORM standard, but we did not create the SCORM standard. SCORM was developed and is now managed by Advanced Distributed Learning Initiative (ADL) to support the Department of Defense and their objective of standardizing learning objects to promote portability of training across systems.Along with providing support and resources to help people navigate the SCORM standard, we also provide software solutions that help eLearning products comply with the standards and solve common problems that arise when implementing them.</Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>eLearning Products</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Learning Management Systems</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Learning Platform Providers</Name><Description/></Stakeholder></Organization><Vision><Description>eLearning content and LMSs work together</Description><Identifier>_851297f8-aac6-11ec-b801-a40cf882ea00</Identifier></Vision><Mission><Description>To provides the communication method and data models for eLearning content and LMSs</Description><Identifier>_851298d4-aac6-11ec-b801-a40cf882ea00</Identifier></Mission><Value><Name>Interoperability</Name><Description/></Value><Goal><Name>Technical Details</Name><Description>Specify the technical details for shareable courseware</Description><Identifier>_85129a32-aac6-11ec-b801-a40cf882ea00</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>SCORM specifies that content should:* Be packaged in a ZIP file.* Be described in an XML file.* Communicate via JavaScript.* Sequence using rules in XML. ^SCORM is composed of three sub-specifications* The Content Packaging section specifies how content should be packaged and described. It is based primarily on XML.* The Run-Time section specifies how content should be launched and how it communicates with the LMS. It is based primarily on ECMAScript (JavaScript).* The Sequencing section specifies how the learner can navigate between parts of the course (SCOs). It is defined by a set of rules and attributes written in XML.</OtherInformation><Objective><Name>Content Packaging</Name><Description>Package content in self-contained directories or ZIP files</Description><Identifier>_85129afa-aac6-11ec-b801-a40cf882ea00</Identifier><SequenceIndicator>1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>The SCORM Content Aggregation Model (CAM) specifies that content should be packaged in a self-contained directory or a ZIP file. This delivery is called a Package Interchange File (PIF). The PIF must always contain an XML file named imsmanifest.xml (the “manifest file”) at the root. The manifest file contains all the information the LMS needs to deliver the content. The manifest divides the course into one or more parts called SCOs. SCOs can be combined into a tree structure that represents the course, known as the “activity tree”. The manifest contains an XML representation of the activity tree, information about how to launch each SCO and (optionally) metadata that describes the course and its parts.</OtherInformation></Objective><Objective><Name>Run-Time Environment</Name><Description>Launch content in web browsers</Description><Identifier>_85129bae-aac6-11ec-b801-a40cf882ea00</Identifier><SequenceIndicator>2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>The run-time specification states that the LMS should launch content in a web browser, either in a new window or in a frameset. The LMS may only launch one SCO at a time. All content must be web deliverable and it is always launched in a web browser. Once the content is launched, it uses a well-defined algorithm to locate an ECMAScript (JavaScript) API that is provided by the LMS. This API has functions that permit the exchange of data with the LMS. The CMI data model provides a list of data elements (a vocabulary) that can be written to and read from the LMS. Some example data model elements include the status of the SCO (completed, passed, failed, etc), the score the learner achieved, a bookmark to track the learner’s location, and the total amount of time the learner spent in the SCO.</OtherInformation></Objective><Objective><Name>Sequencing &amp; Navigation</Name><Description>Navigate between SCOs and roll up progress data to the course level</Description><Identifier>_85129c94-aac6-11ec-b801-a40cf882ea00</Identifier><SequenceIndicator>3</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name>Content Authors</Name><Description/></Stakeholder><OtherInformation>The sequencing specification allows the content author to govern how the learner is allowed to navigate between SCOs and how progress data is rolled up to the course level. Sequencing rules are represented by XML within the course’s manifest. Sequencing operates on a tracking model that closely parallels the CMI data reported by SCOs during run-time. Sequencing rules allow the content author to do things like:* Determine which navigational controls the LMS should provide to the user (previous/next buttons, a navigable table of contents, etc).* Specify that certain activities must be completed before others (prerequisites).* Make some parts of a course count more than others toward a final status or score (creating optional sections or providing question weighting).* Randomly select a different subset of available SCOs to be delivered on each new attempt (to enable test banking, for instance).* Take the user back to instructional material that was not mastered (remediation).</OtherInformation></Objective></Goal></StrategicPlanCore><AdministrativeInformation><StartDate/><EndDate/><PublicationDate>2022-03-23</PublicationDate><Source>https://scorm.com/</Source><Submitter><GivenName>Owen</GivenName><Surname>Ambur</Surname><PhoneNumber/><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></AdministrativeInformation></PerformancePlanOrReport>
