International Research Journal of Engineering and Technology (IRJET) e-ISSN: 2395 -0056 Volume: 02 Issue: 04 | July-2015 www.irjet.net p-ISSN: 2395-0072 COMPARATIVE STUDY ON EXTENDED ENTITY RELATIONSHIP AND UNIFIED MODELING LANGUAGE *1Mrs. Kavitha S., *2Ms. Nancy A., *1Assisant Professor, Department of Computer Science Auxilium College (Autonomous), Vellore, TamilNadu, India *2M.Phil Research Scholar, Department of Computer Science Auxilium College (Autonomous), Vellore, TamilNadu, India ---------------------------------------------------------------------***--------------------------------------------------------------------- Abstract - Entity Relationship modeling is the process to represent an object without knowing its properties, but of coming up with an abstract and conceptual in the relational model need to know its key attributes. representation of data. Entity Relationship diagrams Specialization ultimately model the databases. Entity Relationship Specialization Process of defining a set of model is generally better in relationship name and subclasses of an entity type. Defined on the basis of some participation representation than the Unified Modeling distinguishing characteristic of the entities in the super Language diagram. In Extended entity relationship class. Describing the relationship Super class/subclass or diagram is describing the data requirements for a new Class/subclass Super type/subtype or Type/subtype. information system in a direct and easy to understand Subclass can define: Specific attributes Specific graphical notation. Unified Modeling Language has a relationship types. Subclass can be subclass write more direct relation with object oriented analysis and design than one super class. to representation for the cardinality relationship compared with Entity Relationship diagrams. The fields Generalization are entities, attributes, relationship, cardinalities, Generalization Process of defining a more general identifiers to use the Extended Entity Relationship and entity type from given entity types reverse process of Unified Modeling Language diagrams with the specialization. Generalize into a single super class. Original representing notation. entity types are specialized subclasses. Entities in Key Words: Entity Relationship model, Extended entity generalization must all come from subclasses relationship (EER), Unified Modeling Language, object generalization is the reverse of the specialization process. oriented analysis and design. Several classes with common features are generalized into a super class; original classes become its subclasses. I. INTRODUCTION 1.1 Unified Modeling Language UML is a standard language for specifying, The Extended entity relationship (EER) model is a visualizing, constructing, and documenting the artifacts of conceptual (or semantic) data model, capable of software systems. UML stands for Unified Modeling describing the data requirements for a new information Language. UML is different from the other common system in a direct and easy to understand graphical programming languages like C++, Java, COBOL, etc.UML is notation. Data requirements for a database are described a pictorial language used to make software blue prints so in terms of a conceptual schema, using the EER model. EER UML can be described as a general purpose visual model of EER schemas are comparable to UML class modeling language to visualize, specify, construct and diagrams. Actually, what will be discussing is an extension document software system. of Peter Chen’s proposal (hence “extended” ER). These represent classes of objects (facts, things, people...) that 1.2 UML Class Diagram have properties in common and an autonomous existence. The EER model is very different from the relational model The class diagram is a static diagram. It in a number of ways; for example, in EER it is not possible represents the static view of an application. Class diagram © 2015, IRJET.NET- All Rights Reserved Page 390 International Research Journal of Engineering and Technology (IRJET) e-ISSN: 2395 -0056 Volume: 02 Issue: 04 | July-2015 www.irjet.net p-ISSN: 2395-0072 is not only used for visualizing, describing and of abstraction at which the developer operates, requiring documenting different aspects of a system but also for the developer to learn a new higher-level language that constructing executable code of the software application. may then be mapped into lower-level. The class diagram shows a collection of classes, interfaces, associations, collaborations and constraints. It is also The experiment and two replications aimed at known as a structural diagram. comparing the support provided by ER and UML class diagrams during comprehension activities by focusing on 1.3 UML Object Diagram the single building blocks of the two notations. The results Object diagrams are derived from class diagrams reveal that UML class diagrams are generally more so object diagrams are dependent upon class diagrams. comprehensible than ER diagrams, even if the former has Object diagrams represent an instance of a class diagram. some weaknesses related to three building blocks. These The basic concepts are similar for class diagrams and findings suggest that a UML class diagram extension object diagrams. Object diagrams are used to render a set should be considered to overcome these weaknesses and of objects and their relationships as an instance. improve the comprehensibility of the notation. A data model is a set of concepts that can be used to describe II. Related work both the structure of and the operations on a database. The evaluation process of conceptual specifications developed using either Extended Entity- UML can be used to study mappings to different Relationship (EER) or Unified Modeling Language (UML) types of database systems. Introducing UML through a conceptual models. It provides a comprehensive comparison to the EER model, UML diagrams are used to framework for evaluating EER and UML conceptual teach different approaches for mapping conceptual schemas. Furthermore, it defines classes of metrics designs to the relational model. It cover object-oriented facilitating the evaluation process and leading to the and object-relational database systems, different features choice of the appropriate representation among several of UML are used over the same enterprise to understand schemas describing the same reality. Based on quality mapping alternatives for each model for object-oriented criteria proposed in the literature to select a subset of and object-relational database systems. In the relational criteria relevant to conceptual EER schema quality and object-relational models that require the development evaluation. Finally, this evaluation process to UML of code to maintain inverse relationships to address the schemas Following the development of framework, mapping techniques from the point of view. analyze a case study and provide evidence in the support of the usefulness of the framework. III. PREVIOUS IMPLEMENTATIONS The EER contains all concepts of ER. EER adds It created to design more accurate database more concepts like Specialization/Generalization, schemas reflect the data properties and constraints more Subclass/Super Class, Categories and Inheritance to get precisely. More complex requirements than traditional more accuracy than ER. UML includes a set of graphic applications. The Extended Entity-Relationship (EER) notation techniques to create visual models of Object- model is a conceptual (or semantic) data model, capable of oriented software intensive systems. Unified Modeling describing the data requirements for a new information Language is a standard for software development. EER system in a direct and easy to understand graphical Diagram on the other hand is used for database design. notation. Data requirements for a database are described in terms of a conceptual schema, using the EER model. EER Executable UML is fundamental approach to model EER schemata are comparable to UML class Model Driven Architecture a new way of writing diagrams. Actually, what we will be discussing is an specifications and developing applications, based on a extension of Peter Chen’s proposal (hence “extended” platform-independent model (PIM).In software ER).These represents classes of objects (facts, things, engineering, many industries used to build systems by people...) that have properties in common and an soldering wires together to form hard-wired programs. autonomous existence. Notion of object-orientation, an approach for structuring data and behavior together into classes and objects. Its moved from one language to another, Increased the level © 2015, IRJET.NET- All Rights Reserved Page 391 International Research Journal of Engineering and Technology (IRJET) e-ISSN: 2395 -0056 Volume: 02 Issue: 04 | July-2015 www.irjet.net p-ISSN: 2395-0072 Attributes are 14 UML diagram types to help you model this These describe the elementary properties of behavior. They can be divided into two main categories entities or relationships. An attribute associates with each structure diagrams and behavioral diagrams. instance of an entity (or relationship) a value belonging to a set known as the domain of the attribute. The domain 4.1 Class Diagram contains the admissible values for the attribute. Class diagrams are used UML diagram type. It is For example, Surname, Salary and Age are the main building block of any object oriented solution. It possible attributes of the Employee entity, while Date and shows the classes in