Modeling the Application

Modeling is an activity in which you create abstract development objects that can be reused by other objects during development. Modeled objects are used to represent the application data, centralize business logic, define default behavior, and enforce consistency.

By modeling the data and common business logic, it easier to construct components and to maintain the application, because changes made in the modeled development objects are inherited by the components that use them.

Modeled Development Objects include:

Modeled entities and their child objects—modeled fields, keys, and relationships. These objects primarily describe the application data and define default behavior for retrieving and storing the data, but they can also be used to define common user interface controls. They are reused in components to create component entities, which inherit from the modeled entities.
Modeled properties for selected field and entity property values. These properties determine how data is stored, entered, and displayed. They are defined in homogeneous libraries and are reused in Entity and Field objects.
For example, you can define a library of Modeled Field Layouts that determine the display format for specific types of data, such as dates, telephone numbers, email addresses, or currency.
IncludeScripts, which are fragments of ProcScript, large or small, that can be included in script modules. They enable you to centralize commonly-used code patterns, and even to generate components or ProcScript modules. IncludeScript objects are defined in libraries and resolved during compilation.
Snippets, which are named fragments of code or text that you can insert into your application script or layout to speed development. Uniface delivers a default set templates and snippet libraries which are loaded when you start the Uniface IDE for the first time