1 / 16

Learning Design, generic service descriptions and universal acid Martin Weller

Learning Design, generic service descriptions and universal acid Martin Weller. Outline. Context Service oriented architecture SLeD project Integration issues Discussion. Context. Reuse of content Reuse of pedagogy Reuse of tools Open source VLEs Service Oriented Architecture

oprah-spence
Télécharger la présentation

Learning Design, generic service descriptions and universal acid Martin Weller

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. Learning Design, generic service descriptions and universal acid Martin Weller

  2. Outline • Context • Service oriented architecture • SLeD project • Integration issues • Discussion UNFOLD September 2005

  3. Context • Reuse of content • Reuse of pedagogy • Reuse of tools • Open source VLEs • Service Oriented Architecture • Web services UNFOLD September 2005

  4. Reuse of LDs If… Provide savings More convenient Quality Therefore… Need range of tools But… Need to remain neutral to specific tools So Service oriented approach is ideal UNFOLD September 2005

  5. SOA needs • Generic service descriptions • Methodology for describing services • Tools that use these UNFOLD September 2005

  6. Universal acid? Dennet’s analogy for evolutionary theory Generic services will ‘eat’ through any architecture Simple algorithms produce complex behaviour UNFOLD September 2005

  7. Or generic services are… • Nice in theory, but… • Impractical • Inefficient • More work than they are worth • Offer less functionality • Better to build tools from scratch UNFOLD September 2005

  8. SLeD • Upgrading of CopperCore to integrate QTI calls in LD packages • Development of a technical methodology for integrating service calls in LD • Demonstration of this methodology with an interface to an ePortfolio tool UNFOLD September 2005

  9. Proposed architecture UNFOLD September 2005

  10. Approach • Broker – interprets request by player • Player – handles display, coordination and user interfaces • Translators – generic service descriptions not enough, need application specific code • QTI file as resource in LD • Player identifies type ‘QTI’, so sends to QTI engine to generate HTML UNFOLD September 2005

  11. Process UNFOLD September 2005

  12. Outcomes • Successfully modified architecture • Integrated calls to QTI (APIS) • Devised approach • Mock implementation for eportfolio UNFOLD September 2005

  13. Integration Issues • Eportfolio is different from QTI • QTI determines how questions are seen • Eportfolio only says how they are stored – NOT how it gets into an application • Option 1 – minimal integration (LD has been completed) • Option 2 – rich integration (develop a description) UNFOLD September 2005

  14. Other Issues • No OS eportfolio tools have WS interface yet • Complexity of developing description for every service UNFOLD September 2005

  15. Discussion • It worked • But… • Is generic sometimes a goal in itself? • Didn’t explore loss of richness • Is it worth the effort? UNFOLD September 2005

  16. If you want more.. http://sled.open.ac.uk/ http://www.coppercore.org/ http://www.jisc.ac.uk/index.cfm?name=programme_elearning UNFOLD September 2005

More Related