Create and support LTI learning activities for multiple exercises

[raffifasaro]

Feature Proposal

Spec Version 0.2.0

Context

Problem

Currently there is no way for LTI instructors to create learning activities for a group of exercises.

Motivation

It is only possible to link a single exercise to a learning activity in LTI. This functionality is expanded towards support of multiple exercise selections. This is an important feature for instructors, who want to represent a learning unit containing multiple exercises (for example, all exercises of a certain course week). Students will then only see one learning activity for this exercise group, making the course page more readable and freeing up course topics within Moodle.

Requirements Engineering

Existing (Problematic) Solution / System

What is the current solution (if there is one)? What is the problem with the current solution?
You may include a UML Model here

Proposed System

Instructors are able to select multiple exercises in the content selection table on Moodle. If multiple exercises are selected, these are part of a new group of selected exercises, which is represented by a single learning activity on the Moodle course page.
Student are able to select this learning activity and open a new LTI page on Moodle which supports this new grouped content by having a UI element to navigate the different content items per learning activity.

Requirements

1. FR: Multiple exercise selection is supported: Instructors are able to select multiple exercises and have them displayed under a single learning activity

2. FR: Usable learning activities for grouped exercises: Students are able to select the learning activity containing multiple exercises and get a new UI, which supports grouped content.

3. FR: Artemis UI featuring grouped content in LTI view: The LTI view of Artemis exercises is adapted to grouped content by displaying a UI element to switch between exercises of the same selection group defined by the learning activity.

4. NFR: User Experience: Consistent Interface: The new UI elements should be displayed in Moodle without any drawbacks or alterations compared to the original Artemis page.

Analysis

Analysis Object Model

What are the involved Analysis Objects?

Dynamic Behavior

Include dynamic models (Activity Diagram, State Chart Diagram, Communication Diagram) here to outline the dynamic nature of the PROBLEM

System Architecture

Subsystem Decomposition

Show the involved subsystems and their interfaces. Make sure to describe the APIs that you add/change in detail. Model the DTOs you intend to (re)use or change!

Persistent Data Management

Describe the Database changes you intend to make.
Outline new configuration options you plan to introduce
Describe all other data persistence mechanisms you may use.

Access Control / Security Aspects

Describe the access control considerations for your feature

Other Design Decisions

Potential topics to discuss here include: WebSockets, testing strategies.

UI/UX Design

Screenshots of the final UI mockups (mandatory): Please include screenshots to provide a clear and persistent visual reference of the design.
Link to the design mockup (optional): Additionally, you may include a link to the live design mockup (e.g., Figma, Sketch) for a more interactive view. Note that this link is supplementary and should not replace the required screenshots.