100%(6)6 out of 6 people found this document helpful
This preview shows page 3 - 5 out of 17 pages.
To detail the relationship among the entities please refer to the following:A.Management manages the employeeB.Management is responsible for the department C.Management hires the customerD.Employees work with management E.Employees are part of the department F.Employees work with the customerOnce the relationships have been defined the lines must be drawn between the entities defined bythe relationships. Please see Appendix B - relationships defined by diamonds.3. Each relationship type; 1:1, 1:M, or M:N can be seen in Appendix C. Each relationship type has a specific symbol to show correspondence to the definitions. For example, A manager who manages many employees is shown as (1:M). This can be interpreted as one manager who can only manage only one or multiple employees. Please see Appendix D.4. Finally, identification of the entity attributes is defined and results can be determined. Please see Appendix E for details. There are risks when creating the ERM Diagram when developmental or iterative steps
Database Monitoring and NormalizationPage 4are not performed. Some common components organizations use: Entities, attributes, relation-ships and constraints. The database model is built with specific entities in mind, usually defined by the organization (Carpenter, D. A. 2008, p. 381). Attributes can be defined as features of the actual entities. Relationships are assumed as the set of correlation among the interacting entities. Finally, the constraint is the limitation of the relationship which will ensure overall database in-tegrity. No standard modeling exists which would be suitable for all system types, however each model will align with the organization requirements. Each organization will have a different model based on its system and needs. System components are the basic collection in which to implement a system model (Eessaar, E. 2016, p. 5). With that being stated, all information must be researched and defined correctly. If any of the components are missed or defined incorrectly the database will fail. Risk management is an important part to the success of the database.Some entities that are required for development of the data repositories can be deter-mined through various effective entities within the organization. These entities are required for the development of the data repositories. Entities that are implemented by each department in theorganization can be reviewed and added to the database. Tasks that are performed by the organi-zation are also important to list. Entities to review are management, department, employee, salary and customer (El-Sofany, H. H. and El-Seoud, S. S. 2009, p. 15-17). Departments such as planning, training, security and hiring could be included as well.