1 / 20

The Educom NLII Instructional Management Systems Project

The Educom NLII Instructional Management Systems Project. Thomas D. Wason, Ph.D. University of North Carolina at Chapel Hill tom_wason@unc.edu. Project Objectives. Goal: develop an open architecture for on-line learning

tyra
Download Presentation

The Educom NLII Instructional Management Systems Project

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. The Educom NLII Instructional Management Systems Project Thomas D. Wason, Ph.D.University of North Carolinaat Chapel Hill tom_wason@unc.edu

  2. Project Objectives • Goal: develop an open architecture for on-line learning • Deliverables: create freely distributable specifications and software that enables the development, use, and management of Internet-based learning environments • Model: HTTP + Mosaic de facto standard, led to explosion of content, new markets

  3. IMS Members • Education members • CSU, Collegis Research Institute, UNC, U. of Michigan, Miami Dade, CIC (“Big Ten”), Buena Vista University, George Mason University, JISC • Commercial members • Microsoft, Apple, IBM, Sun, International Thomson Publishing, Collegis, Farance Inc., KPMG, NIST, Department of Defense, Empower, @Learning, Unisys, Oracle, Asymetrix • Cooperative creates open specifications and prototype, members create products Parts of the prototype are being developed by Blackboard LLC

  4. Funding and requirements IMS Members Specs Specs, Code, and Market Development IMS Members, Testbed, Developers Network, Public IMS Staff (14 full-time) Permanent Stds. body Work Process

  5. Initial dissemination/support • Developers’ Network • Technical support for IMS developers • Marketing opportunities • Testbed • 10 sites: BVU, IDC Herzliya, MDCC, NPS, Penn State, UCF, Hawaii, Michigan, UT Knoxville, Twente, Virginia

  6. Convergence • Airline Industry CBT Consortium (AICC) • Dublin Core • LOMG • ADL • IEEE • ARIADNE • GEM

  7. Interchanges Peer-to-Peer Interchange L C P Learners Teachers Coordinators Providers T Interchange

  8. Teacher Authoring Tools Learning Resources Off Campus Student IMS Mgmt System CD Collaboration Tools Back office On campus Student IMS Campus Environment

  9. Technical Overview • Scope of Specification • Profiles • Metadata • Content • Management (Content, Course, Collaboration) • External Services

  10. IMS Profile Specification • Educational records “Wallet” • Mobile • Contains • Personal information • Performance information • Portfolio • Preferences

  11. Metadata Specification

  12. Metadata benefits • Find and organize materials more easily • Helps in automating some authoring tasks • Enables customized learning experiences

  13. Metadata Extensibility IMS CORE METADATA Title: Author: Learning Level: Keywords: and more…. AICC EXTENSIONS Airframe type: …. BIOLOGY Extensions Phylum: ….

  14. IMS Metadata Specification • IMS Metadata Search/Query Demonstration • http://metadata.imsproject.org/mdtool/ • IMS/NIST Metadata Repository • dictionary of terms for describing content • supports group specialization • can be queried/browsed with modified authoring tools

  15. IMS Content Specification • Supports technical interoperability of • assessment • sequencing • reporting data • bookmarking • notification • metadata

  16. IMS Interoperability ActiveX/DCOM-based Content and Tools JAVA/Corba-based Content and Tools HTML/CGI-based Content and Tools ex. HTML and PERL

  17. Management Specification • Manages • Content • Courses • Collaboration • Interfaces • Database, Security, Access control, HTTP/CGI, tracking, session management, DCOM/Corba message bridging ….

  18. Publisher School Content Content Distribution and Access Option 1: Distribute Content Option 2: Provide Access to Content Publisher School Content Reference Content

  19. External Services Specification • Specifies technical interface to campus IT infrastructure • student records • billing/commerce • library

  20. www.imsproject.org Project Information • IMS Project • Mark Resmer (resmer@sonoma.edu) • Technical • Steve Griffin (steve_griffin@unc.edu) • Market Development • Denis Newman (denis_newman@earthlink.net) • Metadata • Tom Wason (tom_wason@unc.edu)

More Related