Browse Prior Art Database

Converting between Object Oriented and Workflow Graph Views of Processes

IP.com Disclosure Number: IPCOM000114460D
Original Publication Date: 1994-Dec-01
Included in the Prior Art Database: 2005-Mar-28
Document File: 2 page(s) / 90K

Publishing Venue

IBM

Related People

Bandat, K: AUTHOR

Abstract

Disclosed is a concept for the conversion between two different views over otherwise fully equivalent processes: between an Object Oriented process view and a workflow graph represented process view.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Converting between Object Oriented and Workflow Graph Views of Processes

      Disclosed is a concept for the conversion between two different
views over otherwise fully equivalent processes: between an Object
Oriented process view and a workflow graph represented process view.

      In order to enable such conversion, both the concepts of OO
description and of workflow description of software have to be
extended towards a semantically complete process description.

      In the OO world an Object Class Library is to be established,
where for each object class the following properties have to be
realized:
  o  specialized methods are defined which can return a status value
      from an object instance or can change the status value for an
      object instance.
  o  other specialized methods are defined which are triggered for
      execution against an object when this object reaches a certain
      defined state.
  o  when a message triggers the application of methods against
      objects, a multiplicity of methods may be triggered, thus
      creating a split into multiple parallel messages to be executed
  o  in symmetry to above, some methods may only be triggered when a
      list or a set of objects has reached a certain state.  In this
      way multiple parallel methods, changing object states, may be
      joined into on single successor method triggered by the
multiple
      objects reaching their state.

      In the OO world also an Object Inventory is to be established
which contains a complete list of all object instances and their
states in a given scope (for each instance of process execution, as
for a program, or a project).  The status information is contained in
the Inventory only for descriptive and operational convenience since
the status information is also available via applying the respective
method to an object.

      It is claimed that with the above given system a process can be
completely defined, and each instance of object execution can be
completely controlled.  It should be understood that the distinction
between different executions of the same defined process originates
from user entered information, and also from data accessed by
functions that are not modelled for the process.

      The workflow side of the world also needs some extensions that
exceed the current standard features of workflow graph defined
processes.  Work flow graphs currently are built up of activity nodes
...