A. Draw an E-R data model for the Highline University Mentor Program Information System (MPIS). Use the IE Crow’s Foot E-R model for your E-R diagrams. Justify the decisions you make regarding minimum and maximum cardinalities. Your model should track students, advisers, and mentors. Additionally, Highline University needs to track alumni because the program administrators view alumni as potential mentors.1. Create separate entities for students, alumni, faculty advisers, and mentors. • At Highline University, all students are required to live on campus and are assigned Highline University ID numbers and email accounts in the format FirstName. [email protected]. The student entity should track student last name, student first name, student University ID number, student email address, dorm name, dorm room number, and dorm phone number.a.At Highline University, all faculty advisers have on-campus offices and are assigned Highline University ID numbers and email accounts in the format FirstName. [email protected]. The faculty entity should track faculty last name, faculty first name, faculty University ID number, faculty email address, department, office building name, office building room number, and office phone number.b. Highline University alumni live off campus and were previously assigned Highline University ID numbers. Alumni have private email accounts in the format FirstName. [email protected]. The alumni entity should track alumnus last name, alumnus first name, alumnus former-student number, email address, home address, home city, home state, home ZIP code, and phone number.c.Highline University mentors work for companies and use their company address, phone, and email address for contact information. They do not have Highline University ID numbers as mentors. Email addresses are in the format FirstName. [email protected]. The mentor entity should track mentor last name, mentor first name, mentor email address, company name, company address, company city, company state, company ZIP code, and company phone number.2. Create relationships between entities based on the following facts: • Each student is assigned one and only one faculty adviser and must have an adviser. One faculty member may advise several students, but faculty members are not required to advise students. Only the fact of this assignment is to be recorded in the data model—not possible related data (such as the date the adviser was assigned to the student).a.Each student may be assigned one and only one mentor, but students are not re-quired to have a mentor. One mentor may mentor several students, and a person may be listed as a mentor before he or she is actually assigned students to mentor. Only the fact of this assignment is to be recorded in the data model—not possible related data (such as the date the mentor was assigned to the student).b. Each mentor is assigned to work and coordinate with one and only one faculty member, and each mentor must work with a faculty member. One faculty member may work with several mentors, but faculty members are not required to work with men-tors. Only the fact of this assignment is to be recorded in the data model—not possible related data (such as the date the faculty member was assigned to the mentor).c.Each mentor may be an alumnus, but mentors are not required to be alumni. Alumni cannot, of course, be required to become mentors.
In the week 4 assignment, you created an ER diagram to detail information on students, alumni, faculty advisers and mentors. For this week's assignment, I want the SQL required to build these tables. Include sample data in for your schema.
SQL Script should have 'create' statements for each of the tables/columns, primary keys established, and foreign keys between the relationships established. Provide a few rows for each table as sample data to ensure relationships work correctly between tables.