Display a Feedback-IFrame after a User has met the given condition

[DimitriB01]

User Story

As a teacher i want that the student has to give feedback after completing a Sub-Topic.
After the student completed all Learning Elements a Modal should open. The Modal should either display a standard-feedback modal (general star rating for the sub-topic) or a moodle-feedback activity modal.

The Database should get a new table with the information (id, Moodle-Feedback-actvity, topicId, Condition (number, prozent))
If the boolean is true the iframe at the end of the sub-topic (when condition is met) should display the moodle feedback that is persisted in the backend.

This Issue has to be done: #263

Possible Solution
If a user triggers the onClose() in the Frontend, this should send a fetch to the backend (should i show the Feedback-Modal). The Backend should then ask Moodle which elements are done in this specific sub-topic. Then the Backend checks if every classification in this sub-topic is marked as done, if yes then it sends "true" back to the Frontend.

For this approach the Frontend first sends a fetch to the Backend. The Backend then fetches the needed information from Moodle via RestAPI calls and then checks if all classifications inside the specified sub-topic are done.

Acceptance criteria

• IFrame is opened after the User closes the last Learning Element with a distinct classification
• IFrame either displays a standard Feedback Form defined in the Frontend
• IFrame either displays a Moodle activity Feedback defined in Moodle.
• Database Table holds all needed information for this task

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• User Story effort is estimated
• User Story has acceptance criteria
• User Story has added value for the product or development
• User Story origin is known (stakeholder)
• User Story is assigned to Release
• Backend and Frontend are cloned from GitHub and Running locally
• Basic knowledge of the backend and frontend architecture
• Activity diagram (or sequence diagram) screenshot in issue

Definition of Done

• All acceptance criteria are met
• The implementation of the User Story has been successfully accepted by the Product Owner
• The implementation is in GitHub
• A code review has been performed (or created in pairing program)
• Code conventions are followed
• Unit test coverage must be greater than 90%
• All tests must have passed
• Technical documentation created (Feature documented in GitHub Wiki)
• UML class diagrams and component diagrams created and up-to-date
• Documentation in realization created (source code)
• Changelog created (Clear description in merge request)
• There are no known bugs