The document discusses IMS Outcomes and its implementation in Sakai. IMS Outcomes is a specification for exchanging assignment and grade data in a standard way. It defines services for managing line items (assignments) and results (grades). Pearson implemented IMS Outcomes as a profile of IMS LTI. Sakai implemented IMS Outcomes services to allow its gradebook to interface with external learning tools via the Pearson implementation. The demo showed assignment and grade data exchange between Sakai and external tools using the IMS Outcomes standard.

1. IMS LIS Outcomes and Sakai Standardizing Grade Exchange John A. Lewis Chief Software Architect Unicon, Inc. Sakai 2010 Conference 17 June 2010 © Copyright Unicon, Inc., 2010. Some rights reserved. This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/us/ Special thanks to Gary Gilbert for all his help with this presentation and demo!

2. Intro to IMS Outcomes

4. Part of the IMS Learning Information Services (LIS) Specification

5. Version 1.0 (Currently in public draft)

6. Released March 2010

9. How to exchange assignment and grade data in a standard way

12. Result : grade for a student in a context

13. Outcomes Data Model

16. Contains a collection of results

18. Can represent the current state of a person's line item attempt (e.g. In-Process)

19. Outcomes Services

25. That is, the parties (that agree to the LTI contract) may extend that contract to include Outcomes

27. A guarantee that the tool consumer will expose the LineItemManager and ResultManager interfaces as web services

28. Deployment time agreement on security profiles of the web services (typically, WS-Security) and POST (typically, hash message (MAC/OAuth) token security)

29. Deployment time provisioning of outcomes endpoint locations in the tool provider

30. Pearson's Implementation

32. Pearson implemented IMS Outcomes as profile of Full LTI

33. Fits with their larger strategy of pushing of standards based integrations

36. TPI reads messages off the MOM and delivers them to Partners (aka tool consumers - e.g. Sakai) that expose Outcomes services - typically, the partners have the gradebook

41. Sakai Implementation

43. Test harness for Pearson TPI

44. Able to use the Sakai Gradebook for testing

47. Two new Java interfaces and implementations that fulfil the LineItem and Result Manager contracts that back the web service

49. GradebookExternalAssessmentService (to manipulate assessments within Sakai)

50. All the other usual suspects: UserDirectoryService , SiteService , CourseManagementService , SessionManager , ToolManager ...

51. Support for tool launch from the Sakai Gradebook (but Pearson TPI doesn't support it yet)

53. Sakai worksite/gradebook could potentially map to many line item data sources (multiple assessment engines)

54. A line in the Sakai gradebook (GB_GRADEABLE_OBJECT_T) maps to a single line item uniquely identified by a GUID

55. A grade in the Sakai gradebook (GB_GRADE_RECORD_T) maps to a single result uniquely identified by a GUID

56. IMS Outcomes Demo In Sakai

70. Working Pearson to contribute all the Sakai artifacts

71. Questions & Answers John A. Lewis Chief Software Architect Unicon, Inc. [email_address] www.unicon.net