1 / 11

XMI2SQL

XMI2SQL. Capstone Presentation Principal Investigator: Eric Hartford Committee Chair: Sam Chung, Ph.D. Committee Member: Isabelle Bichindaritz, Ph.D. Overview. Background Problem Solution Methodology Progress. Background. What do all these acronyms mean? XML

vaughn
Download Presentation

XMI2SQL

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. XMI2SQL Capstone Presentation Principal Investigator: Eric Hartford Committee Chair: Sam Chung, Ph.D. Committee Member: Isabelle Bichindaritz, Ph.D.

  2. Overview • Background • Problem • Solution • Methodology • Progress

  3. Background • What do all these acronyms mean? • XML • Extensible Markup Language • Standardized hierarchical data format • Maintained by World Wide Web Consortium (W3C) • UML • Unified Modeling Language • Standardized language for modeling object-oriented software • Maintained by Object Management Group (OMG)

  4. Background • CASE • Computer Aided Software Engineering • Software tools • Implement modeling languages like UML • Intended to make development less risky and more effective. • XMI • XML Metadata Interchange • Used to encode metadata, including UML diagrams. • Standard export format for many CASE tools. • Maintained by OMG

  5. Background • RDBMS • Relational Database Management System • database system • implements relational data model. • Example: • MS SQL Server • Oracle • MySQL • PostgreSQL • SQL • Structured Query Language • Standard language for interacting with RDBMS. • Maintained by • American National Standards Institute (ANSI) • International Organization for Standardization (ISO).

  6. Problem • Data Modeling • Created using CASE tools • Implementation-neutral • Graphical format • Proprietary format

  7. Problem • Once modeling is complete, how is the design transferred into implementation? • Manual transcription • Custom script • Proprietary automated database insertion • What is wrong with these methods? • Redesigning the wheel • Tightly coupled with software vendors • User has less freedom

  8. Solution • XMI2SQL • Input • XMI encoding of UML model of the data to be implemented • Output • List of SQL commands used to implement the model encoded by the XMI input file • Web Service Interface for cross platform compatibility

  9. Methodology • Analyze similar solutions • Determine / design data model encoding protocol • Determine or design conversion algorithm • Implement web service interface • Test and deploy

  10. Analyze Similar Solutions • UML2SQL • Inserts data directly into database from model. • Uses similar parsing / conversion algorithm to mine • Defines its own data modeling standard • I opted not to use it • I wanted to use Agile Data’s UML Profile (next slide) • I preferred to design my own algorithm • Author of UML2SQL expressed doubt as to viability of the idea.

  11. Data model encoding protocol • Two real standards at this point • Rational’s UML for Data Modeling Profile • Agile Data’s UML Profile for Data Modeling • I chose Agile Data’s profile. • Rational was recently bought out – I’m nervous about trusting IBM to upkeep Rational’s work. • I liked Agile Data’s casual style • Rational’s approach to Keys is not slick. It seems to be proprietary to Rose rather than oriented to OMG UML.

More Related