-
Notifications
You must be signed in to change notification settings - Fork 0
Definitions
SIMVA infrastructure is an open architecture software which is composed of several interconnected systems. Among these systems are the unified SSO login system (KeyCloak), the processing queue system (Kafka), and the cloud storage system (Minio). Its architecture is scalable and interoperable with other third-party tools, which enables the delegation of the most critical functionalities to reliable and scalable platforms.
SIMVA front-end is used to integrate the games into the system, create surveys, manage sessions, manage users participation in the sessions and to track/analyze sessions’ data in real-time. This data evolves from users' responses to surveys to full insights and metrics during the whole session which also includes game-play data.
In SIMVA, the user can be a teacher,a student, a researcher or a developer. The roles and permissions in the front-end are categorized into a supervisor, a coordinator and a participant. Which will be explained later in this document.
A container in SIMVA front-end web application to encapsulate the data of different sessions which comes from different resources. A SIMLET is created to achieve a particular objective, for example to compare the effectiveness of a particular SG, compare between the abilities of three groups of students or compare the programming knowledge acquired across different games. A SIMLET consists of one or more sessions. Each SIMLET has its own supervisors.
A container in SIMVA front-end web application to encapsulate the data of several activities. A session consists of one or more activities (pre-survey, game-play or manual and post-survey) to be undertaken by a group of participants. Each session has its own coordinators.
A SIMVA user who has full access to a particular SIMLET. The supervisor creates/edits/deletes the sessions, assigns the coordinators to them, and assigns the participants to be involved in each session. The supervisor kicks off the sessions of a SIMLET, tracks and exports the results of all sessions.
A SIMVA user who has full access to a particular session. The coordinator configures the session, assigns the coordinators, and assigns the participants to be involved. The coordinator kicks off a particular session, tracks it and exports its results
A user (a student for example) whose role is to undertake the activities such as answering the surveys and playing the games. Each participant can also view her/his own results.
A game client is all metadata of the game such as title, description, category (awareness or education), and subject area (mathematics, programming, bullying,etc) . It's the game’s URL for a web game or the game compressed file for a desktop game.
An integrated game into SIMVA means that the game-client is described in SIMVA and presented as a game-play activity template. Each time a new game is integrated into SIMVA, a game-play activity template with an ID is automatically generated. Each time the game is used in a game-play activity within a session, a new game-play activity instance is created from this template. This means that the game-play activity instance will reference the game-play activity template using its ID. Supervisors can display the integrated games from a menu in SIMVA front-end.
An action or set of actions to be performed by participants. This action could be answering surveys (Limesurvey activity), playing serious games (Gameplay activity) or undertaking traditional learning exercises (manual activity).
A survey-based activity that uses LimeSurvey as service, allowing participants to answer pre and post surveys and enabling the owners to collect data effectively.
The action of playing the serious game where participants game interaction data are collected via the xAPI component (trackers in the code), designed to integrate educational content in an engaging manner.
A traditional learning exercise to be undertaken by participants such as reading a book, reading an article, watching a video or any other passive learning task.
A traditional learning exercise to be undertaken by participants such as reading a book, reading an article, watching a video or any other passive learning task.
An activity template represents the static description of an activity. It defines the metadata of an activity such as its title and description. One template can be used within many sessions by creating instances of the template. The activity template can be a survey activity, a manual activity or a game-play activity. In case of game-play activity, it will also contain game-client data.
An activity instance represents a concrete execution of an activity template. It stores participant’s specific data, such as surveys’ responses, manual activity performance, game-play activity interactions, such as traces and results. When the user adds an activity to a particular session, an instance of that activity template is automatically created.In case of game-play activity, the activity instance is referenced to the integrated game’s ID. However, the game’s collected data will be stored at the session’s game-play activity level.
In case a participant completes an activity but its status is not set automatically to "completed" for a reason, there is a button that enables the supervisor/coordinator to manually change the status to "completed". It's also possible to manually change the status of an activity to "completed" for all participants at once.
Each SIMLET contains a visual dashboard with detailed information about sessions’ activities. The dashboard demonstrates general information about each activity status showing the percentage of participants completion, progress and result. It also demonstrates a detailed list of the participants, this list shows each participant’s name, completion status, progress status and backup result. While the activity is receiving xAPI data, whether it's in progress or completed the dashboard is updated correspondingly to the received traces.
For more details : Data-Dashboard