Our program consists of:

• Teacher

• Chief-Teacher

• Student

• Subject

• Study-account materials

Authorization

• Login form with email and password

• Users are divided into: teacher, chief-teacher, student.

Home page

• List of Subjects sorted by name

• List of Teachers sorted by last name

• Number of classes and number of Students

• ** Student Achievements

• ** Teacher Achievements

Teacher

• List of Subjects taught by the Teacher

• Can add or remove Students in the Subject

• Can grade Students by Subject in the gradebook

• Browse (sort by last name) and search for available Teachers

• ** Teacher Achievements

Teacher-Head

• Assigns the Teacher to teach the Subject

• Can add or remove Teachers

Subject

• Class(s) teaching the Subject

• List of Students studying the Subject

• View (sort by name and by class) and search for Subjects

• ** Educational materials for the Subject (pdf, word, …, pictures, text, links to video materials)

• ** Tasks for the Subject (tests with one or more correct answers that the teacher can create)

• ** The Teacher can add and delete educational materials and create their own tests in the test designer

Student

• Subjects studied by the Student

• Success (list of grades and average score)

• View (sort by surname, by class, by success) of all students

• Pagination

• Search for students

• ** Student achievements (winner/prize winner of olympiads, competitions, tournaments, competitions)

​Teaching and accounting materials

• Class schedule with presentation in the form of a calendar;

• Grade log (date - grade (or absence/lateness))

• A student can only see his own grade statistics

• A teacher can see statistics for all students for his Subjects

GitHub

• The project must be posted to a public GitHub repository

• ** There must be a history of development, branch creation, commits, pull requests, and activity of all team members

Architecture

• The project must include a database, backend, and frontend, developed in compliance with generally accepted programming principles.

• Use of OOP;

Documentation and Instructions

• Documentation (Readme.md) for the project.

• Detailed step-by-step instructions for local deployment of the project. Explain how to deploy all its components (including the database). It is important to develop a clear approach: if the jury members fail to launch the project, it will not be evaluated.

Stability

• The project must work without errors and bugs.

** Testing

• Ensure code coverage with tests, including integration with a plugin for tracking test coverage.