Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Teacher can select algorithm for every sub-Topic #306

Open
24 tasks
DimitriB01 opened this issue Feb 15, 2024 · 0 comments · May be fixed by #326
Open
24 tasks

Teacher can select algorithm for every sub-Topic #306

DimitriB01 opened this issue Feb 15, 2024 · 0 comments · May be fixed by #326
Assignees

Comments

@DimitriB01
Copy link
Contributor

DimitriB01 commented Feb 15, 2024

User Story

As a teacher i want to set the algorithms for all topics. That setting affects all learning paths of all students.

Acceptance criteria

  • As default the learning path should be in order defined by prof-standard
  • It can be changed to a specific Algorithm (graf, aco...)

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants