Consultor Eletrônico

Status: Unverified

GOAL:

RoundTable Glossary

FACT(s) (Environment):

RoundTable 9.1x

FIX:

Alias
Defines an alternate name for a database or object.

Application Group
A group of related objects that perform interdependent activities within a software application.

Application Group Directory
A subdirectory in which objects belonging to an application group are stored together.

Change History View
A list of each change made to a specified object in the current workspace. The Change History View is available in the Roundtable Tabletop.

Component Directory Structure
A common way to arrange directory structures in an application system is by the types of components found in the system. This organization is typical when many discrete components are reused across functional boundaries in a software application system.

Config Folder
The Config folder contains information about how Roundtable should process an object in a workspace. The Config folder is found on the TableTop.

Configuration
A map of the contents of your application at a given time.

Configuration Hierarchy
A map of the contents of your application that usually corresponds closely to the architecture of your system.

Configuration Level
Application software systems under configuration control are mapped into a configuration hierarchy. The configuration level refers to the depth of the hierarchical tree where an object is found.

CRC
Cycle redundancy check. This is a calculated value that is generally unique for any given piece of data. Roundtable calculates a CRC value for each file loaded into the repository. When required, this CRC value can be compared with a CRC calculation on a file at the operating system level to determine if the repository file and OS file are the same.

Cross Reference
A cross reference or Xref is generated for many kinds of relationships among objects in a workspace. These cross references are generated when a full compile is performed on a compilable object. Database schema objects are also cross referenced automatically by the system.

Cyclical Redundancy Check
Cycle redundancy check. This is a calculated value that is generally unique for any given piece of data. Roundtable calculates a CRC value for each file loaded into the repository. When required, this CRC value can be compared with a CRC calculation on a file at the operating system level to determine if the repository file and OS file are the same.

Data Type
The PROGRESS data type determines what kind of data can be stored in a variable or database field.

Deployment
Roundtable manages the process of packaging a release of an application system from a workspace for delivery to a remote site. The process of packaging the release is called the deployment process and the update package created is called a deployment.

DOC
A DOC object normally contains documentation and is always stored in a directory called doc off of the objects workspace module directory. You can also use the PCODE object to store documentation objects. Check out a DOC object to modify the document it contains.

Domains
The idea behind a domain is that you create a single definition that is used in a number of different places. For example, you might define a single PFIELD object called Address and use this field definition in a number of different tables, or even many times in the same table.

Event
Each completed change that results in a change to the contents of a workspace is recorded as a sequential event in the workspace event history.

Field Assignment
A PFIELD object contains attributes that describe a field (column) and are referenced by field assignments in PFILE objects. The collection of attributes in the PFIELD object and PFILE field assignment completely def.ine a field in a table. A field assignment contains the product module and name of the PFIELD object, local field name, field order, mandatory status, and triggers of the field.

Fields View
In the Fields View a list of each field defined in a selected table appears in the browse on the TableTop. This view is reached by selecting a PFILE object and then choosing the Expand button.

Group Access
You define a collection of security privileges and name them with a group access code. You assign one or more group access codes to one or more users in a workspace. Security privileges accumulate based on each group access code assigned to a user in a workspace.

Group Access Code
A code that identifies a set of security privileges that can be enjoyed within the Roundtable environment. You create access groups and then specify what security privileges belong to the group. You can then associate one or more access groups with one or more users by workspace.

Group Code
User-defined values entered when the user defines objects. The group code is used to sort the objects in the object browse table.

Group Directories
Roundtable checks out objects to a task directory where the programmer modifies them. The changes are not seen by others until the programmer executes the Update Group/Public Source option, which copies the modified objects into a group directory. Other programmers might choose to see the changes by attaching one of their tasks to the group. The last completed version of the objects remain in the workspace directory.

Indexes View
In the Indexes View, a list of each index defined in a selected table appears in the browse on the TableTop. This view is reached by selecting a PFILE object and then choosing the Expand button. The definition of the index appears in the Index folder.

Informal Xref View
In the Informal Xref View, a list of each object that uses a specified informal object appears in the browse on the TableTop. Informal objects include shared variables, shared workfiles, etc.

Module Load
A Roundtable utility used to search for objects in the operating system directory associated with a selected workspace module. The user is able to quickly create new objects for the new source code found.

Module View
In the Module View, a list of each object included in a specified workspace module appears in the browse on the TableTop. You change the currently selected workspace module by using the Module drop-down list on the TableTop.

Note Folder
A folder, on the TableTop, that displays a brief description of the changes made to the currently selected object version. You are prompted to enter these notes each time you finish editing an object.

Object Types
All workspaces are comprised of collections of Roundtable objects. These objects are of one of the following types:
PCODE: A collection of optimized files whose purpose is specified by assigned subtype
PFIELD: A database schema definition for a field
PFILE: A database schema definition for a table
PDBASE: A database schema definition for a database
DOC: A special type used for documentation objects

Object Version
Object versions are created each time you check in an object. Object versions are stored in the repository. You can see a list of all versions of an object by selecting the object in a workspace and then choosing View®Object Version List View. Object versions are permanent. They are never deleted from the repository.

Orphan
When the same object is checked out in two workspaces at the same time, an object version orphan is created. The term indicates that the changes made in one of the object versions will be lost in some future promotion process among workspaces. For instance, suppose you have a de.velopment and test workspace, that you check out the same object in both workspaces, and then you check in both objects. If you then import the object from the development workspace into the test workspace, the object version imported from development replaces the object version created in test. The changes made in test are lost. Roundtable warns you
of object orphan conditions wherever possible.

Orphan Change Management
When the same object is checked out in two workspaces at the same time, an object version orphan is created. The term indicates that the changes made in one of the object versions will be lost in some future promotion process among workspaces. For instance, suppose you have a development and test workspace, that you check out the same object in both workspaces, and then check in both objects. If you then import the object from the development workspace into the test workspace, the object version imported from development replaces the object version created in test. The changes made in test are lost. Roundtable warns you of object orphan conditions wherever possible.

Partner Site
A partner site is a Roundtable installation that receives repository information from another Roundtable installation. You perform a partner site deployment at the sending site and a partner site load at the receiving site to move repository information among sites. Each site must have a different site number.

PCODE
An object that encapsulates up to ten files that together define a system component. These system components can contain textual or binary data, and you assign a subtype code to each PCODE object to describe these files. The first nine of these files are called parts and their attributes are specified in the subtype definition. The tenth file is the .WRX file created by the UIB for procedures that contain OCX controls. The .WRX file is managed automatically by Roundtable and need not be explicitly defined by the user. We strongly recommend that the .WRX file have the same name as the UIB managed procedure. Check out a
PCODE object when you need to modify the system component it encapsulates.

PDBASE
An object that contains the topmost components of a database schema definition. PDBASE (database) objects record a list of table assignments that relate PFILE objects with the PDBASE object. Check out a PDBASE object when you need to add, delete, or change the name of a database table or sequence.

PFIELD
A PFIELD object contains attributes that describe a field (column) and are referenced by field assignments in PFILE objects. The collection of attributes in the PFIELD object and PFILE field assignment completely define a field in a table. A field assignment contains the product module and name of the PFIELD object, local field name, field order, mandatory status, and triggers of the field. The PFIELD object contains the remainder of attributes that define a field in a table.

PFILE
A PFILE object contains attributes that describe a table. PFILE objects are referenced by table assignments in PDBASE objects. The collection of attributes in the PFILE object and PDBASE table assignment completely define a database table. Check out a PFILE object when you need to add, delete, or change a PFILE assignment or an index definition.

Product
Roundtable provides three logical levels of configuration hierarchy:
product, product module, and object. Products own one or more product modules, product modules own one or more objects. This hierarchy provides a logical view of an application system and is useful for implementing promotion and deployment strategies for the application system.

Product Module
Roundtable provides three logical levels of configuration hierarchy:
product, product module, and object. Products own one or more product modules, product modules own one or mor.e objects. This hierarchy provides a logical view of an application system and is useful for implementing promotion and deployment strategies for the application system.

PROGRESS ADE
Application Development Environment.

PROGRESS UIB
User Interface Builder.

Promote
The process of importing objects from one or more source workspaces into a target workspace.

PROPATH
A comma-delimited string that contains the operating system directory paths that will be searched by PROGRESS for source code during the compile process.

R-code
PROGRESS-compiled procedures have an extension of .r. Any compiled PROGRESS procedure is referred to as r-code.

Recent View
In the Recent View, the object browse table displays a history of the navigation you have performed in a workspace through the selection of various views on various objects. You can double click on a row in the recent view list and Roundtable will re-establish that view for you.

Release
A release is a record of a specific event number in a workspace. It is used to re-create the exact contents of the workspace configuration that existed as of that event for purposes of promotion and deployment from a workspace. A release labels a version of a workspace.

Release Record
Each release record has a sequential release number that uniquely identifies it in the workspace. Release records also contain a text label that describes the configuration of the system at the time the release record was created. For example, release number 23 from the Test workspace might have the descriptive label "Beta Release 2.1a".

Remote Site
Sites that receive updates packaged by Roundtable are called remote sites.

Run-time, Query, or Development
PROGRESS products types.

S-code
PROGRESS source code.

Share Status
Checked out objects have a share status of Task, Public, Group, or Central. The share status controls where the object is edited and the visibility of the edits on the object to the rest of the users in a workspace.

Source Workspace
The promotion of code through a development cycle is defined by assigning source workspaces to each workspace in the system. The import process build searches each specified source workspace for objects that should be imported into a selected target workspace. For instance, if you have a development workspace and a testing workspace, you specify that the development workspace is a source workspace for the testing workspace. The import process pulls completed object versions included in the latest source workspace release level into the target workspace.

Spec Folder
The Spec folder displays object version information about the currently selected object. This information includes the product module, version level, subtype, task number, update status, object group, and synopsis.

Subtype
Subtypes control the naming, management, creation, and storage of PCODE objects. Up to nine file parts are used to define a system component. These system components can contain textual or binary data. In addition to file parts, you specify edit, naming, and procedure generation services for a subtype, as required.

Table Trigger
A database table might have a table trigger. The trigger specifies the name of a procedure file to execute when a trigger condition occurs. The trigger conditions include: FIND, CREATE, WRITE, and DELETE.

Tables View
The Tables View lists each table assignment in a PDBASE object in the browse on the TableTop. You reach the Tables View by selecting a PDBASE object and then choosing the Expand button.

Target Workspace
A term used to describe the destination of objects in an import process. The import process is executed in t.he target workspace, and objects are imported into it from one or more source workspaces.

Task Directories
You create Task directories where checked out objects are copied. This makes it possible to isolate your work from others until it is ready to be checked in or promoted for review into the group or central workspace directories. Use of task directories is optional.

Task Folder
The Task folder displays a brief description of the task under which the currently selected object was created.

Task Management
The management of units of work performed on the application system managed by Roundtable. All work done on individual objects in the Roundtable system is performed under a task. Usually, managers assign tasks and programmers check out one or more objects under the task. Completing a task checks in all objects that were checked out under the task. Various task reports are available.

Task View
The Task View lists each object associated with the current task in the browse on the TableTop. Only current work in process tasks can be viewed in this manner.

Update Status
An attribute of an object's assignment to a workspace. The update status attribute can have a value of Current, Modified, or New. This update status attribute is one of the attributes used to determine if the object needs to be compiled or updated.

User Access Assignments
User access assignments specify what security privileges a user enjoys in a specified workspace. A user access assignment consists of a user paired with a group access privilege in a workspace. Users can begiven different security privileges in each workspace.

User Maintenance
The process of adding, editing, or deleting users in the Roundtable system.

Variant
Roundtable allows you to create more than one variation of the same object to create variants. Variants have the same object name and type but belong to different product modules. For example, you might need three variations of an install program, one each for UNIX, DOS, and Windows. Only one of the variants of an object can appear in a workspace at the same time. Variants are often created in custom workspaces that are specific to customers or vertical markets.

Version List View
The Version List View provides a list of every version of a specified object in the browse on the TableTop. To get the Version List View, select an object in any other view and then choose View®Object Version List View.

Visual Difference
The Visual Difference tool provides a side-by-side comparison with highlighted differences for any two object versions in the system. This tool is useful for quickly identifying the nature and scope of differences between text files. The visual difference tool cannot be used with binary files or PDBASE, PFILE, or PFIELD objects.

Where Used View
The Where Used View provides a list of each object that references a selected object. This view allows you to see where fields are used, where a procedure is called from, each use of an include file, etc. To get a Where Used View, select an object in any other view and then choose View®Object Where Used  View WIP Work In Process (WIP). When an object is checked out it has a WIP status. When a task is being worked on it has a WIP status.

Work-In-Process
Work In Process (WIP). When an object is checked out it has a WIP status. When a task is being worked on it has a WIP status.

Workspace
Roundtable provides secure development and testing environments by managing configurations of your software applications in workspaces. A workspace is a copy of your application programs and related databases, the content of which is known and managed by Roundtable. Roundtable manages the creation, deletion, and modification of objects (code, databases, t.ables, fields, and text) within the workspace. A workspace is a configuration of object versions.

Workspace Directories
A workspace has a root directory under which the subdirectories and files that make up the software application will exist. The root directory is specified as an absolute path in the Workspace Maintenance Window. Subdirectories are defined as part of workspace module definitions and subtype definitions.

Workspace Module
The contents of each workspace is broken up into one or more workspace modules. Unlike a file system where many levels of nested subdirectories can be seen, only one level of workspace modules exists. Each workspace module points to a single relative subdirectory under the workspace root directory. This subdirectory is defined in the workspace module definition. The contents of a workspace module is defined by the assignment of workspace module definitions to one or more product
modules.

Workspace Module Definition
Workspace module definitions name a workspace module, provide a description for the workspace module, and specify a file system subdirectory relative to any workspace's root directory. You assign a workspace module definition to product modules. You assign product modules to workspaces to define the logical content of your application. Roundtable creates a workspace module and associated subdirectory in the workspace based on the workspace module definition associated with the assigned product module. You specify a product module when creating a
new object. The object is stored in the subdirectory specified in the workspace module definition, and the object is listed in the workspace module.

Workspace Source
The import process promotes code from one or more workspaces (source workspaces) into the current (target) workspace.

Workspace Target
The import process promotes code from one or more workspaces (source workspaces) into the current (target) workspace.

Xref Level
The amount of cross reference information maintained in a workspace is defined by the user-specified Xref level. A level of 1 means that no cross reference information will be maintained. The Xref level is set in the Workspace Maintenance Window and Workspace Modules Window.

Xref View
The Xref View provides a list of each object referenced by a selected object. This view allows you to see what files and fields are used, what procedures are called, each use of an include file, etc. To get an Xref View, select an object in any other view and then choose View®Object Xref View..