Writing Homework Help

pls if you could reply to the following DQs with 150-200 words each. 

Nicole: 

An ER diagram stands for an entity-relationship diagram. Entities are objects that exist to be distinguished from other entities or objects (Yue, 2020).  The relationship portion represents associations between the different entities.  The benefits of ER diagrams are that they are easy to understand, more catered towards relational database modeling, and simple to design.  The disadvantages of ER diagrams are that they have limited expressive capabilities, sometimes can be not concise, and there is no standard design so sometimes they can be confusing to interpret.  The logical design of ER diagrams is more beneficial than just a physical design since it better illustrates all of the relationships between entities in a better manner.  If the information was simply in a table it would be harder to depict the relationships between each object. 

Yue, K. (2020). The ER Model and ER Diagram. The entity relationship model. http://dcm.uhcl.edu/yue/courses/csci4333/Fall2020/notes/model/ERDiagram.html. 

Sam:

ER diagrams present a visual depiction of data, and the relationships between data, that is intuitively understood by people working with the data (Ordonez et al., 2020, para. 1). This depiction facilitates communication about needs and goals related to the data. ERDs offer flexibility in that relationships can be created and removed as needed. If the logical design is skipped, connections between data may be difficult to discover. Data may get buried in the physical structure. Unnecessary redundancies may be created if the logical design is skipped. Disadvantages of diagrams are the time and cost related to the development of ERDs. In the life cycle of the system, the time and money put into development of diagrams will pay off in system flexibility and less problems, so these do not appear to be true disadvantages. Anther disadvantage is that there is no standard design system for ERDs. 

Ordonez, C., Al-Amin, S. T., & Bellatreche, L. (2020). An ER-flow diagram for big data [Conference]. IEEE. https://doi.org/10.1109/BigData50022.2020.9378088

Paula:

An entity relationship diagram (ERD) is one of the tools used when designing a database. The database designer uses the information gathered during the discovery phase and creates the ERD to map the relationships between entities. (Coronel & Morris, 2017). The benefit of the ERD helps to map the conceptual model to the logical model during this process. The visualization of relationships between entities and their attributes to describe the organization’s requirements can give a point of reference and better understanding of the database design process (Katz, 2020). 

The disadvantage or challenges of the ERD is that they may contain multiple data relationships that will prove difficult to operationalize into a database (Coronel& Morris, 2017).     

          The logical design becomes a map for the physical design or physical file organization and indexes (Bura, Singh, 2012).  By determining the entities, attributes and identifying primary and foreign keys prior to building the tables and columns for the database, this process should be easier to achieve these points have been verified by the end user.  If the designer goes straight to the physical design, the opportunities redundant and lack of cohesive relationships are more likely to occur (Coronel & Morris, 2017).

References:

Bura, D., Singh, R.K., (2019). Implementing Constraints in Entity-Relationship Models for Enhancing Normalization, IUP Journal of Information Technology, 8(2), 46-57. https://lopes. Idm.oclc.org/login?url=https://search.ebscohost.com/login.aspx?direct=tru… 78123397&site=eds-live&scope=site

Coronel, C., & Morris, S. (2017). Database systems: Design, implementation, and management (13th ed.). https://gcumedia.com/digital-resources/engage/2018…

Katz, A. (2020). Improved Teaching of Database Schema Modeling by Visualizing Changes in Levels of Abstraction. Journal of Information Systems Technology, 31(4), 294-311. https://lopes. Idm.oclc/login?url=https://search.ebscohost.com/login.aspx?direct=tru…