SQL class : Desperate need of homework assistance and explanation

A database at a college must support the following requirements:

For a department, store its number and name.

For an advisor, store his ID number, last name, first name, the department number to which he is assigned. (We will assume an advisor works for only one department, not two or more.)

For a course, store its code and description (for example, MTH110, Algebra and our course CIS452, Structured Query Language).

For a student, store his ID number, first name, and last name.

For each course the student takes, store the course code, the year and semester enrolled, and the grade earned.

Also assume that a student has a single advisor. Advisors each have several students whom they advise, but a student only has one advisor. Be sure to design this relationship into your solution.

Design the database for the preceding set of requirements. Use your own experience as a student to determine and functional dependencies. You will likely have some questions that arise about this fictitious scenario. You can MAKE YOUR OWN ASSUMPTIONS as the answers to these questions, but document these assumptions in writing. For example, lets pretend you have this question burning in your mind Is the StudentID number just like the FacultyID number or are they different? My response to such a question is, You decide and then list the decision as an ASSUMPTION. You can continue making assumptions and documenting them in the space provided. In the real word, a database designer would go visit with the actual people who would be users of the database and ask them about the validity of each item in the ASSUMPTIONS list.

ASSUMPTIONS

StudentID and AdvisorID are similar in structure. For example 000056723 and 884027634 could belong to a student or to an advisor.