XML SCORM STUDIO PROJECT INITIATION

1
XML SCORM STUDIO PROJECT INITIATION

• Project Team
• Project Goals
• Project Time Line
• Questions Answers

2
Project Team

• EDUWORKS
• Robby Robson
• Tyde Richards
• Kristy Saunders
• MISSISSIPPI STATE
• Debbie Brown
• Kelli McCarter
• Others
• NUWC
• Virginia Mesenbrink

• LSI
• Earl Porter
• Charlie Brewer
• Joint ADL Co-Lab
• Bill Pike
• Steve Slosser
• Dean Marvin
• Chris Bray
• Damon Regan
• Mike Sazma

3
Core Development Team

• EDUWORKS
• Robby Robson
• Tyde Richards
• Kristy Saunders
• MISSISSIPPI STATE
• Debbie Brown
• Kelli McCarter
• Others
• NUWC
• Virginia Mesenbrink

• LSI
• Earl Porter
• Charlie Brewer
• Joint ADL Co-Lab
• Bill Pike
• Steve Slosser
• Dean Marvin
• Chris Bray
• (Damon Regan)
• Mike Sazma

4
Who Do You Call?

• EDUWORKS
• Robby Robson
• Tyde Richards
• Kristy Saunders
• MISSISSIPPI STATE
• Debbie Brown
• Kelli McCarter
• Others
• NUWC
• Virginia Mesenbrink

• LSI
• Earl Porter
• Charlie Brewer
• Joint ADL Co-Lab
• Bill Pike
• Steve Slosser
• Dean Marvin
• Chris Bray
• (Damon Regan)

5
ROLES AND RESPONSIBILITIES

• OVERALL DIRECTION
• Robby Robson / Tyde Richards / Bill Pike
• PROJECT MANAGEMENT
• Bill Pike / Virginia Mesenbrink / Robby Robson
• CONTENT / ISD
• Virginia Mesenbrink / Debbie Brown / Mike Sazma
• TECHNOLOGY
• Core Development Team

6
Foundations

• SCORE (VB Version)
• InSite Studio
• OPEL

7
SCORE Content Conversion
8
SCORE

• Disaggregation
• Editing
• SCO Selection
• Add behaviors
• Recombination

9
InSite Studio

• Designer- Friendly UI
• SCORM 2004 Sequencing
• Conversion of Office Docs

10
OPEL

• Persistence Layer
• Breadboard for integrating prototypes

11
SCORE Process Diagram
12
Content Evolution
2000
2005
1995
Standardized Structured Content LET
Elements Separated from Generic Structure
PROPOSED
13
Research Focus Area
ADL Problem Space
14
Research Focus Area
ADL Problem Space
15
Research Focus Area
ADL Problem Space
16
Research Focus Area
ADL Problem Space
17
Research Focus Area
ADL Problem Space
18
XML-Based SCORM Studio

• Create modularized and user friendly tools for
  entire SCORM content workflow
• Enable designers to convert, disaggregate,
  repurpose and recombine content and to create
  complex learning designs without being experts on
  SCORM
• Port SCORE to .NET
• Integrate SCORE with InSite Studio via .NET

19
XML-Based SCORM Studio

• Demonstrate and provide guidelines for use of a
  common non-proprietary XML format that exposes
  the inner structure and workings of SCOs
• Demonstrate that complex adaptive instructional
  designs can be described using a graphical
  interface and instantiated using SCORM SN.

20
XML-Based SCORM Studio

• Investigate methods to effectively integrate
  simulation-based learning content into SCORM 2004
  SN and the SCORM runtime communication API and
  data model.
• Exercise the OPEL APIs and provide services that
  can be shared with DoD, Federal agencies, and
  other organizations committed to advancing the
  state of distributed learning.

21
PROPOSED PROJECT TIMELINE
USE CASES
TESTING
OCT
NOV
DEC
JAN
FEB
MAR
APR
MAY
JUN
JUL
SEP
AUG
22
PROPOSED PROJECT TIMELINE
OPEL
TEST CONTENT DESIGNS
USE CASES
XML FORMAT
OPEL FREEZE
DEMO
INSITE MODS
XML SCORM STUDIO
SOA SPECS
DOCS CODE
.NET SCORE
Kick off
23
Project Management Requirements

• Detailed timeline dependencies
• List of documents
• Informal Formal
• Content format requirements (e.g. IEEE Software
  Engineering Standards)
• Identification of owner (also responsible for
  change control)
• Monthly reporting requirements
• Virginia will collate
• Any ADL requirements?
• Communication enablers
• ADL Community site
• Teleconferences
• Screen / Application sharing

24
Assumptions Constraints

• OPEL
• Content with source files from NUWC
• Assistance from ADL in Use Cases and
  Instructional Design Requirements (including
  target audience description)
• Test environment compatible with all platform
  requirements
• Ability to interact with DoD end users?

25
QUESTIONS?

• THANK YOU!