Create Tables and Queries in MS Access

Database Design

Student Name

Student Id

Institution

Date of Submission

Database Design

Assumptions about Business Rules and Relationships

Enrollment Process: To manage the many-to-many relationship between students and courses, I've introduced an "Enrollment" entity. This assumption is based on the common practice in colleges where students enroll in courses. The Enrollment entity has an EnrollmentID (Primary Key) and an Enrollment Date attribute, which captures the date when a student enrolls in a course.

Instructor-Course Relationship: I assumed that each course is taught by a single instructor. This simplifies the relationship between the Instructor and Course entities to a one-to-many relationship. However, in reality, there might be situations where multiple instructors co-teach a course or an instructor teaches multiple courses.

Attributes: I included essential attributes for each entity based on the scenario. However, there might be additional attributes that the college wants to track, such as Student GPA, Course Schedule, Instructor Qualifications, and more.

Cardinality: The cardinality indicators on the relationships (1 or Many) reflect the assumptions I made about the number of entities that can be involved in each relationship. These assumptions should be confirmed with the client or stakeholders to ensure accuracy.

Primary Keys: I assumed that each entity has a unique identifier (Primary Key) to distinguish records. StudentID, CourseID, and InstructorID are used as primary keys for their respective entities.

Reference

Mistler, S. A., & Enders, C. K. (2012). Planned missing data designs for developmental research. https://psycnet.apa.org/record/2012-07988-041