Some developers like to have a clear separation between the logical analysis and physical design of an application system. SQL Developer Data Modeler supports this separation of tasks and also supports the synchronization of metadata between these. This means that you can start new application development with a logical model without needing to think about the physical implementation details. Once you have completed the analysis, you can then transform the entities to tables and work on the physical implementation. SQL Developer Data Modeler also allows you to work on the relational model with its tables, views, and constraints without needing to consider the physical detail. Without the physical detail, you can create a relational model that is database-agnostic. Then, for a single relational model, you can create multiple physical implementations and generate different DDL for each of these.
In this section, we'll start with a logical model, transform this...