Consider a database for a university that represents students and classes. For simplicity, the database only needs to store the following information: Details of each student, such as their name, ID, and major Details of each class, such as its name, number, and syllabus Details about which student(s) are enrolled in which class(es), where a student can enroll in any number of classes and a class can have any number of students enrolled in it. With the information given, and considering the design principles discussed in class, how many tables should this database use to represent the information