How leilibrk/learning-management-system-database-design works
This is a small Python/MySQL LMS coursework project. Students and professors use a console workflow: authenticate, then access role-specific course, assessment, and grading actions; the Python client invokes MySQL stored procedures and displays their results. The README documents enrollment and course-data design, while the SQL file is not excerpted, so its internal schema relationships cannot be detailed here.
Main entry points: main.py Professor actions · console.sql MySQL database
Components 13
Python client
- Console app
main.py - Authentication
main.py - Student actions
main.py - Professor actions
main.py
LMS capabilities
- Courses and enrollment
console.sql - Exam authoring
main.py - Exam participation
main.py - Homework authoring
main.py - Homework submissions
main.py - Review and grading
main.py
Database
- MySQL database
console.sql
Other components
- Student
- Professor
Connections 15
- Student → Console app: uses
README.md - Professor → Console app: uses
README.md - Console app → Authentication: authenticates
main.py - Authentication → MySQL database: calls login
main.py - Console app → Student actions: routes students
main.py - Console app → Professor actions: routes professors
main.py - Student actions → Courses and enrollment: views courses
main.py - Professor actions → Courses and enrollment: views students
main.py - Student actions → Exam participation: takes exams
main.py - Student actions → Homework submissions: submits homework
main.py - Professor actions → Exam authoring: defines exams
main.py - Professor actions → Homework authoring: defines homework
main.py - Professor actions → Review and grading: reviews and grades
main.py - Student actions → MySQL database: calls procedures
main.py - Professor actions → MySQL database: calls procedures
main.py