SQL2XMI: Reverse engineering of UML-ER diagrams from relational database schemas

Proceedings - Working Conference on Reverse Engineering, WCRE

Volumn , Issue , 2008, Pages 187-191

  Alalfi, Manar H ^a   Cordy, James R ^a   Dean, Thomas R ^a  

^a QUEEN S UNIVERSITY   (Canada)

Author keywords

[No Author keywords available]

Indexed keywords

APPLICATIONS; ELECTRIC RESISTANCE; MARKUP LANGUAGES; REENGINEERING; REVERSE ENGINEERING; SOFTWARE ENGINEERING; UNIFIED MODELING LANGUAGE;

APPLICATION MODELS; DATA MODELS; ER DIAGRAMS; ER MODELS; OPEN STANDARDS; RELATIONAL DATABASES; SOFTWARE DEVELOPMENT PROCESSES; SOURCE TRANSFORMATIONS;

MATHEMATICAL MODELS;

EID: 57849140296     PISSN: 10951350     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/WCRE.2008.30     Document Type: Conference Paper

References (20)

1. R. Abu-Hamdeh, J. R. Cordy, and T. P. Martin. Schema translation using structural transformation. In CASCON, pages 202-215, 1994.
2. S. Ambler. A UML profile for data modeling. www.agiledata.org: Techniques for Successful Evolutionary/ Agile Database Development, 2006.
3. C. W. Bachman. Data structure diagrams. SIGMIS Database, 1(2):4-10, 1969.
4. G. Canfora, A. Cimitile, A. De Lucia, and G. A. Di Lucca. Decomposing legacy systems into objects: an eclectic approach. Inf. & Soft. Tech., 43(6):401-412, 2001.
5. D. T. Chang. Integrating Rational Software Architect with Rational Data Architect. IBM developerWorks, 2007.
6. P. P.-S. Chen. The entity-relationship model - toward a unified view of data. ACM Trans. Datab. Syst., 1(1):9-36, 1976.
7. S. Chung and E. Hartford. Bridging the gap between data models and implementations: XMI2SQL. In AICT/ICIW, page 201, 2006.
8. J. R. Cordy. The TXL source transformation language. Sci. Comput. Program., 61(3):190-210, 2006.
9. G. A. Di Lucca, A. R. Fasolino, and U. de Carlini. Recovering class diagrams from data-intensive legacy systems. In ICSM, pages 52-63, 2000.
10. Federal Information Processing Standards. Publication 184, Integration Definition for Information Modeling (IDEFIX), http://www.itl.nist.gov/ fipspubs/idef1x.doc.
11. D. Gornik. UML data modeling profile. Technical report, IBM Rational Software Whitepaper TP 162 05/02, 2003.
12. P. V. Gorp. UML profile for data modeling, http://www.fots. ua.ac.be/~pvgorp/research/datamodelingprofile/, 2007.
13. No Magic, Inc. MagicDraw UML, http://www.magicdraw.com.
14. Object Management Group (OMG). Request For Proposal Information Management Metamodel (IMM), http://www.omg.org/docs/ab/05-12-02.pdf. Technical report, 2005.
15. Object Management Group (OMG). OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2, http://www.omg.org/docs/formal/07-11-01.pdf. Technical report, 2007.
16. Object Management Group (OMG). UML Profile Catalog, http://www.omg. org/technology/documents/profile_catalog.htm. Technical report, 2008.
17. W. J. Premerlani and M. R. Blaha. An approach for reverse engineering of relational databases. Commun. ACM, 37(5):42-49, 134, 1994.
18. D. Silingas and S. Kaukenas. Applying UML for relational data modeling, http://www.magicdraw.com/files/articles/ Sep04%20Applying%20UML%20for%20Relational%20Data%20Modeling.htm, 2004.
19. T. J. Teorey, D. Yang, and J. P. Fry. A logical design methodology for relational databases using the extended entity-relationship model. ACM Comput. Surv., 18(2):197-222, 1986.
20. H. Yang and W. C. Chu. Acquisition of entity relationship models for maintenance-dealing with data intensive programs in a transformation system. J. Inf. Sci. Eng., 15(2):173-198, 1999.