To create and use the content, SOWISO offers the following three options:
1. Standalone usage
2. Single sign-on integration with the Digital Environment
3. SOWISO API with own front-end
It is also possible to implement a combination of the above options. For instance, let
authors create content via option 1 and let End users playback content via option 3.
Option 1: Standalone usage
There is no integration between SOWISO and the Digital Environment of the customer. User management takes place in SOWISO and End users log in directly on the SOWISO platform. The SOWISO platform can be adjusted to fit the corporate identity of the customer.
Pros | Cons |
Absence of risk: when SOWISO updates occur, there will not be a need for any extra work. | Absence of integration. |
The landing page and the look (corporate identity) can be fully customized. | User management and End user results will not be easily exchanged between Digital Environment and SOWISO. |
Low costs of implementation. | The user needs to log in separately on the SOWISO platform. |
All of the platform features SOWISO offers can be used, e.g. forum, digital assessments, theory pages, adaptivity, classroom management and course management. |
|
Option 2: Single sign-on integration with the Digital Environment
The Digital Environment will function as an identity provider. This means that users will need to be registered on the Digital Environment first before they can exist on the SOWISO platform. There will be no need to log in separately on the SOWISO platform, or it happens in the background via the Digital Environment (for instance using SAML2). We will synchronize the Digital Environment and SOWISO user accounts, which makes it possible to synchronize results and reports.
Interaction with the content will happen on the SOWISO. There are two options for users to have access to the content:
a) Via a direct link to SOWISO
The SOWISO platform is used to navigate to the content and to interact with it.
b) Via the Digital Environment, in a pop-up, new tab, or iframe
The Digital Environment is used to navigate to the content. The SOWISO platform can only be used to do exercises.
Pros | Cons |
Absence of risk: when SOWISO updates occur, there will not be a need for any extra work. | When b) is the case, not all of the SOWISO platform features can be used, e.g. forum and adaptivity. |
The look (corporate identity) can be fully customized. | When b) is the case, a user is active inside of an iframe. This lowers the user experience. |
Relatively low cost of implementation. | When b) is the case, the content has to be offered through the Digital Environment. To guarantee that the right exercises are offered to the user an integration between the Digital Environment and SOWISO will be necessary. |
When a) is the case, all SOWISO platform features can be used. When b) is the case, only a few of the SOWISO platform features can be used. |
|
Option 3: SOWISO API with own front-end
SOWISO has developed its own API, which can be used for external access to the application. The customer can create his or her own front-end, which uses SOWISO as a back-end system. SOWISO will then only be used as a back-end system, while the customer can decide the look and interaction. This requires significant development and maintenance on the side of the customer, but will most likely lead to the best user experience.
Pros | Cons |
Both the look (corporate identity) and the interaction can be fully customized. | When SOWISO updates occur, the customer might need to do some extra activities. |
A user works directly in the Digital Environment. This improves the user experience. | Not all of the SOWISO platform features can be used, e.g. forum, adaptivity, digital assessments, class management, and course management. |
User synchronization is not necessary (but still recommended). | Relatively high cost of implementation. |
| The content has to be offered through the Digital Environment. To guarantee that the right exercises are offered to the user an integration between the Digital Environment and SOWISO will be necessary. |
|
|