Running Header: DATABASE AND ERD DESIGN 1
DATABASE AND ERD DESIGN 2
Logical database design involves the process of describing entities in a database, the attributes that constitute each entity, and the relationships that exist among various entities. In our case, the art Work Museum constitutes entities such as the Artist, Section, and Artwork. The artist table is meant to store information concerning the various artist involved in artwork at the museum. It should therefore contain attributes such as artist’s first name, last name, ID, and artist artwork. The artist ID acts as the primary key which identifies each artist uniquely. Secondly, the section entity will store information on the location of the various artwork for easier location. The table should therefore contain attributes such as the section name, section ID, and artwork name in each given section.
Finally, the database should have an entity called artwork. This is meant to store information concerning all the artworks in the museum. The entity should have attributes such as artwork name, artwork ID, artist ID and the artwork location. The artist ID will act as foreign key in the artwork entity. This will act to establish the relationship between the artist and the artwork done. In our museum database, one Artist may have several artworks. On the other hand, one section may store several artworks. Several artists may also be stored in one section of the database. Each artwork must have a single location. It should also have a single artist assigned to it.
The Entity Relationship Diagram
Artist
Artist ID
Artist first name
Artist last name
Artist artwork
Section
Section name
Section ID
Artwork name
Artwork
Artwork name
Artwork ID
Artist ID
References
Kroenke, D., & Kroenke, D. (1977). Database processing (No. 04; QA76. 9. D3, K7.). Reading, MA: Science Research Associates.
Powell, G. (2006). Beginning database design. John Wiley & Sons.
Yeh, D., Li, Y., & Chu, W. (2008). Extracting entity-relationship diagram from a table-based legacy database. Journal of Systems and Software, 81(5), 764-771.