Rework of the LTI content selection table

[raffifasaro]

Feature Proposal

Spec Version 0.2.0

Context

Problem

The content selection table when creating a LTI learning activity in moodle only allows the instructor to select exercises.

Motivation

A revised table is needed to accommodate new categories that will be added in the future. This will enable instructors to select different Artemis features, not only exercises.

Requirements Engineering

Existing (Problematic) Solution / System

The current implementation does not allow for the implementation of other Artemis features like lectures to be selected as content for learning activities. It is essential to add more functionality to this table to support further enhancements of LTI.

Proposed System

A solution for this problem would be more layers and views. For example providing multiple categories for content (Lectures, Exercises, Competencies) under which the specific units are listed. This would improve navigation and accommodate new features as categories.

Requirements

Describe the Functional and Non-Functional Requirements of the feature. Stick to the INVEST methodology!

1. FR: <Title>:

2. NFR: <FURPS+ Category>: <Title>:

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.