The Adelia object types are described below:
Access
Access path to a logical entity.
Application area
Functional subunit of an information system.
Basic graphical object
Basic graphical object which is used during the Visual Adelia window layout design.
Conceptual entity
Collection of properties presenting a particular interest for the company and having its own and identifiable existence. An entity is identified by one or more properties known as keys.
Conceptual property
The smallest element of information handled by the organization. Elementary part of the information system.
Correction
Work space in which only the object assigned to it can be modified.
Adelia object managed only in a correction environment.
Data type
Data class defining a set of characteristics common to properties.
Folder
A documentation folder consists of the definition, description and documentation of objects. A folder is divided into chapters and subchapters.
IBM logical property
IBM logical field.
Installation
Group of programs that together enable an application to be installed (an application = a set of programs).
Join entity
Logical view of a database which implicates several entities.
Logical entity
Set of logical properties.
Logical property
Property coming from the Conceptual Model or created at the Logical level.
Logical server
Abstract identification of the database for Visual Adelia programs.
Management rule
Conceptual, organizational or technical translation of the objectives selected and the constraints accepted by the company. It involves processes (action rule) or data (calculation rule, etc.).
Personalized graphical object
Graphical object created by customizing a basic graphical object's properties and which is used during the layout design of Visual Adelia windows.
Program
Set of processes resulting from the generation of a task at the physical level.
Program template
Standard sequencing of Adelia instructions.
Relationship
Semantic link between several conceptual entities independent of any processing. Its existence is conditioned by the existence of several entities.
Report
Report image which can be made up of several formats.
Report template
Set of characteristics common to reports (positioning of fields, division into formats, etc).
Screen standard
Set of characteristics common to screen layouts (positioning of fields, display attributes, function key descriptions, etc.).
Software engineer
Individual or group of individuals in charge of one or more application areas of an information system.
Task
Elementary processing unit complying with the "3 units rule": place, action and time.
Transaction
Screen image that can consist of several formats.
Transaction template
Set of characteristics common to transactions (screen size, function keys definition, division into formats, etc.).