Create a normalized Entity-Relationship Model
nancyj
Create_a_normalized2.docxCreate a normalized (this means third normal form) Entity-Relationship (E-R) model for a University WebCampus transactional database. Make sure you include
DEPARTMENT (DeptCode, DepartmentName, CollegeCode); SITE (SiteCode, SiteName, AddressLine1, AddressLine2, AddressLine3, City, State, ZipCode, Phone, Fax, Email);
TUITION (SiteCode, DegreeLevelCode, TuitionPerCredit); COLLEGE (CollegeCode, CollegeName); TERM (TermCode, TermDescript); COURSETYPE (CourseTypeCode, CourseTypeDescript); TRIMESTER (TrimesterCode, TrimesterDescript); STATE (StateCode, StateName); DEGREELEVEL (DegreeLevelCode, DegreeLevelDescript).
But, don't forget about other entities like COURSES, STUDENTS, and INSTRUCTORS. Resolve the many-to-many relationships with association entities. Show the foreign keys (FK) and primary keys (PK) in the box for each entity. (Note: Every entity must have a primary key. Not every entity has a foreign key.) The list of attributes for each entity can be shown on a separate page if there is not enough room in the entity box on the E-R diagram. Create the E-R diagram in MS Visio. If for some reason MS Visio does not run your PC, you can use another drawing tool such as PowerPoint or the free software available here: http://dia-installer.de/ Make sure the keys in your diagram are clearly labeled, and your diagram shows the relationships between the entities using the crow's foot notation.
For an example of what a complete E-R model looks like, see the attached PowerPoint. Although this example is in PowerPoint, using Visio is easier. The example is for a games database.
