Three major concepts underlie subsetting:.

Subset definition

Subset expansion

Protection logic

Subset definition, or scoping a subset, is the process of choosing the objects to include in the subset. If you have access to a model, you can create a subset definition on the workstation. Subset definitions are stored in the encyclopedia.

Subset definitions consist of the following components:

Scoping object types

Scoped object

Usage requested

Expansion option

The object types available for defining subsets are called scoping object types. A subset may contain any combination of scoping object types. Each type of scoping object lets you work on different parts of the model.

The scoping object types are:

Subject areas

Entity types

Functions

Processes

External objects

Business systems

Procedures

Procedure steps

Common action blocks

Templates

Databases

Data records

Work attribute sets

Exit states

Organization units

Matrices

COOL:Gen-supplied classes

User-defined classes

User-defined objects

You can choose specific entity types, processes, or procedures to include in a subset, or you can choose all occurrences of an object type. For example, you can define a subset that contains all the model's entity types or templates.

You may include as many scoping objects of as many types as needed to define a subset. In most cases, you only need one or two to define the subset for a specific workstation activity.

SUBSET Expantion

When downloading a subset, COOL:Gen expands your subset to include additional indirectly related, or neighborhood, objects which are related to the scoped object by:

Definition

Content information

The number of objects in the downloaded subset will be greater than the number of scoped objects in the subset definition. COOL:Gen processing logic determines the actual content of the downloaded subset.

The following list defines the available expansion objects:

Expansion Explanation

Default Includes the scoping object and its implied objects

Full Adds additional, optional components

Short Includes smaller groups of objects

Type A Applies only to procedures and procedure steps

Type B Applies only to procedure steps

Expansion happens during subset downloading, not at subset definition. Each scoping object type has its own combination of expansion options.

Protection Logic

Protection logic prevents subset users from making conflicting updates and optimizes shared use of a model.

The following are protection logic rules:

Any number of subsets can have access usage of an object.

Only one active subset can have modify usage of an object. Other subsets containing that object only have access usage of the object.

Only one active subset can have delete usage of an object. All other subsets containing that object have read-only usage.

Usage level defines actions to perform on a scoped object. You may override usage levels or downgrade them at download time.

D - Delete Most powerful level, allows deletion of an object from model.

M - Modify Allows changes to an object. You can add or delete associations.

A - Access Allows use of an object. The user may not change any characteristics of the object. You can add or delete associations.

R - Read Only Only allows read of objects. You cannot add or delete associations.

Encyclopedia transfers between the workstation and the encyclopedia. Selecting Encyclopedia from the Model pull-down provides the following actions:

Check Out a Model: Transfers a model or subset from the encyclopedia to the workstation. Sometimes referred to as download.

Update and Check In Model: Transfers a workstation model or subset to the encyclopedia. Sometimes referred to as upload.

Update but Do Not Check In: Copies a workstation model or subset to the encyclopedia, but does not perform checkin. Sometimes referred to as upload.

Resend Last Update: Retransmits an unsuccessful update from the workstation to the encyclopedia.

Verify Last Update: Checks whether the last update of a model or subset from the workstation to the encyclopedia was successful.

Generate New Model: Uses a workstation copy to create a new model.

Check Out a Model downloads (copies) a model or subset from the encyclopedia to the workstation. Models and subsets are checked out to a user, not a workstation.

When checking out a model or a subset, its encyclopedia name must appear on the workstation's model list. If its encyclopedia name is not on the workstation's model list, you must create an empty model of the same name before requesting check-out.

Checkout Model: Logon to the host.-> Select Model Encyclopedia -> Check Out A Model.-> Type Subset name. Select OK.

Creating New Model: Select Model New. Type Model Name and Local. Select OK.

Generating new Model: Logon to the host. Select Model Encyclopedia Generate New Model. Type Model Name. Select OK.

Update and Check In Model uploads (copies) a workstation model or subset to the encyclopedia. To update and check in a model, you must be authorized in the encyclopedia as a project coordinator or encyclopedia administrator. When a model is checked in (uploaded) to the encyclopedia, it becomes the active copy.

The initial check-in sends the entire model to the encyclopedia. Subsequent updates send only changes unless you specify Generate New Model.

After an update with check-in, the model is set to read-only on the workstation and changes cannot be saved. If an update failure occurs, perform Resend Last Update.

Check-in conflict occurs when:

Adding a new object with the same name as some existing in a model in the encyclopedia

Renaming new objects by the encyclopedia

Another way of illustrating views is as vantage points from which processes "see" entities and their attributes. The attributes are provided on a need-to-know basis. For example, one process might need to view only the Status attribute of an entity occurrence of CUSTOMER. Another process might need to see the Name and Address attributes of CUSTOMER. By carefully defining the scope of views, you can control and restrict access to shared information.

To define the scope of a view, you select the entity types, subtypes, and work sets containing attributes the process receives, uses, or produces.

To define the view subset, you evaluate whether the process receives, uses or produces the view.

Note:

The import, export, local and entity action categories are called view subsets. A view subset is not to be confused with a model subset that can be checked out from the encyclopedia.

An entity action view always represents an entity view with attributes from a single work type, entity type, or subtype. The view is required when:

A pair of entity types must be read to satisfy a selection condition in a Read statement.

Import views represent the information a process or procedure receives. When defining an import view, you specify whether the view is optional.

It is important to distinguish between views that a process receives and views a process reads. A process cannot read an import view. Only entity action views can be created, read, updated and deleted.

Export views represent information a process or procedure produces. Export views consist of information displayed on a screen, printed in a report, or passed to another process, procedure step, or action block.

Local views represent data a process stores temporarily. The data is neither received by a process, nor sent to a screen.

Import, export, and local views can contain group views.

A group view is a collection of associated entity views, subtype views, attribute views, or work views.

When a procedure imports or exports a list of entities, the list is included as a repeating group view.

Repeating group views can contain other repeating group views. This is called a nested repeating group view. Nested repeating group views can be added only to screens. Nested repeating group views are not supported in GUI applications.

Entity action views cannot contain group views, because a process cannot Create, Read, Update, or Delete a collection of views.

You can create a non-repeating group view. Non-repeating group views occurs once; therefore, they function like a view of a single entity, subtype, or work set.

• Imports
• Exports
• Locals
• Entity Actions

Views:

1.Group View

2.Entity View

3.Subtype View

4.Work View

Model

Creates new models; opens, copies, saves, and deletes existing models; displays model status and other information; generates reports; and accesses the encyclopedia.

Open, New, Copy, Delete, Rename, Reports, Info, Save Model, Encyclopedia (Checkout Model, Update and Check in Model, Update but Do not check-in, Resend Last Updt, Verify Last Updt, Generate New Model), ,Exit.

Planning

Provides tools for high-level analysis of a business' activities and data

Data Model, Data Model List, Activity Hierarchy, Activity Dependancy, Organization Hirerarchy, Matrices, Check(Data, Activity, Model)

Analysis

Provides tools to refine the models built during Planning and to build process logic which describes the data and activity interaction

Data Model Browser, Data Model, Data Model List, Componant Modeling, Entity Life Cycle,

Activity Hierarchy, Activity Dependancy, Action Diagram, Workset List, Structure Chart, Action block usage, Matrices, Business System Defination, Check(Data, Activity, Model)

Design

Provides tools to define what the user sees and to detail environment-specific requirements

Business system defaults, Dialog Design, Dialog Flow Browser, Screen Design, Navigation Diagram, Event Browser, Action Diagram, Workset list, Structure Chart, Action block Usage, Prototyping, Dialect Defination, Check, Technical Design, Data Structure List, Data Store List, Transformation, Retransformation, Ref Intigrity Process

Construction

Provides the tools to create databases and executable applications

Environment, Packaging, Generation

Options

Provides tools to access information about the way the model is displayed and the way items are added

Single adds, Multiple Adds, Toolbar, fonts, colours, printer, Paths, Encyclopedia Communications, Encyclopedia Selection, Password, Box size, Consistency Check Level, Support(…)

Window

Provides tools to control the size and display of windows on the screen

The first four values for the target environment are the following:

Operating System (Guardian)

DBMS (NonStop SQL/MP)

Language (C)

TP Monitor (Pathway)

These four values are always used for the generation and installation of DDL and referential integrity triggers.

2. Select a tick mark in the Code or Scrn column for each object to generate

3. Select a tick mark in the Inst column for each Dialog, Batch, or Window Manager to which the selected Code or Scrn objects are subordinate

4. Generate Code, Selected.

An external action block contains only import and export views and an EXTERNAL designation.

A procedure step calls an external action block through the USE statement.

To define the logic for an action diagram, select Add Statement. The statements are organized according to their type: looping statements, entity action statements, and other miscellaneous statements.

Looping Statements

Case

Case of

Else

Else If

For

For Each

If

Otherwise

Repeat

While

Entity Action Statements

Associate

Create

Delete

Disassociate

Read

Read Each

Remove

Set

Summarize

Summarize Each

Transfer

Update

Miscellaneous Statements

Abort Transaction

Command Is

Escape

Exception

Database Exception

Exit State Is

External

Functions

Invoke

Make

Move

Next

Note

Printer Terminal Is

Retry Transaction

Use

Procedure Step Use

Help for these actions is available only from the Add Statement pull-down and the Help Index. You cannot access help for these actions from the Add Statement pop-up window.

USE references logic in common action blocks and algorithms. The logic is common in that it can also be used in other processes, procedures, and action blocks (including external action blocks).

After selecting an action block to USE, you then match the import views, export views, local views, and entity action views. You can also match views to <none>. For example, if you do not currently have a view to match to INPUT_EMPLOYEE, you can leave the view unmatched and use the Change function later to match the view.

After selecting an algorithm, you then match the import views of the algorithm with the supplying views from the process. The "ing" form of the USE statement indicates the use of an algorithm. For example, SET bonus value USING bonus_value_calculation.