Key entities/tables based on Course Management System architecture and Course Management System Project and their relationships based on the architecture and technology stack mentioned:
Course Management System Data Model
| Entity | Fields | Relationships | Purpose |
|---|---|---|---|
| Courses | – Course ID – Course Name – Course Description – Credits – Syllabus – Instructor ID | – One-to-Many (Instructors, Enrollment) – Many-to-One (Prerequisites) | Stores information about each course offered in the system, including its details and instructor. |
| Instructors | – Instructor ID – Name – Department – Phone | – One-to-Many (Courses) | Stores details of instructors responsible for delivering the courses. |
| Students | – Student ID – Name – Enrollment Status – Program | – Many-to-Many (Courses via Enrollment) | Holds student data and enrollment status for tracking participation and progress. |
| Enrollment | – Enrollment ID – Student ID – Course ID – Enrollment Date – Grade | – Many-to-Many (Students, Courses) | Tracks student enrollment in specific courses and their progress (grades). |
| Course Documents | – Document ID – Course ID – File Name – File URL – Upload Date | – Many-to-One (Courses) | Stores and links course-related documents (syllabus, learning materials, etc.) stored in SharePoint. |
| Prerequisites | – Prerequisite ID – Course ID – Prerequisite Course ID | – Many-to-Many (Courses) | Stores prerequisite course data, ensuring proper course enrollment sequence. |
| Notifications | – Notification ID – Course ID – Notification Message – Send Date | – One-to-Many (Courses) | Stores system-generated notifications for deadlines, updates, etc., automated through Power Automate. |
| Workflows | – Workflow ID – Description – Trigger – Action | – One-to-Many (Courses) | Manages automated workflows like notifications and document approvals, linking SharePoint and Dataverse. |
Key Relationships:
- One-to-Many (Courses and Instructors): An instructor can teach multiple courses, but a course is associated with only one instructor.
- Many-to-Many (Students and Courses): Students can enroll in multiple courses, and each course can have many students. This is tracked via the Enrollment entity.
- One-to-Many (Courses and Course Documents): Each course can have multiple documents (syllabus, materials), managed and stored in SharePoint.
- Many-to-Many (Courses and Prerequisites): Courses can have prerequisites, allowing you to define relationships between advanced courses and their foundational ones.