Database Design and Entity Relationship Model

Queston: Describe the database design, entity relationship model,and database implementatiin? Answer: Database design methods According to the requirements of the database, the first step for designing a database is to create the structure of the database with the help of various tables of the database. The second step is to create the database is the designing of the table and entity relationship model. The third step for designing the database is to determine the primary keys as well as the foreign keys from different tables. The third step for creating a database is the normalization; the normalization of the table can be broadly categorized into five kinds such as, first normalization form or 1NF, second normalization form or 2NF, third normal form or 3NF, fourth normal form, fifth normal form and the Boyce-codd normal form. The entity relationship model can be referred to as such kind of data model which describes the relationship between different tables and attributes of the table. The relationship model is basically used for designing the relational database. From the model of entity relationship va rious relationships between the several data can be found whether it is one to one relationship or one to many relationships model. The normalization process of database design can be defined as such kind of process which is used to organize the attributes of the tables of the relational database to reduce the redundancy. Database design 1) Entity relationship model The entity relationship model showcases the relationship between four tables such as management table, member table, accessories table and player table. The management table consists of four entities such as admin_Id, Admin_name, admin_contact no and the admin_address. The membership detail consists of four entities such as Mem_Id, Mem_name, Mem_address and Email_id. The accessories table consists of three entities such as no of balls, no of rackets and the number of footballs. The player table consists of four entities such as player_id, player_name, player_contact number and email_id. The management table has 1 to n relationship with membership detail, player table and the accessories table. The membership details table has a relationship with the player table. The player table also has a relationship with the accessories table. 2) 3NF form of the structure The above relationship diagram showcases the third normalization form of the relational database. The third normalize form is constructed between the two tables such as membership details and the player. The player table consists of four entities such as player_id, player_name, player_contact no and the email_id and the membership details consist of 4 four entities. The member id is associated with the player id and the member name is associated with the player name and the membership email id is associated with the player email id. Database implementation 1) 2) To create a table in MS access 2007 first, you should click on create blank database which will show the new blank database. The developer should enter the table name such as membership details, player details, management details and accessories details. After that the developer should double click on add new fields where in table design view the developer should enter the various column name of that table. After filling up all the tables with different entities the developer should click on save button to save the tables. After filling up all the details of the table the designer should click on the database tools to click the relationship to create entity relationship of the database model. The entity relationship showcases the different types of relationship like 1 to n or 1 to 1 relationship between different tables and its entities. The management table has many relationships with the membership table, player table and the accessories table. The third normalization form of the d atabase has also been described in this design. The 3NF normalization has been created between the two tables such as the membership details table and the player table. 3) The overall design report have been described in the above screenshot which denotes the four different tables such as the membership details, player table, management table and the accessories table. The four tables have different types of entities which also related with the entities of the other tables. References Bain, M. and Whitehead, A. (2007).SugarCRM developer's manual. Birmingham, U.K.: Packt Pub. Haley, M. (2005).The Concordance database manual. Norwood Mass.: Books24x7.com. Harrington, J. (2002).Relational database design clearly explained. New York: Morgan Kaufmann Publishers. Hernandez, M. (1997).Database design for mere mortals. Reading, Mass.: Addison-Wesley Developers Press. Lightstone, S., Teorey, T. and Nadeau, T. (2007).Physical database design. Amsterdam: Morgan Kaufmann/Elsevier. Ling, T., Lee, M. and Dobbie, G. (2005).Semistructured database design. New York: Springer. McHugh, P. (1989).Alaska IPASS database preparation manual. Portland, Or. (319 S.W. Pine St., P.O. Box 3890, Portland 97208): U.S. Dept. of Agriculture, Forest Service, Pacific Northwest Research Station. Penney, A. (1997).Climate database (CLIDB) user's manual. Wellington, N.Z.: NIWA. Roman, S. (1999).Access database design programming. Sebastopol, CA: O'Reilly. Stephens, R. (2009).Beginning database design solutions. Indianapolis, IN: Wiley Pub. Stephens, R. and Plew, R. (2001).Database design. Indianapolis, Ind.: Sams. Teorey, T., Lightstone, S. and Nadeau, T. (2005).Database modeling design. Amsterdam: Elsevier.