Hierarchical to Relational Schema Conversion via XMI and XSLT

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database management systems lack efficient tools for converting hierarchical database schemas into functionally equivalent relational schemas, limiting flexibility and compatibility with Relational Modeling Tools.

Innovation Solution

The system imports the database schema from a description file, translates it into an XMI file using the Common Warehouse Metamodel, and then transforms it into a relational schema using an XSLT stylesheet, enabling management with relational modeling tools.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If hierarchical database schemas are used, then database management capabilities are maintained, but compatibility with Relational Modeling Tools is lost

Engineering Contradiction:
Improvecompatibility with Relational Modeling ToolsVSAvoidschema conversion process
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary conversion system that translates hierarchical database schemas into relational schemas. This intermediary process enables compatibility with Relational Modeling Tools while preserving the original hierarchical database capabilities, resolving the contradiction between maintaining hierarchical database management and achieving compatibility with relational tools.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If schema conversion tools are added, then flexibility and compatibility are improved, but system complexity increases

Engineering Contradiction:
Improvedatabase management flexibilityVSAvoidconversion system structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The conversion system is designed with multi-functionality to handle various hierarchical database types and convert them to relational schemas. By making the conversion tool universal and capable of handling multiple scenarios, the system achieves high flexibility without proportionally increasing complexity, as the same core conversion mechanism serves multiple purposes.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Productivity

If manual conversion processes are used, then conversion accuracy can be maintained, but conversion time increases

Engineering Contradiction:
Improveschema conversion speedVSAvoidconversion accuracy
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The conversion system employs self-service mechanisms where the hierarchical schema automatically provides metadata and structural information that the conversion process uses to generate accurate relational schemas. This self-describing capability of the source schema enables automated conversion with high accuracy, eliminating the need for manual intervention while maintaining conversion quality.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7599947B1Method and system for converting hierarchical database schemas into relational database schemas
Publication Date: 2009.10.06 UNISYS CORP
  • US7599947B1 patent drawing
  • US7599947B1 patent drawing
  • US7599947B1 patent drawing

AI summary

A specialized server holding a hierarchical database works with a Graphical User Interface to transform a hierarchical schema by utilizing an XMI file which is used with a modeling tool to develop a relational schema for display and use in a relational database in the Graphical User Interface.