![]() |
Data
Architect Professional database modeling |
![]() |
Options are disabled when they are not relevant to the current state of the application. |
![]() |
The tool-bar is a collection of dock-windows. Dock-windows can be moved or hidden. Use the Window menu option to make a hidden dock-window visible. |
![]() |
Most Browser items have a context popup menu which can be invoked by <right-clicking> the item. |
![]() |
Many of the output messages contain information about the source of the message - <clicking> on such a message will usually bring the source into focus and <double-clicking> the message will usually invoke the sources properties dialog. |
![]() |
One way to create a document under a Project is to <right-click> the Project in the Browser dock-window. This invokes the Projects popup menu which includes options for creating/adding documents to the Project. |
Model Type |
Definition |
|
![]() |
Logical Model |
Represents the logical system -
that is the system without regard to any physical implementation. This
is created relatively early in the System Development Life Cycle (SDLC)
- typically early in the Design Phase. A Data Architect is the typical
person(s) who creates Logical Models but because it is abstracted from
implementation details it can be created by someone with less technical
and more business skills. |
![]() |
Physical Model |
Represents the physical
implementation of the database. This is created in the later stages of
the Design Phase of the SDLC - after the Logical Model is complete and
after the database type has been selected. A Data Architect or someone
with good design skills and a high degree of undertanding with
regard to the target database type creates the Physical Model. |
![]() |
Diagram |
Data Architect may be used to
create generic, free-form diagrams. |
![]() |
SQL File |
SQL files may be edited using the Advanced SQL Editor (ASE) embedded in Data Architect. This editor includes syntax highlighting for SQL and supports submitting SQL to the database and displaying any results. The results can be exported/displayed in a variety of formats such as; delimited, html, text boxed, and graphical grid. |
![]() |
A
Physical Model must always represent the design in the Logical Model.
It is ok for the Physical Model to use more optimal column data types
(although only when absolutely required) or to even contain more
entities/tables to improve the efficiency of data access and storage.
But it should never contradict the Logical Model and the intention
detailed there. |