PSL/PSA

Set Syntax

• Print
• Email

Details

Category: PSL v6.x Syntax

Written by Geoffrey Darnton

Set Syntax

Defining a Set using PSL

A Set definition is used for data or information to be included in a PSA database. As with all Objects in PSL, the definition starts with a basic statement:

DEFINE SET set-name(s) ;

Normally, sets would be defined one at a time. However, the option to have a list of set names is used when it is sufficient simply to declare a list of objects as sets - this may be necessary to prevent an object being identified as ambiguous with respect to type.

Information about a Set is then defined using a set of Relations. These Relations are grouped according to a set of system ASPECTS. There is no special significance to these aspects, and a system definer could use any combination of available relations, and does not need to make any declarations about those aspects. Here are the available aspects, and links will take you to the available syntax for each:

PROPERTIES & CHARACTERISTICS

SYNONYM [IS] names(s);

DESCRIPTION;

text-entry ;

DOCUMENTATION;

text-entry;

LONG-NAME;

text-entry;

KEYWORD [IS] string(s) ;

LEVEL [IS] string(s) ;

SEE-MEMO [ systemparameter-name string ] memo-name , ... ;

SECURITY [IS] string(s) ;

SOURCE [IS] string(s) ;

ASSERT non attribute-name subtype-name system-parameter-name [IS] attribute-name integer real string system-parameter-name , ... ;

ASSERTED [BY] non attribute-name subtype-name system-parameter-name [TO BE] integer real string system-parameter-name [FOR] attribute-name , ... ;

ATTRIBUTE [IS] attribute-name integer real string system-parameter-name , ... ;

SUBTYPED [AS] subtype-name ;

SYSTEM BOUNDARY & I/O FLOW

GENERATED [ [ON] system-parameter-name event-name condition-name integer real string ] BY process-name interface-name , ... ;

GENERATED [ system-parameter-name event-name condition-name integer real string ] [TIMES] ] BY process-name interface-name , ... ;

RECEIVED [ [ON] system-parameter-name event-name condition-name integer real ] BY process-name interface-name , ... ;

RECEIVED [ system-parameter-name event-name condition-name integer real [TIMES] ] BY process-name interface-name , ... ;

RESPONSIBLE-INTERFACE [IS] process-name interface-name ;

SYSTEM STRUCTURE

SUBPART [IS] set-name(s) ;

PART [OF] set-name ;

COMPOSED [OF] [ systemparameter-name integer real ] set-name , ... ;

COMPONENT [ systemparameter-name integer real ] IN set-name , ... ;

SUBSETS [ARE] set-name(s);

SUBSET [OF] set-name(s);

GENERIC STRUCTURE

INCLUDES [ system-parameter-name integer real string ] name , ... ;

INCLUDED [ system-parameter-name integer real string ] IN name , ... ;

KNOWN [AS] name [ [BY] name] , ... ;

KNOWN-NAME [OF] name [ [FOR] name] , ... ;

KNOWS name [AS] name , ... ;

LINKS name [ [AS] system-parameter-name string ] , ... ;

LINKED [TO] name [ [AS] system-parameter-name string ] , ... ;

DATA STRUCTURE

CLASSIFICATION [IS] attribute-name system-parameter-name integer , ... ;

COLLECTION [OF] [ system-parameter-name integer real ] entity-name input-name output-name group name element-name ] , ... ;

ORDERED [BY] entity-name group name element-name ;

SUBSETTING-CRITERIA [ARE] entity-name group name element-name ;

DATA DERIVATION & FLOW

DERIVATION ;

text-entry ;

DERIVED MAINTAINED UPDATED [ [ON] system-parameter-name condition-name event-name integer real string ] [BY] process-name, ... [USING set-name(s) group-name(s) element-names(s) entity-name(s) input-name(s) condition-name(s) relation-name(s) ] ;

EMPLOYED [ [ON] system-parameter-name condition-name event-name integer real string ] [BY] process-name, ... ;

USED [BY] process-name(s) [TO] DERIVE [ [ON] system-parameter-name condition-name event-name integer real string ] set-name(s) group-name(s) element-names(s) entity-name(s) output-name(s) condition-name(s) relation-name(s) , ... ;

USED [BY] process-name(s) [TO] UPDATE [ [ON] system-parameter-name condition-name event-name integer real string ] set-name(s) group-name(s) element-names(s) entity-name(s) input-name(s) condition-name(s) relation-name(s) , ... ;

USED [BY] process-name(s) [TO] MAINTAIN [ system-parameter-name condition-name event-name integer real string ] set-name relation-name , ... ;

FLOWS [ [ON] system-parameter-name condition-name event-name integer real string ] FROM set-name(s) process-name interface-name TO set-name(s) process-name interface-name , ... ;

OBTAINS [ [ [ON] system-parameter-name condition-name event-name integer real string ] set-name(s) group-name(s) element-names(s) entity-name(s) input-name(s) condition-name(s) relation-name(s) output-name(s) FROM set-name(s) process-name interface-name ], ... ;

SENDS [ [ [ON] system-parameter-name condition-name event-name integer real string ] set-name(s) group-name(s) element-names(s) entity-name(s) input-name(s) condition-name(s) relation-name(s) output-name(s) TO set-name(s) process-name interface-name ], ... ;

HAS [ [ [ON] system-parameter-name condition-name event-name integer real string ] entity-name ] , ... ADDED MODIFIED REFERENCED REMOVED [BY] process-name(s);

QUANTIFICATION & RESOURCE USAGE

CARDINALITY [IS] system-parameter-name integer real string ;

SYSTEM DYNAMICS

CAUSES event-name(s) [WHEN event-name(s)] [ IF condition-name(s) [ [IS] TRUE] ] ;

CAUSES event-name(s) [WHEN event-name(s)] IF condition-name(s) [IS] FALSE;

CHANGES condition-name(s) ;

INTERRUPTS process-name(s) [IF condition-name(s) [ [IS] TRUE ] ] ;

RESUMES process-name(s) [IF condition-name(s) [ [IS] TRUE ] ] ;

TERMINATES process-name(s) [IF condition-name(s) [ [IS] TRUE ] ] ;

TRIGGERS process-name(s) [IF condition-name(s) [ [IS] TRUE ] ] ;

INTERRUPTS process-name(s) IF condition-name(s) [IS] FALSE ;

RESUMES process-name(s) IF condition-name(s) [IS] FALSE ;

TERMINATES process-name(s) IF condition-name(s)[IS] FALSE ;

TRIGGERS process-name(s) IF condition-name(s) [IS] FALSE ;

LOCKED [ BY ] event-name(s) [ IF condition-name(s) [ [IS] TRUE ] ] ;

UNLOCKED [ BY ] event-name(s) [ IF condition-name(s) [ [IS] TRUE ] ] ;

LOCKED [ BY ] event-name(s) IF condition-name(s) [IS] FALSE ;

UNLOCKED [ BY ] event-name(s) IF condition-name(s) [IS] FALSE ;

LOCKING CAUSES event-name(s) [ IF condition-name(s) [ [IS] TRUE ] ] ;

UNLOCKING CAUSES event-name(s) [ IF condition-name(s) [ [IS] TRUE ] ] ;

LOCKING CAUSES event-name(s) IF condition-name(s) [ [IS] FALSE ;

UNLOCKING CAUSES event-name(s) IF condition-name(s) [ [IS] FALSE ;

MAKES condition-name(s) TRUE FALSE ;

VOLATILITY-MEMBER ;

text-entry ;

VOLATILITY-SET ;

text-entry ;

PROJECT MANAGEMENT

PROJECT-CROSS-REFERENCE [IS] name(s) string(s) ;

PROJECT-CROSS-REFERENCED [WITH] name(s) ;

RESPONSIBLE-PROBLEM-DEFINER [IS] string(s) ;

REQUIREMENTS TRACEABILITY

SATISFIES requirement-name [ [BY] HAVING system-parameter-name integer real ] , ... ;

TRACE-KEY [IS] string(s) ;

[there are no relations for System Control, when defining a Set].

Subtype Syntax

• Print
• Email

Details

Category: PSL v6.x Syntax

Written by Geoffrey Darnton

Subtype Syntax

Defining a Subtype using PSL

A Subtype definition is used for data or information to be included in a PSA database. Typically, a Subtype can be used to rename an object type or to add additional object types. As with all Objects in PSL, the definition starts with a basic statement:

DEFINE SUBTYPE subtype-name(s) ;

Normally, subtypes would be defined one at a time. However, the option to have a list of subtype names is used when it is sufficient simply to declare a list of objects as subtypes - this may be necessary to prevent an object being identified as ambiguous with respect to type.

Information about a Subtype is then defined using a set of Relations. These Relations are grouped according to a set of system ASPECTS. There is no special significance to these aspects, and a system definer could use any combination of available relations, and does not need to make any declarations about those aspects. Here are the available aspects, and links will take you to the available syntax for each:

PROPERTIES & CHARACTERISTICS

SYNONYM [IS] names(s);

DESCRIPTION;

text-entry ;

DOCUMENTATION;

text-entry;

LONG-NAME;

text-entry;

KEYWORD [IS] string(s) ;

LEVEL [IS] string(s) ;

APPLIES [TO] name(s) [ [AS] systemparameter-name string ] ;

SEE-MEMO [ systemparameter-name string ] memo-name , ... ;

SECURITY [IS] string(s) ;

SOURCE [IS] string(s) ;

ATTRIBUTE [IS] attribute-name integer real string system-parameter-name , ... ;

SUBTYPED [AS] subtype-name ;

SYSTEM STRUCTURE

SUBPART [IS] subtype-name(s) ;

PART [OF] subtype-name ;

COMPOSED [OF] [ systemparameter-name integer real ] subtype-name , ... ;

COMPONENT [ systemparameter-name integer real ] IN subtype-name , ... ;

GENERIC STRUCTURE

INCLUDES [ system-parameter-name integer real string ] name , ... ;

INCLUDED [ system-parameter-name integer real string ] IN name , ... ;

KNOWN [AS] name [ [BY] name] , ... ;

KNOWN-NAME [OF] name [ [FOR] name] , ... ;

KNOWS name [AS] name , ... ;

LINKS name [ [AS] system-parameter-name string ] , ... ;

LINKED [TO] name [ [AS] system-parameter-name string ] , ... ;

PROJECT MANAGEMENT

PROJECT-CROSS-REFERENCE [IS] name(s) string(s) ;

PROJECT-CROSS-REFERENCED [WITH] name(s) ;

RESPONSIBLE-PROBLEM-DEFINER [IS] string(s) ;

REQUIREMENTS TRACEABILITY

TRACE-KEY [IS] string(s) ;

[there are no relations for System Boundary & Input/Output Flow, Data Structure, Data Derivation & Flow, Quantification & Resource Usage, System Control, or System Dynamics when defining a Subtype].

Resource Syntax

• Print
• Email

Details

Category: PSL v6.x Syntax

Written by Geoffrey Darnton

Resource Syntax

Defining a Resource using PSL

A Resource definition is used for data or information to be included in a PSA database. A Reesource can be any kind of resource needed and at some stage consumed by the target processing system. As with all Objects in PSL, the definition starts with a basic statement:

DEFINE RESOURCE resource-name(s) ;

Normally, resources would be defined one at a time. However, the option to have a list of resource names is used when it is sufficient simply to declare a list of objects as resources - this may be necessary to prevent an object being identified as ambiguous with respect to type.

Information about a Resource is then defined using a set of Relations. These Relations are grouped according to a set of system ASPECTS. There is no special significance to these aspects, and a system definer could use any combination of available relations, and does not need to make any declarations about those aspects. Here are the available aspects, and links will take you to the available syntax for each:

PROPERTIES & CHARACTERISTICS

SYNONYM [IS] names(s);

DESCRIPTION;

text-entry ;

DOCUMENTATION;

text-entry;

LONG-NAME;

text-entry;

KEYWORD [IS] string(s) ;

LEVEL [IS] string(s) ;

SEE-MEMO [ systemparameter-name string ] memo-name , ... ;

SECURITY [IS] string(s) ;

SOURCE [IS] string(s) ;

ASSERT non attribute-name subtype-name system-parameter-name [IS] attribute-name integer real string system-parameter-name , ... ;

ASSERTED [BY] non attribute-name subtype-name system-parameter-name [TO BE] integer real string system-parameter-name [FOR] attribute-name , ... ;

ATTRIBUTE [IS] attribute-name integer real string system-parameter-name , ... ;

SUBTYPED [AS] subtype-name ;

SYSTEM STRUCTURE

SUBPART [IS] resource-name(s) ;

PART [OF] resource-name ;

COMPOSED [OF] [ systemparameter-name integer real ] resource-name , ... ;

COMPONENT [ systemparameter-name integer real ] IN resource-name , ... ;

GENERIC STRUCTURE

INCLUDES [ system-parameter-name integer real string ] name , ... ;

INCLUDED [ system-parameter-name integer real string ] IN name , ... ;

KNOWN [AS] name [ [BY] name] , ... ;

KNOWN-NAME [OF] name [ [FOR] name] , ... ;

KNOWS name [AS] name , ... ;

LINKS name [ [AS] system-parameter-name string ] , ... ;

LINKED [TO] name [ [AS] system-parameter-name string ] , ... ;

QUANTIFICATION & RESOURCE USAGE

CONSUMED [BY] processor-name [ [AT] [A] RATE [OF] [ system-parameter-name integer real PER attribute-name unit-name process-name input-name output-name entity-name event-name ] , ... ] ;

MEASURED [BY] unit-name ;

PROJECT MANAGEMENT

PROJECT-CROSS-REFERENCE [IS] name(s) string(s) ;

PROJECT-CROSS-REFERENCED [WITH] name(s) ;

RESPONSIBLE-PROBLEM-DEFINER [IS] string(s) ;

REQUIREMENTS TRACEABILITY

SATISFIES requirement-name [ [BY] HAVING system-parameter-name integer real ] , ... ;

TRACE-KEY [IS] string(s) ;

[there are no relations for System Boundary & Input/Output Flow, Data Structure, Data Derivation & Flow, System Control, or System Dynamics when defining a Resource].