1 / 33

Introduction of SCORM: Sharable Content Object Reference Model

Introduction of SCORM: Sharable Content Object Reference Model. Hao-Chuan Wang Computer Science Department National Chengchi University 2003 May. Outline. Introduction SCORM Overview SCORM Content Aggregation Model Content Model Metadata Content Packaging Run-Time Environment Demo.

nessa
Download Presentation

Introduction of SCORM: Sharable Content Object Reference Model

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Introduction of SCORM:Sharable Content Object Reference Model Hao-Chuan Wang Computer Science Department National Chengchi University 2003 May

  2. Outline • Introduction • SCORM Overview • SCORM Content Aggregation Model • Content Model • Metadata • Content Packaging • Run-Time Environment • Demo

  3. Introduction • Computers in Education: developed over 30 years. • early years: CAI • with the impact of AI and cognitive science: Intelligent Tutoring System (ITS) • Multimedia and internet: web-based learning • A new term today: e-Learning • What’s the next step of learning technology?

  4. Introduction • Most web-based learning systems today: • Proprietary format • Contents are not exchangeable and sharable • Expensive costs for maintenance: ex. Updating and extending • Standard reference model is needed. • Many e-Learning specifications are proposed. • SCORM: unifying these specs.

  5. SCORM Overview • Sharable Content Object Reference Model • Defines a Web-based learning “ Content Aggregation Model “ and “ Run-Time Environment “ for learning objects. • A model that references a set of interrelated technical specifications and guidelines designed to meet DoD’s requirements for Web-based learning content.

  6. Reference Model Criteria • Durable –no modification required as versions of system software change. • Interoperable –operate across a wide variety of hardware, operating systems and Web browsers. • Accessible –can be indexed and found as needed. • Reusable – can be modified and used by many different development tools.

  7. BOOK 1: The SCORM Overview BOOK 3: The SCORM Runtime Environment Meta-data XML Binding and best Practice (from IMS) Metadata Dictionary (from IEEE) Content Packaging (from IMS) Content Structure (derived from AICC) Data Model (from AICC) Launch, Communication API (from AICC) Others: Applications, Conformance…etc. SCORM: A Collection of Specs. BOOK 2: The SCORM Content Aggregation Model From SCORM 1.2 Overview, http://www.adlnet.org

  8. Footnotes of overview • Back to the viewpoint of practice: • SCORM separate contents from learning platform. • Contents are packaged following the spec. of Content Aggregation Model • How contents communicate with Learning Management System (LMS) are specified in the spec. of Runtime Environment

  9. SCORMContent Aggregation Model The Content Aggregation Model spec. consists of three components: • Content Model : basic learning objects • Meta-data : mechanism for describing instances • Content Packaging : the structure and behavior

  10. Content Model • Defines how lower-level sharable, reusable learning resources are aggregated to compose higher-level units of instruction. • Learning resources are aggregated into: • Assets • Sharable Content Objects (SCO) • Content Aggregation

  11. Assets • Learning content in its most basic form is composed of Assets. • Assets could be representation of types of media. Ex. image, text, video clip. • Asset metadata • allow for search and discovery within online repositories,thereby enhancing opportunities for reuse. • The mechanism for binding Assets to Asset meta-data is the Content Package.

  12. Example of Assets From SCORM 1.2 CAM, http://www.adlnet.org

  13. SCO • A collection of one or more Assets that utilizes the SCORM Run-Time Environment to communicate with Learning Management System (LMS). • A SCO represents the lowest level of granularity learning resources that can be tracked by an LMS.

  14. Example of SCO Communication with Runtime Env. From SCORM 1.2 CAM, http://www.adlnet.org

  15. Content Aggregation • The Content Aggregation defines the content structure. • A map (content structure) that can be used to aggregate learning resources into a unit of instruction.

  16. Example of Content Aggregation From SCORM 1.2 CAM, http://www.adlnet.org

  17. Meta-data • The purpose of meta-data is to provide a common nomenclature enabling learning resources to described in a common way. • Learning resources described with meta-data can be systematically searched and retrieved. • Assets, SCO, Content Aggregation all use the same meta-data model.

  18. Categories of Meta-data Elements • Nine main categories and totally about 80 tags. • Rights • Relation • Annotation • Classification • General • Lifecycle • Meta-metadata • Technical • Educational

  19. Symbol Table

  20. Example of Categories: General • The General category groups the general information that describes the resource as a whole.

  21. Example of Categories: Technical • The Technical category groups the technical requirements and characteristics of the resource.

  22. Example of Categories: Educational • The Educational category groups the educational and pedagogic characteristics of the resource.

  23. Examples of Meta-data • around.jpg, 6 of 9 meta-data categories are used.

  24. Content Packaging • A standardized way to exchange digital learning resources between different systems ( LMS ) or tools. • Define the structure ( or organization ) and the intended behavior of a collection of learning resources. • A manifest file : list all of the resources or assets included in the package, the organization of the SCOs, the metadata for the package and the SCOs • All the actual SCO files

  25. Content Packaging (cont.)

  26. Content Packaging XML Binding

  27. Example of Manifest File • Each learning object is packaged with “imsmanifest.xml”

  28. Run-Time Environment • A common way to start learning resources, a common mechanism for learning resources to communicate with an LMS. • The responsibility of the LMS : to determine which learning resource is to be launched. • The responsibility of the SCO：to find the API Adapter.

  29. Run-Time Environment (cont.) From SCORM 1.2 RTE, http://www.adlnet.org

  30. API for Communication • A set of predefined functions: allows the SCO to communicate with the LMS. • All communication between the API Adapter and the SCO is initiated by the SCO. • Threefold API Adapter objects : • Execution State : to handle execution state : LMSInitializeandLMSFinish • State Management : to handle errors :LMSGetLastError,LMSGetErrorString, and LMSGetDiagnostic • Date Transfer : to transfer data to and from an LMS : LMSGetValue, LMSSetValue, andLMSCommit

  31. API Adapter State Transitions From SCORM 1.2 RTE, http://www.adlnet.org

  32. DEMO • ADL’s Sample Run-Time Environment Version 1.2.1 • Run-time Environment Server Component: Implemented using Java Applications and Java Servlets. • Run-time Environment Client Component: Implemented using JSP, Java Applets, HTML, and JavaScript. • Sample Course: Implemented using HTML and JavaScript.

  33. Conclusion • Future of web-based learning: “Object-oriented” concepts. Learning objects. • Easy to retrieve and find learning objects: Learning services around the web! • More adaptive and effective learning experiences for learners.

More Related