earticle

영어

A perfect design of the diagrammatic notations is necessary to communicate between the designer and the user at the requirements analysis stage. The Unified Modeling Language (UML) and Enhanced Entity Relationship (EER) are typically used for designing large systems and applications. On paper, diagrammatic notations can be used to develop or perform maintenance on the application. Any notations used, must represent business rules accurately. At the same time, the notations must be understandable to manager, user and programmer. ER and EER diagrams have been taught in colleges and universities for many years. In recent years, the Unified Modeling Language has appeared for the representation of relational databases. There are many articles in the literature discussing the efficacy of using the UML in modeling relational database systems. The choice between diagrammatic notations does not show any thoughtfulness for an understanding of the human reader. This study focuses on a comparison between the EER and the UML Class Diagram, the cause of the common notations and acceptance among system analysts and programmers. It was proven through an experiment on the sample of students participating in the experiment. The experiment takes the opinion of information technology students to determine which the best diagrammatic notation for them to use. These students will be programmers and system analysts in the future. The results identified through experiment are the favorite for graphic students, and the result can show any relational model closer to the user and manger.