1. eText Integration Options Updated on January 6, 2012 CMS

2. Integration with Pearson LMS Platforms PSN eCollege Power School Power School PSN+

3. Integration Scenarios by Platform

4. Course-Aware vs. Non Course-Aware Integrations Course-Aware: Allows instructors to share notes and highlights and a customized Table of Contents with students. Non Course-Aware: With the exception of Disaggregated scenarios, users can create notes, highlights and bookmarks for themselves. – Disaggregated: No personalization features. Lacks notemaking, highlighting, bookmarking, and searching capabilities. No left nav ToC, glossary, index or custom baskets

5. Current Integration Scenarios Course Aware – Scenario 1: Simple URL Linking/ Stand Alone – Scenario 2: Advanced Linking – Scenario 3: Integration API – Scenario 7 Trusted Platform/Non-SMS Integration API – Scenario 9: Course Aware eCollege Integration (TPI) – Scenario 11: LTI – Scenario 12: Course Aware Stand Alone (Limit of 2 Simultaneous Users Per User ID) – Scenario 14: iPad Non Course-Aware – Scenario 4: Disaggregated (Contexual) – Scenario 5: Self-Study – Scenario 6: Disaggregated with Self-Study Personalization – Scenario 8: Stand Alone – Scenario 10: Non-Course Aware eCollege Integration (TPI) – Scenario 11: LTI – Scenario 14: iPad – Scenario 15: School iPad (RUMBA Authentication) – Scenario 16: School Portal (RUMBA Authentication)

6. Comprehensive Integration Features Matrix

7. Integration Scenario 1: Simple Linking Using a simple URL linking mechanism, the course creation and membership are managed by the eText platform. User Experience Flow: Used by, but not limited to: WPS, Course Compass, Pegasus

8. Integration Scenario 1: Simple Linking: Instructor 1 st time

12. Integration Scenario 1: Simple Linking: Instructor 2 nd & Subsequent times

13. Integration Scenario 1: Simple Linking: Student 1 st time

18. Integration Scenario 1: Simple Linking: Student 2 nd & Subsequent times

19. Integration Scenario 1: Direct Login Login directly to the eText through a login page. The course creation and membership are managed by eText User Experience Flow: Used as a direct method of accessing eText

20. Integration Scenario 1: Direct Login: Instructor 1 st time

25. Integration Scenario 1: Direct Login: Instructors 2 nd and Subsequent times

26. Integration Scenario 1 Direct Login: Instructors 2 nd and Subsequent times

27. Integration Scenario 1: Direct Login: Student 1 st time

33. Integration Scenario 1: Direct Login: Students 2 nd & Subsequent times

35. Integration Scenario 2: Advanced Linking This approach will enable the eText platform to use the course information from the host LMS to automate course creation & membership using a static Course ID. Now Deprecated

36. Integration Scenario 3: Integration API This model incorporates a web services API to enable a more robust mechanism to communicate course information & course membership from the host LMS platform to the eText platform. Used by: Mastering, EPIC

37. Integration Scenario 3: Instructor 1 st time

41. Integration Scenario 3: Students, every time

42. Integration Scenario 4: Disaggregated (Contextual) This model applies when the desire is to limit users to a specific range of pages within the eText & not allow any personalization (notes, highlights, bookmarks). User Experience Flow: Used by, but not limited to: WPS, Course Compass, Pegasus

43. Integration Scenario 4: Instructors & Students, every time

45. Integration Scenario 5: Self Study This scenario allows instructors & students to make private notes, highlights & bookmarks. User Experience Flow: Used by, but not limited to: XL, WPS, Course Compass

46. Integration Scenario 5: Instructors & Students, every time

47. Integration Scenario 6: Disaggregated with Self Study Features This scenario limits users to a particular page range, but allows instructors & students to make private notes, highlights & bookmarks. User Experience Flow: Used by, but not limited to: XL, WPS, Course Compass

48. Integration Scenario 6: Instructors & Students, every time

49. Integration Scenario 7: Non-SMS Integration API This model incorporates a web services API to enable a more robust mechanism to communicate course information & course membership from the host LMS platform to the eText platform. User Experience Flow: Used by: PSN+, PSN

50. Integration Scenario 7: Instructors & students, every time

51. Future Integration Scenario 7: Access eText through PSN+ on an iPad using Mobile Safari Users sign into PSN+ (or OLE) using mobile Safari on an iPad. User clicks on an eText link and crosses over to the eText app to access the title PSN+ or OLE Login Page PSN+ or OLE Interstitial Page eText title on iPad Currently, PSN+ is not accessible using Mobile Safari but will be in 2012. OLE is expected to be Mobile Safari ready later this year. PSN+ is already integrated with S7 and OLE will likely be so as well.

52. Future Integration Scenario 7: Access eText through PSN on an iPad using Mobile Safari (After PSN switches to RUMBA) Users sign into PSN using mobile Safari on an iPad. User clicks on an eText link and crosses over to the eText app to access the title PSN Login Page PSN Bookshelf Interstitial Page eText title on iPad Currently, PSN is not accessible using RUMBA but plans to be by BTS 2012. PSN is already integrated with S7 but passes a PSN user identity.

53. Integration Scenario 8: Stand Alone eText Users log directly into the eText from a login page and select a book from a bookshelf. User Experience Flow: Used as a direct method of accessing eText.

54. Integration Scenario 8: Instructors & Students, every time

56. Integration Scenario 9: Course aware eCollege Integration via TPI This integration can be utilized when linking directly from the eCollege platform to an eText and a connection between students and instructors is desired. User Experience Flow: Used by: eCollege

57. Integration Scenario 9: Instructors & Students, every time

58. Integration Scenario 10: Non-Course aware eCollege Integration via TPI This integration can be utilized when linking directly from the eCollege platform to an eText and a connection between students and instructors is desired. Used by: eCollege

59. Integration Scenario 10: Instructors & Students, every time

60. myeBook Product Summary Integration Scenario 11: SMS Integration LTI This scenario uses LTI integration and allows the BU to choose if they would like to use course aware aggregated or disaggregated access. XL and CCND are the two platforms that currently support this integration. Disaggregated Course Aware Currently used by: XL, CCND

61. myeBook Product Summary Integration Scenario 11: Course Aware, Aggregated This model incorporates a web services LTI to enable a more robust mechanism to communicate course information & course membership.

62. myeBook Product Summary Integration Scenario 11: Course Aware, Aggregated Instructor 1st Time

63. myeBook Product Summary Integration Scenario 11: Course Aware, Aggregated Instructor 1st Time Link from LMS eText UI

64. myeBook Product Summary Integration Scenario 11: Course Aware, Aggregated Students, every time

65. myeBook Product Summary Integration Scenario 11: Course Aware, Disaggregated The Course Aware, Disaggregated scenario limits users to a specific range of pages within the eText & allows personalization (notes, highlights, bookmarks). User Experience Flow:

66. myeBook Product Summary Integration Scenario 11: Course Aware, Disaggregated Instructors & Students, every time

67. myeBook Product Summary Integration Scenario 11: Bidirectional Linking In addition to linking from an LMS to eText, Scenario 11 also offers the option to link from the eText back to areas within the LMS platform. Currently, the XL platform is the only platform that has implemented this feature. User Experience Flow:

68. Integration Scenario 12: Direct Login (prevents simultaneous login under same User ID) Login directly to the eText through a login page. The course creation and membership are managed by eText User Experience Flow: Used as a direct method of accessing eText

69. myeBook Product Summary Integration Scenario 12: Direct Login: Instructor 1 st time

70. myeBook Product Summary Integration Scenario 12: Direct Login: Instructor 1 st time

71. myeBook Product Summary Integration Scenario 12: Direct Login: Instructor 1 st time

72. myeBook Product Summary Integration Scenario 12: Direct Login: Instructor 1 st time

73. myeBook Product Summary Integration Scenario 12: Direct Login: Instructor 1 st time

74. myeBook Product Summary Integration Scenario 12: Direct Login: Instructors 2 nd and Subsequent times

75. myeBook Product Summary Integration Scenario 12 Direct Login: Instructors 2 nd and Subsequent times

76. myeBook Product Summary Integration Scenario 12: Direct Login: Student 1 st time

77. myeBook Product Summary Integration Scenario 12: Direct Login: Student 1 st time

78. myeBook Product Summary Integration Scenario 12: Direct Login: Student 1 st time

79. myeBook Product Summary Integration Scenario 12: Direct Login: Student 1 st time

80. myeBook Product Summary Integration Scenario 12: Direct Login: Student 1 st time

81. myeBook Product Summary Integration Scenario 12: Direct Login: Student 1 st time

82. myeBook Product Summary Integration Scenario 12: Direct Login: Students 2 nd & Subsequent times

83. myeBook Product Summary Integration Scenario 12: Direct Login: Students 2 nd & Subsequent times

84. myeBook Product Summary Integration Scenario 14: HiEd eText/Int’l - iPad App This integration scenario enables eTexts to be viewable using the HiEd/Int’l eText iPad App (SMS authentication). The free iPad App is downloaded via iTunes App Store.

85. myeBook Product Summary Integration Scenario 14: iPad: Direct Login to Pearson HiEd/Int’l eText App (Students & Instructors) User enters their MyLab/Mastering credentials to gain entry to their bookshelf.

86. myeBook Product Summary Integration Scenario 14: iPad – Accessing eText from MyLab/Mastering via Safari Mobile for the first time The user clicks on an eText link from an Pearson Learning Platform using Mobile Safari and is sent to an interstitial page. The user can choose to download the Pearson eText HiEd/Int’l App or go right to their title. If they choose to to download the App, they are directed to the Apple iTunes store, otherwise they are directed to the app’s Sign In page. If this is the first time the user is crossing over to the app and has not previously signed in, it will prompt them to enter their MyLab/Mastering credentials. Interstitial Page eText App Sign In Page Link from LMS eText title

87. myeBook Product Summary Integration Scenario 14: iPad – Accessing eText from MyLab/Mastering via Mobile Safari - subsequent sign ins to App If the user has previously logged into the eText App crossing over from an LMS via Mobile Safari will auto sign the user into the App and the user directed to the eText app bookshelf Interstitial Page eText App Sign In Page – Auto Login Link from LMS eText title

88. myeBook Product Summary Integration Scenario 15: eText for Schools iPad App (RUMBA) This integration scenario uses RUMBA authentication. It enables a user to view their eTexts using the Pearson eText for Schools app for the iPad.

89. myeBook Product Summary Integration Scenario 15: School iPad app: Direct Login to the Pearson School eText App (Students & Instructors) User enters their RUMBA (PSN+) credentials to gain entry to their eText for iPad bookshelf. (Note: There is a known defect whereby PSN+ is not passing the proper RUMBA identity to eText)

90. myeBook Product Summary Integration Scenario 15: School iPad app – Accessing eText from School Portal via Mobile Safari for the first time Interstitial pageeText Sign IneText TitlePortal Page it will prompt them to enter their RUMBA credentials. The user clicks on an eText link from the School Portal using Mobile Safari and is sent to an interstitial page. The user can choose to download the Pearson eText HiEd/Int’l App or go right to their title. If they choose to to download the App, they are directed to the Apple iTunes store, otherwise they are directed to the app’s Sign In page. If this is the first time the user is crossing over to the app and has not previously signed in. Interstitial Page eText App Sign In Page Link from Portal eText title

91. myeBook Product Summary Integration Scenario 15: iPad – Accessing eText from School Portal via Safari Mobile - Subsequent Sign-Ins to App If the user has previously logged into the eText App crossing over from the Portal via Mobile Safari will auto sign the user into the App and the user directed to the eText app bookshelf Interstitial pageeText Sign IneText TitlePortal Page Interstitial Page eText App Sign In Page – Auto Login Link from Portal eText Title

92. myeBook Product Summary Integration Scenario 16: Access Pearson eText through School Portal Mac/Windows (Students & Instructors) User enters their RUMBA credentials to gain entry to School Portal and their eText. RUMBA Login Page Portal eText School Portal Sign IneText titlePortal Home Page

93. Integration Scenario 16: Stand Alone eText without Portal for Mac / Windows browsers Users log directly into the eText bookshelf from a RUMBA Sign In page and select a title. Uses RUMBA authentication for users on a Mac/Windows PC browsers. User Experience Flow: Used as a direct method of accessing eText while on a Mac/Windows PC.

94. Integration Scenario 16: Stand Alone eText without Portal for Mac / Windows browsers RUMBA Sign in Page eText bookshelf Text title

95. eText Contacts Peter Chapman - CMS eBook Program Director – Peter.Chapman@pearson.com Peter.Chapman@pearson.com Janet Marhefka—Higher Ed/INTL Product Manager – Janet.Marhefka@pearson.com Janet.Marhefka@pearson.com Jane Stanhope—School Product Manager – Jane.Stanhope@pearson.com Jane.Stanhope@pearson.com