These samples represent various scenarios possible when running content using the cmi5 runtime definitions. Most of these scenarios are based on the “Simple” Course Structure Example from Section 15.1 of the specification.
Some common attributes about all samples:
account.name property would be unique to the learner and the account.homePage unique to the LMSNormal unless specifiedDiscrepancies with the above are pointed out where necessary.
Typical session that does not result in the awarding of credit based on the MoveOn criteria because requisite statements are not sent. Shows the minimum, common session which includes Launched Statement, Fetch URL Response, LMS.LaunchData State content, Initialized Statement, and Terminated Statement.
Session from an AU that has its Move On criteria set to CompletedOrPassed that has a Passed Statement recorded. LMS.LaunchData content shows CompletedOrPassed Move On criteria as does the Launched Statement context extensions. Note that the Satisfied Statement is issued immediately following the Passed Statement.
Session from an AU that has its Move On criteria set to CompletedOrPassed that has a Completed Statement recorded. LMS.LaunchData content shows CompletedOrPassed Move On criteria as does the Launched Statement context extensions. Note that the Satisfied Statement is issued immediately following the Completed Statement.
Session from an AU that has its Move On criteria set to CompletedOrPassed that has a Failed Statement recorded followed by a Completed Statement. Note that the Satisfied Statement is issued immediately after the Completed Statement, regardless of the Failed Statement’s existence.
Session from an AU that has its Move On criteria set to Completed that has a Completed Statement recorded. LMS.LaunchData content shows Completed Move On criteria as does the Launched Statement context extensions. Note that the Satisfied Statement is issued immediately following the Completed Statement.
Session from an AU that has its Move On criteria set to Passed that has a Passed Statement recorded. LMS.LaunchData content shows Passed Move On criteria as does the Launched Statement context extensions. Note that the Satisfied Statement is issued immediately following the Passed Statement.
Session from an AU that has its Move On criteria set to Passed and includes a Mastery Score that has a Passed Statement with score recorded. LMS.LaunchData content shows Passed Move On criteria and 0.9 Mastery Score as does the Launched Statement context extensions.
Session from an AU that has its Move On criteria set to CompletedAndPassed that has both a Passed Statement and a Completed Statement recorded. LMS.LaunchData content shows CompletedAndPassed Move On criteria as does the Launched Statement context extensions. Note that the Satisfied Statement is issued following the Completed Statement and not after the earlier Passed Statement.
Same as the Completed and Passed Move On scenario but with a passing score recorded. Note Passed statement includes result.score.scaled of 0.88 which is greater than the Mastery Score of 0.86 as defined in the LMS.LaunchData, Launched Statement, and Passed Statement.
Same as the Completed and Passed Move On with Mastery Score scenario but with an initial Failed Statement. Note Failed statement includes result.score.scaled of 0.82 which is less than the Mastery Score of 0.86 as defined in the LMS.LaunchData, Launched Statement, and Failed Statement. The following Passed statement includes a result.score.scaled of 0.91 which is greater than the Mastery Score of 0.86 which is also included in the Passed Statement.
Session showing the use of “cmi5 allowed” Statements. Includes a single “cmi5 allowed” Statement using the “experienced” verb. Note the statement must happen between the Initialized and Terminated statements and uses the context template from the LMS.LaunchData.
Session showing the use of the “progress” extension. Includes 3 “cmi5 allowed” Statements that have an increasing progress of 25% (25), 50% (50), and 75% (75) followed by a Completed Statement. Note the “progress” extension is not included in the Completed Statement.
Multiple session scenario showing a CompletedAndPassed Move On criteria where the Passed and Completed Statements occur in separate sessions. Note LMS.LaunchData differs between the two because the session identifier is contained therein. Each session includes distinct Launched, Initialized, and Terminated Statements which include distinct context because of the distinct sessions.
Session with a Launch Mode of Review. Likely a previous session has recorded completion and pass or waived. Note the Launch Mode value in the Launched Statement context extensions and the LMS.LaunchData.
Session that includes the absolute minimum data, and is associated with a NotApplicable Move On criteria which results in immediate satisfaction of the course upon registration creation. Includes Satisfied Statement.
Session that is abandoned, essentially a session without a Terminated Statement. Includes Launched Statement, LMS.LaunchData State content, Initialized Statement, and Abandoned Statement.
In this scenario the learner :
Note that standard cmi5 verbs are used in cmi5 allowed statements as well as non-standard verbs (exit-before-completing).
In this scenario The learner:
Note the standard cmi5 verbs, allowed statements, and cmi5 defined statements. Also note that the satisfied verb issued for the activity is a “cmi5 allowed” statement per the best practice (Best Practice #13 – LMS create “satisfied” statements for AU’s.)
Copyright 2012-2016 Advanced Distributed Learning (ADL) Initiative, U.S. Department of Defense
Licensed under the Apache License, Version 2.0 (the “License”). You may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.