A Business Algorithm is used to express the generalized function of the Business Process.
The underlying properties of the algorithm or method rather than the specifics of any particular implementation. In short a description of the method in its simplest and most general representation.


This extends the WorkflowStepSequence allowing for a graph structuring of WorkflowSteps. It adds a WorkflowStepRelationStructure which describes the order of Workflow steps in StructuredWorkflowSteps that has multiple entry points and/or multiple exit points and/or, alternatively, a WorkflowStep can have multiple predecessors and/or multiple successors.


In the context of data management a WorkflowStepRelationStructure describes a network of data transformations and data products. Like all RelationStructures, a WorkflowStepRelationStructure is a Directed Acyclic Graph (DAG). A forward looking WorkflowStepRelationStructure describes the succession of data transformations and data products. A backward looking WorkflowStepRelationStructure describes the antecedents of one or a combination of data transformations and/or data products.



A BusinessProcess precondition or post condition which describes the condition which must be met to begin (pre) or exit (post) a process. It may include a specified dataset. The dataset has a position in the DataStore, SQL that describes it, rejectionCriteria against which its adequacy may be tested and an optional annotation that describes its provenance.


Whereas ComputationActions are used in statistical packages like SPSS, Stata, SAS and R to perform data management and data transformations, MetadataDrivenActions are used by ETL (Extract Transform Load) platforms along with ComputationActions.

In ETLs the user is presented with a menu of MetadataDrivenActions that are captured here in an external controlled vocabulary.

In ETLs users enter into a dialog with the platform through which they customize the MetadataDrivenAction. The user writes no code. The dialog is saved.


Allows for the identification of the BusinessProcess specifically as a member and optionally provides an index for the member within an ordered array.


A DataPipeline is a single traversal of the Generic Longitudinal Business Model (GLBPM) and/or the Generic Statistical Business process Model (GSBPM) in the course of a study where a study is either one off or a wave in a StudySeries.


BusinessProcesses could be Generic Longitudinal Business Process Model (GLBPM) and/or Generic Statistical Business Process Model (GSBPM) steps and/or sub-steps. BusinessProcesses participate in a DataPipeline by virtue of their preconditions and postconditions.

A BusinessProcess differs from a WorkflowStep by virtue of its granularity. Higher level operations are the subject of BusinessProcesses. A BusinessProcess has a WorkflowStepSequence through which these higher levels operations may optionally be decomposed into WorkflowSteps.


Gives a UnitDataRecord structure to a Logical Record. UnitDataRecord structures a LogicalRecord as either a SimpleCollection or a StructuredCollection (InstanceVariableRelationStructure) of instance variables.

The UnitDataRecord also organizes instance variables in a UnitDataViewpoint. The UnitDataViewpoint assigns roles to Instance Variables. In any one UnitDataViewpoint UnitDataRecord instance variables play one of three roles: identifier, measure or attribute. The same UnitDataRecord may have many UnitDataViewpoints.


Subscribe to RSS - Proposal