ترجمه مقاله نقش ضروری ارتباطات 6G با چشم انداز صنعت 4.0
- مبلغ: ۸۶,۰۰۰ تومان
ترجمه مقاله پایداری توسعه شهری، تعدیل ساختار صنعتی و کارایی کاربری زمین
- مبلغ: ۹۱,۰۰۰ تومان
In 1999, the SQL standard version presented new features to manipulate objects in relational database which has since been called Object-Relational Database (ORDB). Nowadays, many Object-Relational Database Management Systems (ORDBMS) offer resources to manipulate object in database. However, for these resources to become really utilized in corporate environment, it is necessary, among other things, to have CASE tools to aid in object-relational database design. An extension made in ArgoUML tool that permits developers to build graphics schemas to ORDBs is presented. These schemas can be generated using an ORDB profile presented here in. This profile is an extension of the UML class diagram and contains elements to represent the new resources to manipulate object in databases. The tool maps the graphic schema to SQL:2003 code and SQL code to Oracle dialect.
I. INTRODUCTION
Nowadays, there are many CASE (Computer-Aided Software Engineering) tools to aid generation and maintenance of relational databases. Erwin, DBDesigner, DB-Main and others are some of the examples. Such tools offer resources to create graphic models and have an option for the automatic generation of SQL (Structured Query Language) code for some Database Management Systems (DBMS) (eg. Oracle, PostgreSQL, etc.). It is possible to divide tools into two categories: the first supports generation Entity-Relationship Model (ERM) [8] and the second supports generation of table models. In the first case, the developer creates a conceptual model using the tool which offers resource for mapping from that model to the table, in the other words, the tool generates a logical model through generation of the appropriated SQL code to the DBMS chosen. In the latter, the developer creates a model of table, that is, a graphic logical model, which is translated into the appropriated SQL code for the DBMS chosen. In both cases, the tool generates the SQL code automatically. This is important because the SQL code written by the developers can contain more errors and depends on the developers’ knowledge. The scenario gets worse for cases in which code generation for more DBMS ones is necessary.
VI. CONCLUSIONS AND FUTURE WORK
An extension to ArgoUML CASE tool to generate logical models to ORDBMS is proposed. The objective is to increase the use of ORDB. Experience has shown that the existence of tools that support technologies broadens their use. The new modules added to ArgoUML use the Graphic Logical Model to generate, respectively, SQL code in Oracle 11g dialect and SQL:2003 dialect from graphic logical schema. The tool introduced shows that our proposal is viable. However, to use it in real projects, it is necessary to make improvements such as new modules connecting to other SGBDs that offer support to objects besides changes in the tool interface to better represent the new resources and the automatic generation of logical schemas to ORDB as from a conceptual model (UML classes diagram) (Figure 1).