Developing applications

Development steps

An application composed of persistent classes is developed by:

· designing a package

· generating the physical model

· creating tables (DDL)

· clarifying tables

Designing a package

The first step is to design a package containing persistent classes. These classes are declared persistent by tagged values, which are used to specify the implementation of the persistence, by guiding the definition of the tables and keys used.

The "SQL" tab of the auxiliary window simplifies model annotation (for more details, please see "The auxiliary window and SQL Designer").

The tagged values provided by Objecteering SQL Designer are detailed in the "Annotating the model" chapter of this user guide, as well as in the annex corresponding to the RDBMS used.

Generating the physical mode

Objecteering SQL Designer is used to generate and maintain one or several physical models from a logical model.

Generating SQL code

The user interface is used to:

· generate creation and destruction scripts for all the package's tables, views, stored procedures and triggers

· visualize the scripts produced

· run the scripts

The database is then created. You can also use the free parts of SQL code to insert the first recordings into the database.

Adjusting tables

This is not yet the end of the application's life. The generator is used to create individual tables which correspond to a class or an association. The logical model can still be iteratively modified and the physical model associated with it updated.