See in Description "Database Design and Implementation"
As explained throughout this course, entity relationship modeling is a critical element of database design. If the database is not properly modeled, it is unlikely that the database will be properly developed. Using this knowledge, explain the key reasons why entity relationship modeling is important, and determine at least (1) way in which it impacts the overall development of the database.
Analyze the key ways that entity relationship modeling helps database developers overcome potential design challenges and conflicting goals.
For the database that you described in the Week 1 and Week 2 discussions, determine the major / minor challenges that might exist when you are creating an entity relationship diagram (ERD) for the business function / operation.
Systems have databases that store data in tables that allow for easy retrieval and updating the records stored. The data is stored in tables have relationships with the other different tables to make data management more effective. To understand better this relationships between the different entities in databases and clearly define them, visual diagrams are used to show the internal relationships and how they are linked to real world entities using the entity relationship diagrams. The diagrams clearly show the information created, stored and used by a system (Bagui & Earp 2003).
These entities can be in physical resources, events, and agents related to an organization. They are real world objects that are distinguishable from other objects with each entity having a set of distinguishing attributes. Entity relationship diagrams are useful tools for modeling entities in a database and showing the relationship of real world entities. The ER model helps to group the entities to entity sets that enable for clarity in their hierarchies which is important during system design. The diagrams help to organize items as well as valuable information related to the system entities. Also, they help order the business requirements with clarity. They are used by system developers to prevent the designing conflicting system services. (Rosenblatt 2013) Different integrity constraints can be expressed through ERD models which are useful in system development. The different constraints include participation, key and overlap constraints. However, it is important to note that not all constraints can be expressed using the entity relationship model such as the functional dependency constraint.
Challenges that might exist when creating an entity relationship diagram for our business function/operation access to the building and offices. The major challenge would be to design the structure to allow the right people access to the correct offices. Some offices are only allowed to the people with Top Secret clearances, some with Secret clearances, and others you do not need any clearance. Once you get everyone assigned clearances to the correct office everything else should fall into place. The minor challenge would be making sure the fingerprint is assigned to the right person.
Bagui, S. & Earp, R. (2003). Database design using entity-relationship diagrams. Boca Raton, FL: Auerbach. Rosenblatt, H. (2013). Systems Analysis and Design. Florence: Cengage Learning.
