Functionality and SCORM-compliancy evaluation of eLearning tools

Ivan Ganchev, Mairtin O'Droma, Radoslav Andreev

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

A comparative analysis of the functional design and standards' compliancy of eLearning authoring/assembling tools and Learning Content Management Systems (LCMSs) is presented with a view of assessing how their functionality meets the requirements for robust development of eLearning content that complies with the existing eLearning standards and specifications. The standard reference model used as a basis for the comparative analysis is the Sharable Content Object Reference Model (SCORM) of the Advanced Distributed Learning (ADL) Initiative. The results show up the strengths but also the inadequacies of existing products. The exercise is useful also in that it implicitly draws out, in a fairly systematic and detailed way, a range of strengths and attributes one would like to see in the functional design of a minimal comprehensive eLearning authoring/assembling tool and LCMS.

Original languageEnglish
Title of host publicationProceedings - The 7th IEEE International Conference on Advanced Learning Technologies, ICALT 2007
Pages467-469
Number of pages3
DOIs
Publication statusPublished - 2007
Externally publishedYes
Event7th IEEE International Conference on Advanced Learning Technologies, ICALT 2007 - Niigata, Japan
Duration: 18 Jul 200720 Jul 2007

Publication series

NameProceedings - The 7th IEEE International Conference on Advanced Learning Technologies, ICALT 2007

Conference

Conference7th IEEE International Conference on Advanced Learning Technologies, ICALT 2007
Country/TerritoryJapan
CityNiigata
Period18/07/0720/07/07

Keywords

  • eLearning authoring/assembling tools
  • Learning content management systems (LCMS)
  • Reference model
  • SCORM

Fingerprint

Dive into the research topics of 'Functionality and SCORM-compliancy evaluation of eLearning tools'. Together they form a unique fingerprint.

Cite this