SCORM Application

Candace Filip, Instructional Designer

Aaron Silvers, Content Developer

ADL Technology Center

2

Goals

• To demonstrate four SCORM 2004 content examples

• Describe lessons learned about Sequencing from an Instructional Design and Content Development perspective including:  – Effective team communications– Project management– Instructional sequencing

3

Session Agenda

• Demonstration of applications– Data Model– Plug-In Technologies– Application Programming Interface– Sequencing & Navigation

• Lessons Learned

Data Model Content Examples (DMCE)

Released 21.12.2004http://www.adlnet.org/downloads/3.cfm

5

DMCE Overview

• Describes the SCORM 2004 Run-Time Environment Data Model

• Demonstrates usage of several data model elements

6

DMCE Purpose

• To provide information and examples for organizations and individuals to view in preparation for the design, development and implementation of SCORM 2004 content

7

DMCE Audience

• Instructional Designers

• Content Developers

• Project Managers

• Acquisition Personnel

• Other

8

DMCE Objectives

• Provide audience with information about the SCORM 2004 Data Model Elements

• Import and explore into any SCORM 2004-conformant Learning Management System (LMS)

DMCE Demonstration

10

DMCE Results

• Content Developers and Instructional Designers are able to better understand the concept of Data Model Elements

• Most downloaded SCORM 2004 content example from ADLNet.org

• Used as a testing package by LMS vendors

Plug-In Technologies Example (PITE)

Released 11.05.2005http://www.adlnet.org/downloads/201.cfm

12

PITE Overview

• Describes and gives examples of the use of plug-in technologies with SCORM 2004– Macromedia Flash MX 2004– Macromedia Director MX 2004

• Demonstrates the code necessary for the plug-in to communicate with the LMS

13

PITE Purpose

• Provides information and examples for organizations and individuals to view in preparation for the use of plug-ins with SCORM 2004

14

PITE Audience

• Content Developers

• Others

15

PITE Objectives

• Demonstrates multimedia content that works in a SCORM environment using a variety of browser plug-in technologies

PITEDemonstration

17

PITE Results

• Provides an example of how to work with different technologies in a SCORM 2004 Run-Time Environment

• Raised awareness in authoring tool vendors to support SCORM 2004 with their products

Multiple Sequencing Content Examples (MSCE)

Demonstrating the Application Programming Interface

(API)Released 27.09.2005

http://www.adlnet.org/downloads/219.cfm

19

MSCE Overview

• Designed to demonstrate sequencing strategies using the SCORM 2004

20

MSCE Purpose

• Create a better understanding of the API for developers 

21

MSCE Audience

• Content Developers

• Software Developers

• Others

22

MSCE Objectives

• Replace the original “Photoshop” examples with optimized code

• Provide improved, relevant documentation to accompany the content examples

• Introduce useful content about the SCORM 2004 API

MSCE Demonstration

24

MSCE Results

• Widely adopted download to demonstrate different sequencing strategies with a high degree of reusable content

Sequencing Essentials Content Example

(SECE)

26

SECE Overview

• Describes high-level background knowledge of the mechanisms built into SCORM 2004 to implement Instructional Sequencing strategies

• Visually illustrates concepts involved in SCORM 2004 Sequencing and Navigation

27

SECE Purpose

• Provides high level information as background knowledge necessary to successfully implement SCORM 2004 Sequencing & Navigation strategies

28

SECE Audience

• Content Developers

• Instructional Designers

• Project Managers

29

SECE Objectives

• To give an overview of general Sequencing and Navigation knowledge

• Ensure audience has understanding of concepts of Sequencing and Navigation

SECE Demonstration

31

SECE Results

• Pending release

Lessons Learned

33

Lessons Learned

• Instructional strategies relating to Sequencing & Navigation

• Project team communications

• Efficiencies gained over time– Streamlining processes

34

Planning Decisions

• Analyze audience

• Make metadata decisions early

• Design templates for use with content

• Document all decisions

35

Design Document

• Design document is the place to notate all decisions and changes for the content example

• Provides information to the team so all are on the same level of understanding

36

Design Document

• Introduction– Purpose and Scope

• Instructional Strategy– Audience– Context– Objectives– Participation– Assessment

• Design Strategy– Presentation– Sequencing Strategy– Screen Design

Considerations– Technical

Requirements

– Naming Conventions– Data Tracking and

Reporting– Data Model

Elements– Metadata

Requirements– Multimedia– Navigation

– Re-entry and exit behaviors

• Implementation• Project Management

– Roles and Responsibilities

– Project Milestones

37

Metadata

• Writing quality Metadata

• Capturing Metadata

• Rendering of Metadata

38

Sequencing

• Instructional Strategy

• Flow Charts– Aids communication from Instructional

Designer to Content Developer– Results

39

Content Development

• Building a reusable library of code

• Reuse of resources saves development time– Requires more time in architecture

• Developing for efficiency

Questions

41

Resources

• ADLnet.org Web Site– SCORM Documentation– Content Examples– SCORM Articles

http://www.ADLnet.org/

42

Thank you