International Research Journal of Engineering and Technology (IRJET)
e-ISSN: 2395 -0056
Volume: 04 Issue: 02 | Feb -2017
p-ISSN: 2395-0072
www.irjet.net
Review on Automation Tool for ERD Normalization A.S.Gaikwad, F.A.Kadri, S.S.Khandagle,N.I.Tava Student, Department of Computer Engineering, MET'S BKC IOE Nashik, Maharashtra, India Guided by Prof.Madhuri Shinde. Department of Computer Engineering, MET BKC ---------------------------------------------------------------------***---------------------------------------------------------------------
Abstract - Entity Relationship Diagram (ERD) is the first
step in database design; it is an important step for the database designers, users, analyst, and managers and in software engineering. In this paper, a methodology for detection of ambiguity in the ERD diagram is given. If ambiguity is found then apply various normalization techniques to remove it. The Normalization algorithms that are included are – 1NF, 2NF. This methodology is based on a predefined set of a heuristic rules that aims to extract the ambiguity of the ERD, then these rules are mapped into a database. A diagram generator automatically converts ERD into database schema's or table according to the rules of generations. The proposed methodology is explained by the examples to show how it can provide a mechanism for quick and easy way in extracting the Database Schemas. Key Words: Entity Relationship Diagram, entity, relationship, attribute
2. EXISTING SYSTEM
1. INTRODUCTION The Entity Relationship Diagram (ERD) shows that the real world consists of a collection of entities, the relationships between them, and the attributes that describe them. An entity is the object where we want to store data. A relationship defines the allowed connections between instances of entities [1]. Attribute is a characteristic common to all or most instances of a particular entity. Since the ER approach is easy to understand, a designer can focus on conceptual modeling of an organization, making decisions of what to use from entity sets, relationship sets and constraints. The ER-Diagram tool provides a mechanism for quickly and easily modeling data structures required by a software system. The ERD tool provides all the usual features of a data modeling tool and additionally provides reverse engineering. Thus, the user can create a database system quickly on a number of different target platforms without the need to write any Data Definition Language (DDL) type code. There are many essential concepts between ERD structure and English grammar structure [3] after analyzing the English sentences, so it is easy to make mapping between them. This paper describes a methodology, which is able to extract the ERD from a description of the application domain given © 2017, IRJET
|
in English sentences. Using ER-extractor it extracts entities relationships and attributes according to the heuristic rules it will be defined, as well as by matching between the structures of both English and ERD structures. After that, ER-generator depends on the predicate to convert the structure, which next pass the ER-descriptor to start to draw the ERD automatically depending on the rules. This paper proposed to define a methodology that provide a help to the database designer to automatically extract the ERD from a given English sentences. ERD is the first step in database design, it is also a simple technique described in a graphical way to decide which database fields, relationships and tables will be the base of any database. ERD is a good communication tool between users and who use the system during the identification of the user information requirements process.
Impact Factor value: 5.181
|
There is face-to-face interaction in traditional environment. The data normalization is introduced in this environment. DBMS is directly saved in the database whereas files locally act. Transactions are not possible in file systems; whereas various types of transactions are possible in DBMS like insert, view, delete, update etc. In DBMS, for accessing data tables i.e. schema is used whereas in file systems data is access is done through various files. In file systems to store different relationships in directories “File Manager” is used; whereas to store the relationships in the form of structural tables, a database manager i.e. administrator is used. Therefore, the data in database is more secure as compare to data in file systems. Various tools are available that allows database designers to draw and model the ER diagram. The given section provides an overview of the tool sets that are considered to define ER Diagrams for extending the ER Model. Summary and comparisons of all the modeling tools and ER drawings used in Chen like model is provided for ER definitions in Table 1. Comparison of tools is based on the criteria such that if the tool is open source or need to buy, draw or model or both, ISO 9001:2008 Certified Journal
|
Page 1323