haski-rak/haski-frontend

Frontend of HASKI

HASKI-Frontend

The bridge between AI backend models and LMS, wrapped in a web application.

The complete technical documentation can be found here.

Setup

• Install a JavaScript Runtime like Node.js.
• If you choose to use yarn as a package manager, install it globally via npm install --global yarn, otherwise use the npm equivalents in the following steps.
• Navigate into the root project directory, where package.json lays.
• Install the project dependencies via yarn install
• Add a .env.development file
• For production add a .env.development file

.env file

The content of the .env file gets injected at build time. The values will not be available at runtime. The .env file is not tracked by git.

# API
# Change the backend url to the correct one
BACKEND=http://localhost:8080

Scripts

• Run for development: yarn start
• Build for production: yarn build-prod
• Serve production build: yarn serve -s dist
• Run tests: yarn test
• For linting: yarn lint

IDE

Optional plugins for your development environment:

Plugin	README	Explanaition
SonarCube	https://www.sonarqube.org/	SonarCloud will automatically scan the code for required standards and notify you in the merge request.
Babel JavaScript	https://babeljs.io/	Compiles JavaScript.
ESLint	https://eslint.org/	ESLint statically analyzes your code to quickly find problems.
JavaScript and TypeScript	https://github.com/microsoft/vscode-typescript-next.git	TypeScript version used to power JavaScript and TypeScript IntelliSense.
Npm Intellisense	https://marketplace.visualstudio.com/items?itemName=christian-kohler.npm-intellisense	Code completion for imports.

haski-frontend's Issues

Moodle HASKI Login

User Story
As a student I want to login into the HASKI System
As a anonymous student I want to login into the HASKI System
As a tutor I want to login into the HASKI System
As a assistant I want to login into the HASKI System
As a moodle admin I want to login into the HASKI System

Acceptance criteria

• User clicks on the activity and his ID is sent to the HASKI System
• Secure communication between the LMS and HASKI is guaranteed
• If the request was successful, the user sees a blank page
• If the request failed, the user sees the corresponding error message

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Learning Element has Value "Timespan" (Available From - To)

User Story
As a student i want to see the available date for a limited Learning Element

Acceptance criteria

• The available time is displayed by the Learning Element
• If the current Time is not in the timespan, the Learning Element can not be opened anymore. (Grayed-out)
• Timespan-Functionality is copied from the origin-moodle course

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Create Questionnaire component

User Story

As a student/anonymous student I want to do a questionnaire so that my learning type can be determined.

Acceptance criteria

• Feedback activity in Moodle (dummy data) is created
• Backend persists result from feedback activity associated to the user
• Publish Moodle course and consume questionnaire in HASKI

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
• 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

As a Admin I want to log in to the HASKI System, so that I can manage the system.

User Story
As a Admin I want to log in to the HASKI System, so that I can manage the system.

Acceptance criteria

• User is prompted with login
• Login sets corresponding flags and redirects the user
• Registration form
• Login form
• Corresponding backend
• Secure login using state-of-the-art security
• If the login was successful, the user sees a blank page
• If the request failed, the user sees the corresponding error message

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Learning Element has Difficulty

User Story
As a tutor/admin i want to define the difficulty of a Learning Element.

Acceptance criteria

• Learning Element difficulty has a visual representation
• Defined difficulty can be seen by every User
• Learning Element difficulty can be edited by tutor/admin
• Learning Element difficulty can be removed from an element

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Course shows Learning Path

User Story
As a user i want to see my individual Learning Path.

Acceptance criteria

• In the HASKI-course the users individual Learning Path is shown
• The order of Sub-Themes in the Learning Path, can change
• Users can see changes in the Learning Path

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Learning Element has a Grade

User Story
As a student i want to view the Grading status of a Learning Element, that i have submitted to be reviewed.

Acceptance criteria

• The student can view the grade
• The grade can be changed by tutor/admin role
• Grading is only available, after the student sent a Learning Element for submission
• Only the Student and grading-user can see the grade
• The student and grading-user become a message, that only they see this grade

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Learning Element change evaluation Type (manual/automatic)

User Story
As a tutor/admin i want to to be able to set the evaluation type of the Learning Element.

Acceptance criteria

• Evaluation type can be manual or automatic
• If manual is selected, the tutors and professor gets a notification asking for a review
• Tutors and prefessor have a way to access the students submission
• If automatic is selected, the element answer is sent to the backend. There it will get an evaluation through a AI.

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Course has a "last edited" (Date/Time) Field

User Story
As a student i want to see the "last edited"-information for a HASKI-course.

Acceptance criteria

• "last edited"-field added to the HASKI-course
• The field updates after saving a change in the HASKI-course
• The field does not update its value if the change was not saved

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Topic can have a Description

User Story
As a tutor and admin i want to add a description to a Sub-Theme.

Acceptance criteria

• Sub-Themes got an additional field "Description"
• It is possible to edit and save the description
• Description is displayed correctly

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Create Glossary page

User Story

As student i want to see the Glossary page.

Acceptance criteria

• Glossary page can be accessed
• Glossary page represents all needed information
• Glossary page is accessible from HASKI-course root page

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

Common 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

Technical Definition of Done

• #85
• Informationsstücke auflisten (Begriff : string, Erklärung : string)
• Wireframe erstellen
• Skelett-Komponente in Projekt anlegen
• Schnittstellen bauen (fetch, store)
• API-Schnitstelle in Backend einbauen bzw. mit Marc abklären (Daten existieren in JSON im Frontend)
• Errormanagement (Mindset: mit leeren Informationen umgehen (undefined) -> Unser System crasht nicht)
• Loading Statemanagement (Skeleton MUI für alles, was gefetcht wird)
• Reusable Components and Functions
• Style Guide konsultieren -> in HASKI Mindset verfallen (aktuell nicht umsetzbar)
• UX-Review (alle Planes beachten, für Reviewer wichtig)
• Material UI verwenden (Größe, Alignment, Layout)
• Accessibility (aktuell nicht umsetzbar)
• #86
• Testing

Course can have a Pseudonym-Name/Alias-Name

User Story
As an tutor and admin i want to be able to change the HASKI-course name.

Acceptance criteria

• Moodle-course name and HASKI-course name can be different
• HASKI-course name can be changed
• Changed name can be saved

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Learning Element can have a Done Date

User Story
As a student i want to see the done-timestamp on Learning Elements.

Acceptance criteria

• Every Learning Element has a "done" field.
• After the user finishes a Learning Element, the done-timestamp changes its value
• While the student did not finish any Learning Element in a course, the information is empty/not available
• Done field changes only on the individual student

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Learning Element can get Student-Feedback

User Story
As a student i want to be able to give feedback to each Learning Element. (In form of text)

Acceptance criteria

• Every Learning Element has a possibility to get student-feedback
• Given feedback is only visible to the specific student, any tutor and any administrator
• It should not be possible to edit given feedback

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Learning Element view recently visited

User Story
As a student i want to identify the last Learning Element i have viewed/visited. (Can be the same as recently done.)

Acceptance criteria

• It is possible to identify the last Learning Element the user has viewed/visited
• After the user clicks on another Learning Element, the "recently viewed"-information changes
• While the student did not open any Learning Element in a HASKI-course, the information is empty/not available
• The information is individual to every student

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Learning Element can have a Pseudonym-Name / Alias-Name

User Story
As a tutor and admin i want to to be able to set the Learning Element name seperately from the origin Moodle-course element.

Acceptance criteria

• It´s possible to change the HASKI-course Learning Element name
• It´s possible to save the HASKI-course Learning Element name
• The HASKI-course Learning Element name is displayed correctly

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Topic can have a Pseudonym-Name/Alias-Name

User Story
As a tutor and admin i want to to be able to set the HASKI-course name seperately from the origin Moodle-course name.

Acceptance criteria

• It´s possible to change the HASKI-course name
• It´s possible to save the HASKI-course name
• The HASKI-course name is displayed correctly

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Learning Element has Value "Time Spent"

User Story
As a user i want to see the time i have spent working on a Learning Element.

Acceptance criteria

• Every Learning Element has a value "Time Spent"
• It is 0 before clicking on the element
• Timer starts after the user clicks on it
• Timer ends after the user closes the element page
• Timer restarts, if the user opens it again

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Course has suggested Sub-Themes and Learning Elements

User Story
As a student, when i look at a HASKI-course, i want to see Suggested Sub-Themes and Learning Elements. (Suggestions are AI generated)

Acceptance criteria

• List of suggested Sub-Themes and Learning Elements is retrieved from the backend
• Display suggested Sub-Themes and Learning Elements in the HASKI-course

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Create project/team information course-page

User Story

As a student i want to read the project/team information page.

Acceptance criteria

• Project/Team information page can be accessed
• Project/Team information page represents all needed information
• Project/Team information page is accessible from the HASKI-course root page

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

Learning Element has a Last-Viewed Date

User Story
As a student i want to see the last-viewed timestamp on Learning Elements.

Acceptance criteria

• Every Learning Element has a "last-viewed" field.
• After the user clicks on a Learning Element, the last-viewed timestamp changes
• While the student did not open any Learning Element in a course, the information is empty/not available
• Last-viewed field changes only on the individual student

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

[Technical] Search and Evaluate Library/Code to use HASKI as a Platform

Is probably very similar to #12

[Technical] Understand funktionality of JWT (JSON Web Token) and generate one (Proof of concept)

The communication between Moodle and HASKI needs a JWT-Token to work together. In this Issue we want to understand the functionality of this Token and generate one ourselfs.

Empty Course can be created

User Story
As a Admin i want to be able to create an empty Course. A Moodle course should be the Template for the HASKI-Course.

Acceptance criteria

• After clicking on the HASKI Link / Activity a new Page opens and represents the empty Course.

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Create DSGVO course-page

User Story

As a student i want to be able to see the DSGVO page.

Acceptance criteria

• DSGVO page can be accessed
• DSGVO page represents all needed information
• DSGVO page is accessible from the HASKI-course root page

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

Learning Element can have a Description

User Story
As a tutor and admin i want to add a description to a Learning Element.

Acceptance criteria

• Learning Elements got a field "Description"
• If the Moodle-course element has a description, the value is copied to the HASKI-course Learning Element
• It is possible to edit and save the description
• Description is displayed correctly

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

As a student, I want to do the questionnaire so that the system can determine my learning style

User Story:

As a student, I would like to click on a HASKI activity in Moodle so that I can get individual content

Acceptance criteria

• Questionnaire is embedded in web page
• Completion of questionnaire results in persisted results
• Option to skip questionnaire

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
• Activity diagram is created

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 pass
• All tests must have passed
• Technical documentation created (GitHub)
• UML class diagrams and component diagrams created and up-to-date
• Source code has been commented
• There are no known bugs

Topic has suggested Sub-Themes and Learning Elements

User Story
As a student, when i look at a Sub-Theme, i want to see suggested Sub-Themes and Learning Elements. (Suggestions are AI generated)

Acceptance criteria

• List of suggested Sub-Themes and Learning Elements is retrieved from the backend
• Display suggested Sub-Themes and Learning Elements in the HASKI-course

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Show label-activity of moodle course in HASKI frontend

User Story

As a student I want to see a label-activity in the HASKI frontend.

Acceptance criteria

• Label-activity of moodle course is displayed in HASKI
• New frontend component "label" is created
• New frontend page "course" is created
• Label changes in moodle are reflected in HASKI frontend

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

Learning Element has associated Elements

User Story
As a student, when i look at a Learning Element, i want to see other, associated Learning Elements. (Associate-System could use tags/labels)

Acceptance criteria

• Associated Learning Elements have the same tag/label as the origin Learning Element
• Tags/Labels are used to identify, which Learning Elements are worth associating
• If no tags fit the association, no elements are associated

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Change User specific course color-palette

User Story
As a student i want to be able to choose a course color-palette.

Acceptance criteria

• At least 2 course color-palettes are created
• At least 2 course color-palettes can be selected
• Selected color-palette is saved
• Saved color-palette is applied to the individual user, upon loading the HASKI-course

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Learning Element can be rated by Users

User Story
As a student i want to be able to rate each Learning Element. (In form of stars)

Acceptance criteria

• Every Learning Element has a possibility to get a student-rating
• Given rating is only visible to the specific student, any tutor and any administrator
• It should be possible to edit given rating

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

[Technical] Walking skeleton Frontend

Acceptance criteria

• Walking skeleton of Frontend architecture is realized in GitHub
• Include State management library
• Include Test Library

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
• 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

Learning Element can have a Value/Weight

User Story
As a student i want to see the value/weight of a Learning Element.

Acceptance criteria

• Learning Element value/weight has a visual representation
• Value/weight can be seen by every student
• Value/weight information is retrieved from the backend

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Course can show Author of the original Course

User Story
As a student i want to see the HASKI-course author.

Acceptance criteria

• The Moodle-course author is shown in the HASKI-course

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

[Technical] HASKI Logo in title

Adding the HASKI Logo into the title to replace the react logo for better brand identity.

Learning Element can have Tags/Labels

User Story
As a tutor/admin i want to add and remove tags/labels to a Learning Element

Acceptance criteria

• It is possible to add tags/labels to a Learning Element
• While adding a tag to the Learning Element the user is presented with already existing tags in the same HASKI-course (for example with a dropdown)
• It is possible to remove tags/labels from a Learning Element
• Added tags are displayed

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Learning Element view recently done

User Story
As a student i want to identify the last Learning Element i have finished/done.

Acceptance criteria

• It is possible to identify the last Learning Element the user has done (Moodle Done-Mark?)
• After the user finishes another element, the recently done information changes
• While the student did not finish any Learning Element in a HASKI-course, the information is empty/not available
• The information is individual to every student

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Learning Element can toggle visibility

User Story
As a tutor/admin i want to to be able to set the visibility of a Learning Element.

Acceptance criteria

• Visibility of Learning Elements can be changed (Invisible/Visible)
• If an element is invisible students can not click or see it
• Students should not be able to manipulate the html-dom to make invisible Learning Elements visible again. (Look at the Hide-Functionality in a Moodle-Course, elements can be hidden from students)

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Topic can have Tags/Labels

User Story
As a tutor/admin i want to add and remove tags/labels to a Sub-Theme

Acceptance criteria

• It is possible to add tags/labels to a Sub-Theme
• While adding a tag to the Sub-Theme the user is presented with already existing tags in the same HASKI-course (for example with a dropdown)
• It is possible to remove tags/labels from a Sub-Theme
• Added tags are displayed

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Course can have a Description

User Story
As an tutor and admin i want to be able to add a description to the HASKI-course.

Acceptance criteria

• Course has an additional field "description"
• Users can see the decription of the course
• Description can be saved
• Description can be deleted

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Learning Element has a submission status

User Story
As a student i want to view the submission status of a Learning Element.

Acceptance criteria

• The student can view the submission status
• The submission status can be changed by Tutor/Admin Users
• Submission status contains: open, ready for submission, submitted, graded
• Every Learning Element that can be submitted, has a submission status

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

User Time Spent field

User Story
As a student i want to see my individual "time spent" - information for a HASKI-Course.

Acceptance criteria

• After clicking into a HASKI-Course for the first time the "time spent" timer starts.
• Time spent - timer stops after leaving the HASKI-Course in any way (If the Browser tab is not in focus, possible?)
• User has the possibility to view this information

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

[Technical] Dependency injection

User Story

Acceptance criteria

• DI for state management

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

[Technical] Search and Validate Libraries for using LTI

Course enables access to the Questionaire

User Story
As a student i want to be able to do the Questionaire in the HASKI-course.

Acceptance criteria

• The Questionaire is shown in the course
• The Questionaire can be opened
• The Questionaire is shown correctly
• The student can work on the Questionaire
• The results of the Quesitonaire are accessable to the student

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Course has a "created" (Date/Time) Field

User Story
As a student i want to see the created-date of a HASKI-course.

Acceptance criteria

• A "Created"-date field is shown on the HASKI-course
• The field value is only set once

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Course can have Tags/Labels

User Story
As a Tutor and Admin i want to be able to add and remove Tags from the HASKI-course.

Acceptance criteria

• Tags can be added to the course
• Tags can be removed to the course
• While adding a Tag to the course the user is presented with already existing Tags in the same course (for example with a dropdown)

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

Learning Element has possibility to display solution

User Story
As a student i want to be able to get the solution to a Learning Element.

Acceptance criteria

• If a Learning Element has a solution, the student can view it.
• If a Learning Element does not have a solution, the student does not get the option to view a solution (grayed-out button)

Definition of Ready

• User Story is small enough for Sprint
• User Story is clearly understandable for everyone involved
• 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
• User Story effort is estimated

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

[Technical] Theme page / demo page

User Story

Acceptance criteria

• Dediacted demo page with our own theme as reference

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