Create A Normalized Entity In Third Normal Form

Create A Normalized This Means Third Normal Form Entity Relationship

Create 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: 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. Create 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: 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. Create 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: 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. Although this example is in PowerPoint, using Visio is easier. The example is for a games database. The relationships between the entities: An Account has zero or one PC – zero means a customer has created an account but not linked it to a PC yet A PC / Account combination has one and only one Account A Digital Signature is associated with one and only one Account An Account has zero to many Digital Signatures – zero means the customer has yet to download a game A Country can have zero to many Accounts An Account have one and only one Country A State-Province can have one and only one Country A Country can have zero to many State-Provinces A Pricing record has zero to many Accounts – zero means no customer is using that Pricing An Account has one and only Pricing record A Pricing record has one and only Account Type An Account Type has one to many Pricing records A Currency has one to many Pricing records A Pricing record has one and only Currency A Game has zero to many Digital Signatures – zero means no customers have downloaded that game A Digital Signature is associated with one and only one Game A Rating can be associated with zero to many Games A Game can have one and only one Rating A Game belongs to one or more Genres A Genre has zero to many Games – zero means a new genre without games yet A Game_Genre has one and only one Game A Game_Genre has one and only one Genre An Account has one and only one Gamer A Gamer has zero to many Accounts