Write each table in a uniform way. Explicitly specify primary key={.....}. If there is a foreign key in the table you're writing, foreign key ={....} references tablename, instead of "attribute".

Suppose we have the following requirements for a university database that is used to keep track of students transcripts and faculty affiliation 1. The university keeps track of each student's name, student number, social security number, current address and phone, permanent address and phone, birthdate, sex class (freshman, sophomore graduate), major department, minor department (if any), and degree program(B.A., B.S., Ph.D.). Both social security number and student number have unique values for each student 2. Each department is described by a name, department code, office number, office phone, and college. Both name and code have unique values for each department 3. Each course has a course name, description, code number, number of semester hours level, and offering department. The value of code number is unique for each course. A. Each section has a professor who teaches it, semester, year, course, and section num ber. Section numbers distinguish different sections of the same course that are taught during the same semester/year; its values are 1, 2, 3, up to the number of sections taught during each semester 5. Each professor is identified by social security number, and further described by last name, first name, DOB, expertise, and office phone 6. Each professor is associated with exactly one department as main affiliation 7. Each department has a professor as its chairperson. This fact needs to be documented 8. A grade record refers to a student, refers to a particular section, and grade Design an relational database (schema) for this database application. The schema has to satisfy at least 3NF requirement. S pecify the all applicable attributes of each relation and also indicate data type for each attribute. Note any unspecified requirements, and make appropriate assumptions to make the specification complete. Each relation has to be represented properly in at least the form: relation-name (attribute-1, attribute 2, with keys identified and data type explicitly specified. Please use normal naming convention for l relations and attributes