Conceptual Modeling: Create a conceptual model for the below requirements using the ER Model $($Specify your relationship types$)$ or EER model. You can use drawing tools to create your ER models.

Based on the project requirements and description provided, here's a conceptual database design:

$1.**$Entities and Attributes:$**$

$-**$Employee:$**$

$-$ EmplID $($Primary Key$)$

$-$ Name

$-$ SSN

$-$ Phone

$-$ Email

$-$ Address

$-$ Office Location

$-$ Date of Hire

$-$ Role $($Faculty$/$Staff$)$

$-$ DepartmentID $($Foreign Key referencing Department$)$

$-**$Faculty:$**$

$-$ Rank

$-$ Specialization

$-$ Areas of Research Interests

$-$ Areas of Teaching Interests

$-**$Staff:$**$

$-$ Position

$-**$Department:$**$

$-$ DepartmentID $($Primary Key$)$

$-$ Name

$-$ Phone

$-$ Office Location

$-$ Chairperson $($Foreign Key referencing Employee$)$

$-$ Chairperson Start Date

$-$ Secretary $($Foreign Key referencing Employee$)$

$-$ Secretary Start Date

$-**$Course:$**$

$-$ CourseID $($Primary Key$)$

$-$ Course Name

$-$ Course Code

$-$ Hours

$-$ Credits

$-$ Description

$-$ DepartmentID $($Foreign Key referencing Department$)$

$-**$CourseSection:$**$

$-$ SectionID $($Primary Key$)$

$-$ CourseID $($Foreign Key referencing Course$)$

$-$ Semester Year

$-$ Room Number

$-$ Schedule

$-$ InstructorID $($Foreign Key referencing Employee$)$

$-**$Major:$**$

$-$ MajorID $($Primary Key$)$

$-$ Name

$-$ Description

$-$ Type of Degree

$-$ Total Credits Required

$-$ AdvisingFacultyID $($Foreign Key referencing Employee$)$

$-**$Student:$**$

$-$ EmplID $($Primary Key$)$

$-$ First Name

$-$ Middle Initial

$-$ Last Name

$-$ Date of Birth

$-$ Email

$-$ Phone

$-$ Address

$-**$Graduate:$**$

$-$ EmplID $($Primary Key, Foreign Key referencing Student$)$

$-$ Graduation Year

$-$ Degree Earned

$-$ Honors

$-$ GPA

$-$ Current Job Title$/$Occupation

$-$ EmployerID $($Foreign Key referencing Employer$)$

$-**$Employer:$**$

$-$ EmployerID $($Primary Key$)$

$-$ Employer Name

$-$ Industry

$-$ Address

$-**$CheatingIncident:$**$

$-$ IncidentID $($Primary Key$)$

$-$ Date

$-$ Description

$-$ Resolution

$-$ StudentID $($Foreign Key referencing Student$)$

$-$ SectionID $($Foreign Key referencing CourseSection$)$

$-**$Enrollment:$**$

$-$ StudentID $($Foreign Key referencing Student$)$

$-$ SectionID $($Foreign Key referencing CourseSection$)$

$-$ Grade

$2.**$Relationships:$**$

$-**$Employee $-$ Faculty$/$Staff:$**$ One$-$to$-$One $($An employee can either be faculty or staff$)$

$-**$Employee $-$ Department:$**$ Many$-$to$-$One $($Many employees can belong to one department$)$

$-**$Faculty $-$ Major:$**$ Many$-$to$-$Many $($A faculty member can advise multiple majors, and a major can have multiple advising faculty$)$

$-**$Department $-$ Course:$**$ One$-$to$-$Many $($One department can offer multiple courses$)$

$-**$Course $-$ CourseSection:$**$ One$-$to$-$Many $($One course can have multiple sections$)$

$-**$CourseSection $-$ Instructor:$**$ Many$-$to$-$One $($Many sections can be taught by one instructor$)$

$-**$Major $-$ Student:$**$ Many$-$to$-$Many $($A student can pursue multiple majors, and a major can have multiple students$)$

$-**$Student $-$ Graduate:$**$ One$-$to$-$One $($One student can become one graduate$)$

$-**$Graduate $-$ Employer:$**$ Many$-$to$-$One $($Many graduates can work for one employer$)$

$-**$CourseSection $-$ Enrollment:$**$ Many$-$to$-$Many $($Many students can enroll in many course sections$)$

$-**$Student $-$ CheatingIncident:$**$ One$-$to$-$Many $($One student can have multiple cheating incidents$)$

$-**$CourseSection $-$ CheatingIncident:$**$ One$-$to$-$Many $($One course section can have multiple cheating incidents$)$

This design captures the relationships between various entities involved in managing employees, courses, majors, students, graduates, employers, and incidents like cheating. Adjustments can be made based on specific business rules and requirements.