Monday, 22 August 2011 00:00

Data Modeling - From Conceptual Model to DBMS

Written by
Rate this item
(5 votes)
Enterprise Architect supports comprehensive functionality for modeling database structures. This paper covers the core features for data modeling over the full lifecycle of an application.

The initial development of a system typically involves numerous levels of abstraction.  Database modeling traditionally includes a well established three tiered approach:

  1. Conceptual Model
  2. Logical Model
  3. Physical Model

This paper covers creating these models, interconnecting models on these levels, using MDA transforms for generating the Physical model from the Logical model, along with generating schema scripts for loading to your DBMS. It also covers the features for remodeling legacy systems including Reverse Engineering an existing DBMS structure.

Read 14944 times Last modified on Wednesday, 10 April 2013 05:50
sparxsystems

Sparx Systems


99 Albert Street
Creswick,
Victoria
3363
Australia
P: +61 3 5345 1140
F: +61 3 5345 1104
 
Sparx Systems specializes in high performance and scalable visual modeling tools for the planning, design and construction of software intensive systems. A Contributing Member of the Object Management Group (OMG), Sparx Systems is committed to realizing the potential of model-driven development based on open standards. The company’s flagship product, Enterprise Architect, has received numerous accolades since its commercial release in August, 2000. Enterprise Architect is the design tool of choice for over 740,000 registered users worldwide.

community.sparxsystems.com

2 comments

  • Comment Link Guillaume Wednesday, 06 September 2017 12:20 posted by Guillaume

    Interesting and useful document with a suggested definition on the Conceptual, Logical and Physical models.
    I have worked with conceptual data models coming from standard consortiums publishing them via the RAS. Conceptual models were used when building the application "logical" data model for compliancy & traceability purposes, whilst taking into account existing Physical models i.e. reverse-engineered databased.

    It would be useful to integrate the documented Data Dictionary search in the Database Engineering built-in searches.

  • Comment Link Courvoisier Monday, 18 November 2013 14:24 posted by Courvoisier

    Hi,
    Now I have a point from where I can begin.
    I have nowadays only the trial version of Ultimate for a project, and the support profesionaly helped me with this article, which relate others, so I can contine my project. I formally learnt with this document that there is no Primary key in the Lgocial Model. Thanks.

Login to post comments