...
In order to support these requirements we will (probably) need to enhance or create LMS functionality around tracking and communicating course completion, and both the LMS and the Programs service will need to collaborate in order to fulfill certificates. We will address this work in detail in a follow-on discovery / design effort.
Commerce Integration (tentative)
Integration with Otto (the external commerce service) will work along similar lines to the present integration for creating and fulfilling products based on seats in Course [Runs].
An administration tool in Otto will read from the Program service to find available (active) Programs, and related Course information.New modules in Otto will define a product structure for XSeries encapsulating availability, pricing, upgrade, and refund logic.Otto will use the Program Users API to fulfill registrations in the Program, and continue to use the Enrollment API to fulfill Enrollments as it does presently.
This functionality / integration has been removed from the MVP and will be visited in more detail in a separate document.
...
very likely be revised in a successive design effort.
Mobile Integration
Learners' courseware experience on the Mobile app is not impacted by work being done for the XSeries MVP. Purchasing / registering in XSeries is specifically out of scope within the MVP. We do intend for all new APIs and UX's to be compatible with the Mobile implementations, to support future integrations post-MVP.
...