Skip to main content

Context and Scope

Domain​

A

A

Actors​

A

We distinguish between authenticated users and guests. Authenticated users can be students, academic staff members and system administrators. In particular, we distinguish between authenticated users with the following global roles that can be assigned to each user:

  • Super Admin: Responsible for maintaining the system from a technical perspective. Users with this role have full access to the system.
  • Staff: Typically, these are lecturers who want to administer courses within the system. At RheinMain University of Applied Sciences, this role is assigned to permanent academic staff, such as professors. They have read access to the system configuration (task pools, terms, languages used for tasks). Moreover, they can edit and synchronize task pools, and they can create new courses.

In addition to these global roles, the system uses a fine-grained permission concept within courses. For each course, we define Course Participant as an additional actor, which represents an authenticated user that was registered as a participant in the course. Furthermore, we define the Course Staff Member actor to represent an authenticated user with one of the following roles for a given course:

  • Admin: Administers the course and has full access to it.
  • Lecturer: Supervises a lab group and is allowed to view and grade submitted solutions.
  • Tutor: Supports students during lab groups and has read-only access to submitted solutions and grades.

Business Context​

A

User authentication in Subato is managed through the identity and access management (IAM) system Keycloak, which can be integrated with an external directory service. To support automated assessment of submitted solutions, Subato is connected to Eva2. In addition, tasks can be imported directly from Git repositories, enabling integration with version control systems (VCS).

Technical Context​

The following diagram shows the deployment of Subato at RheinMain University of Applied Sciences:

A