A SCORM Roadmap:

SCORM’s Technical Evolution

Daniel R. Rehak
Professor and Technical Director
Learning Systems Architecture Lab
Carnegie Mellon University
Pittsburgh, PA 15213 USA
Web: http://www.lsal.cmu.edu/
Email: lsal@cmu.edu

Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
1/18
SCORM 1.3 and Beyond
• What COULD happen in SCORM 1.x
• Lots
• What needs to be done?
• A framework for planning
• SCORM 2.x is a different beast

There is no plan for SCORM 1.3+

There is no plan for SCORM 2.x

Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
2/18
In Scope / Out of Scope
In Scope Out of Scope
• Technical • Tools
Extensions • User / Developer
• Learning / Support
Learning Model • Enterprise
Extensions Integration
• Infrastructure • Content & Content
Extensions Development
• Architectural
Framework
Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
3/18
Technical Extensions to SCORM
• Presentation • Web Services
• Navigation • Collaboration
• Assessments • Service-Based
• Simulation Content Content
• Repositories • Localization and
• Data Models Internationalization
• Learner Profiles • Accessibility
• Security • Content Variants
• Communication • Digital Rights
Models Management

Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
4/18
Learning Extensions to SCORM
• Competency-Based • Intelligent
Learning Tutoring Systems
• Performance • Simulation
Support Systems
• Mobile Devices and • Gaming Systems
Mobile Learning • Enterprise
• Adaptive and Integration
Model-Based
Systems

Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
5/18
Infrastructure Extensions to SCORM
• Semantic Web • IMS Specification
• Versioning and Harmonization
Version • Emerging
Management Specifications
• Migration and • Specifications into
Backward Standards
Compatibility

Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
6/18
Evaluating Extensions
• Complexity – is it a complex extension?
• Effort – how long to add the extension?
• Impact – what is the impact on learner?
• Scope – what is scope for system/content?
• Research – is there a research base?
• Practice – is there accepted practice?
• Standards – are the standards available?
• Related Extensions – how does it fit?

Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
7/18
ADL Architecture

Sequencing
Service SCORM
Content
Testing/ Remote
Packages Content
Assessment
Repositories
Service

n
Local

tio
Repository

lec
Se
Course Content
Administration Management Delivery
Service Service Service La
un Browse
ch (Presentation
r
)

SCO
Learner Tracking Tr a RM
c
Profile Service Dat kin g
a
Service SCORM SCORM
RTE API

API
Adaptor

Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
8/18
SCORM System Model
Enterprise
Systems

Enterprise
Standards

Delivery
System
Interface

Delivery
Standards
Standards

Models
Interface

Delivery
User

Content
Standards

Content
Models

Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
9/18
SCORM 1.2 System Model

Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
10/18
SCORM 1.3 System Model

Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
11/18
SCORM 1.3 with Assessments

Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
12/18
SCORM 1.x+ System Model

Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
13/18
SCORM Services Model
EnterpriseBehaviors

Behaviors Integration
DataModels

Enterprise
Standards

DataModels
Behavior Integration Behavior Integration

ContentDelivery
DataModels

DataModels
UIBehaviors

Delivery
DataModels

DataModels
Behaviors

Behaviors
Standards
Standards
Interface

Delivery
Behavior Integration

DataModels

Content
Standards

DataModels

ContentBehviors

Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
14/18
SCORM Services Architecture

Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
15/18
SCORM Bookshelf

Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
16/18
What Next?
• Collection of potential extensions
• Architecture Framework

• Pieces – not the map

• Not a work plan

• Not prioritized

• What Next?
Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
17/18
Questions?
For more information:

http://www.lsal.cmu.edu/
http://lsal.org/

lsal@cmu.edu

Update: 20031027
© Copyright 2003, Carnegie Mellon University
All Rights Reserved
18/18