Given the business rules below, draw a fully-labeled ERD in 3NF that included entities, specified attributes (mark required attributes), labeled relationships (indicate whether each relationship participation is mandatory or optional, strong or weak), primary keys, foreign keys, and cardinalities. Follow the format (Crows Foot Notation) and naming conventions. Do not add additional rules but justify your design assumptions if any. The description of the company and business rules are given below.

A college wants to improve its management of advising and asked you to design a database to link faculty advisors with students.

Business Rules are as follows:

The college has nine departments.

The department has a name, phone contact and email contact.

A program of study has a name and type.

A department manages many programs, but not more than 10.

A program belongs to one department.

For a student we must keep the name and email contact.

A student is enrolled in on or more programs, but not more than 3.

An advisor works for a single department but may advise all the programs in that department. Each department must have an advisor but there might be more than one.

For an advisor you must keep the name and email.

Each advisor has an education level: Bachelor, Master, or PhD.

A student may book a private advising session with only one advisor at a given time.

You must record all advising sessions a student had.

For a session you must keep the date, time and location.

To help the students pick an advisor the department identified 20 areas of advising (e.g. late registration).

Each area of advising has only on main advisor.

An advisor may be a main advisor for several areas.

For an area you must keep the name of the area and the recommended duration of an advising session.