Class Exercise:  One-to-Many(1:M) Database Modeling

                 
For data models with two or more entity classes, a line between classes may be 
drawn to indicate they are related. One technique to depict a 1:M relationship
is to draw a one or vertical bar next to the entity class on the "one" end of a
relationship line to indicate existence, and draw a "crow's foot" (e.g. overlay
an angle bracket) on the relationship line next to the entity class that may 
occur "many" times. To further refine the rules about a relationship, a 0 or 1
may be placed next to the "foot" to indicate zero or more, or one or more 
instance occurrences. And, 0's and 1's may be placed on the "one" end to 
indicate zero or one, or one and only one instance occurrence.

1. Construct a data model to depict the entity class Faculty. A faculty member
   may be identified by faculty id(fId), and fId may be expected to be non-null
   and persistent (non-changing). Other attributes include faculty name(fName),
   office, and phone.










2. Construct a data model for the class Course. Course has the primary key 
   course code (cCode), and has a title (cTitle), classRoom, and meetingTime.










3. Depict a one-to-many (1:M) relationship between Faculty and Course. A 
   faculty member may be assigned to teach many courses, but a course is 
   to be taught by exactly one faculty member.  










4. Expand the Faculty:Course data model to include an Advisee entity class 
   related to the entity class Faculty. A faculty member may have many 
   Advisees, though an Advisee is to be assigned to just one Advisor. Create
   useful attributes for the Advisee class.