1. Delivering QTI Self-tests to Personal Learning Environments using Wookie Widgets Vladimir Tomberg, Raido Kuli, Mart Laanpere, PeeterNormak Tallinn University Estonia 09.12.2010, ICWL 2010, Shanghai 1

2. Personal Learning Environments The shift of PLE pedagogical paradigm: from teacher-driven to self-directed learning process Web 2.0 technology is causing a decrease in the use of existing digital content, which is still valuable and re-usable 2

3. PLE and Tests Questions and tests are digital learning objects, which currently can be hardly delivered to PLE But there is a wealth of valuable, reusable questions and tests stored in learning object repositories 3

4. IMS QTI XML: de facto standard for assessment-related content Since 2005 QTI ver. 2 is stable and widely used (but still is beta!) Possibility to import/export tests Testing system as a set of tools or services: authoring tool, repository, test construction tool, assessment delivery system 4

5. Widgets technology Lightweight Web applications designed for a single specific function Great choice of different widget platforms and related specifications not compatible between themselves First standard: W3C Widget Packaging and Configurationspecification (2006) 5

6. Our scenario for Self-Testing in PLE Teacher embeds selected self-tests into her/his blog in form of widget Embedded search tool provided to learners for finding suitable self-tests from repository Students generate self-test by themselves 6

7. Functional Requirements Searching a suitable test from a repository Visualization of testing questions and submitting the test Receiving results of test’s completion with feedback 7

8. Overall Architecture of Software Solution To implement the embedding widgets into blogs we used Java servlet server Apache Tomcat, which serves several web services and software: Wookie application, QAPS API and question rendering engine R2Q2. 8

9. QAPS QAPS (QTI Assessment Proxy Service) is API, which deals with self-test related data exchange between a Learning Object Repository and the Widget engine. 9

10. Using QAPS API for Self Testing Solution 10

11. Workflow for QTI player prototype components 11

12. Widget at Work: Searching for Test 12

13. Widget at Work: Implementation of Test 13

14. Widget at Work: Finishing Test 14

15. Widget at Work: Feedback 15

16. Conclusion The implementation of QAPS demonstrated the feasibility of re-using the existing QTI content stored in Learning Object Repositories Project source code address:http://trac.htk.tlu.ee/modules/wiki/qti_player 16

17. To Do Adding authentication Service, which is going to aggregate the learners’ profiles, and store their tests’ results 17

18. Thank you. 18