A Proposal for Constructing Relational Database from Class Diagram

Abstract

Database system is important to ensure the data can be stored, updated and retrieved for future use. Data modelling using the Entity Relationship Model has been introduced more than thirty years. However, designing a good database system is still an attractive issue particularly in system analysis and design because of very hard to do consistency checking between system design and database design. In this paper, a proposal for designing a relational database system based on Object Oriented Analysis and Design is presented. The database system is created by the schema table that extract from class diagram. The rules applying in this paper is following the object oriented concept. It is based on the relationships among the classes, multiplicity, attributes name, class name, data type and the behaviours of the classes. Beside that the user is required to insert record to accomplish a good designing the schema tables to avoid redundancy data. Finally, an automatic editor called CDGeST is proposed in order to automate the process.

Comparative Analysis of Data Redundancy and Execution Time between Relational and Object-Oriented Schema Table

“…The steps in object-oriented technique began by first translating the ER diagram into a class diagram. The Visual Paradigm program [10] supports generating class diagram from existing ER diagrams. This program mapped the entities and relationships into the corresponding classes and associations.…”

“…From the table, the database design using object-oriented technique produced higher data redundancy in the Department attribute. This is because the tables in the Database Course were transferred from class diagram [10]. The class diagram in object-oriented refers to the entities in the system requirements.…”

“…In the object-oriented approach, the database system is created by the schema table generated from the class diagrams. The rules applied to adhere to the object-oriented concept, which is based on the relationships among the classes, multiplicity, attributes name, class name, data type and the behaviours of the classes [6].…”