1) continue listing at least 5 entities across the top of your paper. Remember, the entities are related in some way.
2) continue listing at least 5 attributes or characteristics of each entity. The attributes will be listed below each entity, in a list.
For example: student ---------
3) you will find that information in one entity (table) is related to information in another entity (table), such as how a student is related in some way to a class. Really a student does not have anything to do with a class, except that a student might be taking a class, which is a description of the relationship. So to get a roster for a class (A110 for example) you would not need to include all student information (for each student) in the class table, but you could insert a key piece of information into the class table, that would be explicit enough to get information from the student table. Can you see it? It is the studentID (the primary, key field, in the student table). If you insert this key (as foreign key) into the class table, then you will have forged a relationship between these two tables. Your assignment: make these kinds of relationships for the remaining tables as necessary (they do not all need to be related to one another, AND you will more than likely have only one relation between two tables).
4) draw lines between the tables that are related (from the primary key in one table to the foreign key in another table). 5) show the type of relation (one-to-many, many-to-many, etc.). Place a "1" at one end of a relationship line when referring to a primary key. Often the same key is foreign in another table, and it can appear many times in that table. If this is case, place a "many" (infinity) symbol at that end of the relationship line when referring to the foreign key.
-------------- grading --------------
2 points: if you have at least 5 entities that are part of the group (related)
2 points: if you have at least 5 attributes per entity. No points for values (data)
2 points: if you insert foreign keys into appropriate tables (less is more in this case, not the other way around)
2 points: if you create appropriate relationships between your key fields (again, less is more in this case. A primary key does not need a foreign key in all other tables. You will probably only have 4-7 relationships defined.)
2 points: if you designate the appropriate relationship types (one-to-many, etc.)
Bonus: +2 points - implement this ERD in ms-access (bring back only the diagram from the relationships view).