11 Facts About Oracle Designer

Oracle Designer was Oracle's CASE tool for designing an information system and generating it.

Oracle Designer CASE was based on Oracle Designer corporations "Computer Aided Software Engineering" method .

CASE Method was in turn developed by Oracle Designer Consulting UK in the 1980's based on modelling techniques such as Richard Barker et al's Entity Relationship Modelling.

The design philosophy behind Oracle Designer and competing tools in the 80's and 90's was the Three-schema-architecture that separated an external schema, logical schema and internal schema.

Oracle Designer was based on a well thought out set of concepts that suited the types of systems being developed from the 1980's to the mid 2000's.

Oracle Designer was initially based around a database that held design models, called a repository, not to be confused with a modern GIT repository .

Later the Oracle Designer Repository included models and code, but always stored in an Oracle Database.

Tools that made up Oracle Designer each had their view on the repository, with which to create and edit models, generate more detailed models, generate code or inspect the quality of a model.

Early users of Oracle Designer tended to focus on modelling and generating the database structures and often neglected the function model and modules.

The architecture of Oracle Designer Developer was not well suited to the needs and technologies of the internet because it would have required users on the internet to install some kind of application and then directly connect to a database.

Oracle Designer Developer was intended for, and very good at administrative applications that are used for data entry by enterprise employees.