The task is to evaluate the task from the semester plan:
What it means?
The group should be able to create queues for their disciplines. For example:
There is the third laboratory pair in semester.
There are 27 people that want to defense their laboratory work
They need to have an independent instrument that allow to create queues for pair
What the functionality should this queues have?
Create queue (queue can have a name, max capability), command
Groupmember can join the queue in the end, command. If queue has no space (maximum capability is reached), show reject message
Groupmember can leave the queue, command
Groupmember can be thrown back on 5 positions (only for captains), command
Groupmember can be deleted from queue (only for captains), command
Edit queue (change name and max capability)
Delete queue
Show the queue (name and the list of tags (should not tag people)), command
Queue also need to have some message, that will be edited constatly whenever new person joins or leaves queue. This feature is really useful when captain can pin this message and spectate the process of laboratory defensing (as example)
The task is to say what endpoints and tables in database should back-end have. It must be fully described with essential requests, responses, fields, queries, data types, etc.
The task is to evaluate the task from the semester plan:
What it means?
The group should be able to create queues for their disciplines. For example:
What the functionality should this queues have?
The task is to say what endpoints and tables in database should back-end have. It must be fully described with essential requests, responses, fields, queries, data types, etc.