critique 2

ISSN: 2278 – 1323 International Journal of Advanced Research in Computer Engineering & Technology (IJARCET) Volume 2, No 5, May 2013 www.ijarcet.org 1816  Abstract - Normalization is a process of analyzing the given relational schemas based on the functional dependencies and using primary key to achieve minimum data redund ancy. Normalization is one of the key issues to be carried out manually in database design. This research work aims to resolve this issue by doing normalization of multiple databases automatically. This approach provides automatic normalizatio n of databases up to 3NF.The unique feature of the research work is automatic normalization and thereby saving time and reducing mind work. Index Terms —First Normal form, Second Normal form, Third Normal form. I. INTRODUCTION For developing any softwa re system, the database normalization helps to avoid data redundancy. If the relational database is used, it consumes time. If we missed out any constraint, we will face problems. While when we automate database, it is easy for normalizing data. The essenc e of data normalization is to split your data into several tables that will be connected to each other based on the data within them. By designing database tables carefully, we save space, minimize duplication, protect the data to ensure its consistency, a nd provide faster transactions by sending less data. Database normalization is the process of transforming data into well - formed or natural groupings such that one fact is stored in one place. Normalization generally simplifies the relations and reduces the danger of anomalies that may otherwise occur during manipulation of the relations in a relational database. Thus, the normalization procedure provides database designers with a formal framework for analyzing relation based on their keys and on the fun ctional dependencies among their attributes. A database management system (DBMS) is computer software that designed for creating and maintaining databases and allows users to retrieve information from that database.

MS Access, FoxPro, Dbase are some of the examples for database management system. Relational database management system (RDBMS) is a type of DBMS in which the database is organized and accessed according to the relationships between data values.

It is based on the relational model. The e xamples for relational database model are Oracle, DB2 and MS SQL Server. The database has to be maintained to avoid redundancy, to eliminate duplicate data. Now a day all the normalization processes for tables are carried out manually.

The normal form of a relation refers to the highest normal form condition that it meets, and hence indicates the degree to which it has been normalized. Three normal forms called first (1NF), second (2NF), and third (3NF) normal forms were initially proposed. This section1.0 describes the introduction of the proposed work. Section2.0 focuses on literature survey.

Section 3.0 describes the proposed system for automatic normalization. Section 4.0 focuses on the result of the proposed system. A KNOWLEDGE BASED APPROACH FOR AUTOMATIC DATABASE NORMALIZATION G.Sunitha, Dr.A.Jaya ISSN: 2278 – 1323 International Journal of Advanced Research in Computer Engineering & Technology (IJARCET) Volume 2, No 5, May 2013 1817 www.ijarcet.org II. LITERATURE SURVEY This sec tion focus on literature survey of the research work. Sherry verma, ”Comparing manual and automatic normalization techniques for relational database”, [1] proposed the Comparing manual and automatic normalization techniques for relational database, based on the dependency matrix and approach primary key to generate automatically identified the final table . RadhaKrishna, Rajuvelpula,v. sravya,”A web based relational database design tool to perform normalization”, [2] the authors discussed a we b based relational database design tool to perform normalization. To developed an interactive relational database design tool to make the normalization process. Amir Hassan bahmani, MahmoudNaghibzadeh, “Automatic database normalization and prima ry key generation”, [3] the authors proposed an approach for automatic database normalization and primary key generation. In discussed an automatic distinguish one primary key for every final table which is generated. The problem is to normalize the databa se tables automatically. In the current normalization process, even first normal form, second normal form and third normal forms are difficult by doing automatically. Abbasifard, Rahgozar, Pournemati, “Using automated database reverse engineering for database integration”, [4] the authors approach for automated DBRE and data normalization for integrating systems. Along with normalization process we determine constraint rules. The suggested model provides a schema with complete semantics of legacy d atabases. Akehurst, Bordbar, Rodgers, “Automatic normalization via meta modeling”, [5] the authors proposed an approach automatic normalization via meta modeling, by using a declarative approach to the specification of the normalization rules and a precisely defined transformation, over a meta -model of a database system design language. III.PROPOSED SYSTEM FOR AUTOMATIC NORMALIZATION The figure 1 shows the architecture diagram for automatic database normalization. Figure 1 architectural diagram for automatic database Normalization The components involved in the system and the integration of components that work simultaneously. The proposed system is to make the normalization process automatically by giving some kind of human knowledge to the system to do the normalization process in an effective way. To overcome the limitations of existing system, knowledge based approach is proposed to automate the normalization process of the tables. The goal of proposed system is to do the normalization processes up to third normal form with inclusion of all promising constraints that are needed to make tables as perfect.  Easy to maintain the record, and identified the record easily.  The database has to be maintained and avoid redundancy, to eliminate duplicate data. First Normal Form Figure 2 shows the flow chart for 1NF. During the first normalization’s process , each and every fields of table are examined whether it has atomic values or composite values in every record . If null value occurs in table then it would be removed from table by entering corresponding data type value. The redundancy of records is also monitored by the implementation of suitable structural query language. If the replicas of records are found t hen those records are smoothly removed by this system. ISSN: 2278 – 1323 International Journal of Advanced Research in Computer Engineering & Technology (IJARCET) Volume 2, No 5, May 2013 www.ijarcet.org 1818 Figure 2 Flow chart for 1NF Second Normal Form Figure 3 shows the diagram for second normal form.The second normalization part to satisfy the functional dependency. The functional dependency is defined, as every field in a table should be connected with primary key or candidate key of that table. . If any of the non -key fields is connected or logically grouped with a part of candidate key or a part of primary key then it is known as partial functional dependency. The partial dependency should not occur in the table. So in the second normalization part, partial dependency is going to be removed. Figure 3 Flow chart for 2 NF Third Normal Form Figure 4 shows the diagram for third normal form. The third normalization part to satisfy the transitive dependency is removed from the table by extracting the independent columns in the table. It checks the corresponding and all the required constraint s in the flow of streams. Figure 4 Flow chart for 3 NF ISSN: 2278 – 1323 International Journal of Advanced Research in Computer Engineering & Technology (IJARCET) Volume 2, No 5, May 2013 1819 www.ijarcet.org Figure 5 Unnormalized Table IV. RESULTS This research work automates the normalization process that leads to time efficiency. If the result contains more than one table, all these normalized tables are automatically connected with main table. This research work is developed fully with user interface that is the interaction between system and user who develops the system. The given table is normalized and if required the tables are split into two or more tables and foreign key is automatically assigned to tables to create relationships among the normalized tables. Figure 6. Result of the proposed system V.CONCLUSION AND FUTURE ENCHANGEMENT S This research work performed 1 st normal form, 2 nd normal form and 3 rd normal form. These phases are used to normalize the database tables automatically. The status of the research work was completed with the 1 st normal form. Going forward the norma lization of 2 nd normal form and 3 rd normal form will be done. The future enhancements that can be done in system are as follows normalization can be extended up to fifth normal form. REFERENCE [1] Amir Hassan Bahmani, Mahmoud Naghibzadeh, Behnam B ahmani “An Automatic Database Normalization – Primary Key Generation”, IEEE(2008). [2] Sherry Verma , “Comparing manual and automatic normalization techniques for relational database”.

IJREAS ,February 2012. [3] Abbasifard, Rahgozar, Pournemati “Using aut omated database reverse engineering for database integration”(2006). [4] Akehurst, Bordbar, Rodgers “Automatic normalization via meta modeling”. [5] Radha Krishna, Rajuvelpula, sravya “A web based relational database design tool to perform normalization”(2 011).IEEE Journal. G.Sunitha, Final Year MCA, Department of Computer Application, B. s. Abdur Rahman University. Dr.A. Jaya , Professor , Department of Computer Application, B. S. Abdur Rahman University.