Each location in your workspace contains instances which
belong to different entities. Each entity covers a specific aspect
of the application design.
The Data Structure entity
Data Structures describe all sets of data processed by
applications. These sets of data are represented by Segments or Tables.
The Segment entity
A Segment is a structured collection of Data Elements.
It must belong to a Data Structure. Segments are used by different
files. Some Segments represent the common part of the record (sort
criteria and keys) in a file, and other Segments represent the specific
part of the record in a file.
The Table entity
A Table is a set of 'n' occurrences of a Segment
and must belong to a Data Structure. A Table, described only once,
can be called into any entity that uses Tables (Programs, Segments,
Tables, Database Blocks). It is a set of Data Elements, grouped because
they are related to the same topic. Many of its characteristics are
similar to the Segment's.
The Data Element entity
The purpose of the Data Element entity is to identify and
describe all pieces of information used by the company applications.
The Database Block entity
Database Blocks enable you to describe databases both logically
and physically, taking into account the characteristics of certain
DBMSs.
The Macro entity
The purpose of a Macro is to standardize functions that
are common to several programs, or to several procedures of the same
program. A called Macro is a complement to the generation possibilities
of the system. A Macro is usually displayed in a program description
as if its lines had been directly entered by a programmer.
The Program entity
The purpose of the Program entity is to develop and implement
all the procedures defined in the detailed analysis phase.
The Report entity
The Report entity is used to define and describe a Report.
A Report is a document containing formatted data that results from
running a query and applying a form to it. A Report must be called
into a Program instance to be generated.
The Library entity
The purpose of the Library editor is to define and initialize
a Library.
The Dialog (standard or TUI client) entity
The purpose of the Dialog entity is to develop and generate
the online applications of the OnLine Systems Development function
or the TUI applications.
The Screen entity
A Screen belongs to a Dialog and is considered as a list
of fields.
The Server Dialog or Server entity
The purpose of these entities is to develop and generate
the server-side components of Pacbench C/S graphic or TUI applications.
The Logical View entity
A Logical View defines an information concept in your company
data system. It is constituted of a collection of elementary data,
which are Data Elements. It is conveyed between the server and the
client parts through the message that both parts exchange to communicate.
To be used in an eBusiness application, a Logical View must be called
in a Business Component. This Component makes the link between the
structure of the storage entities (Segments) and the structure of
the Logical View. As it is described at a logical level, the same
Logical View can be used by more than one Application.
Meta Entity/User Entity/Meta Data Aggregate concept
The Meta Entity helps you to create your own customized
concepts that the metamodel does not handle in a standard manner.
When a Meta Entity instance is defined and described, it is handled
as any other Pac instance. User Entities are instances of a given
Meta Entity.
The Text entity
The Text entity is used to document applications, throughout
their whole life cycle.