The Frontend should only tell the backend that a learningPath is ready to be calculated. The information what needs to be calculated should reside in the backend
Possible approach
Database has a table that hosts the information
which student is in which course
what topics does a course have (that need to be calculated)
what algorithms should be used to calculate the given topics
The Frontend then only has to tell for which student all the topics need to be calculated.
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)
Technical
The Frontend should only tell the backend that a learningPath is ready to be calculated. The information what needs to be calculated should reside in the backend
Possible approach
Database has a table that hosts the information
The Frontend then only has to tell for which student all the topics need to be calculated.
Definition of Done