Browse Prior Art Database

PFI803: Method and Apparatus for Tool-neutral Interchange and Standardization of Process Flows with local styles

IP.com Disclosure Number: IPCOM000195707D
Publication Date: 2010-May-12
Document File: 5 page(s) / 92K

Publishing Venue

The IP.com Prior Art Database

Abstract

Executive Summary: A method and apparatus to create a tool-neutral process interchange format to enable an efficient process interchange/conversion.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 5

PFI803: Method and Apparatus for Tool-neutral Interchange and Standardization of Process Flows with local styles

Summary:

     A method and apparatus to create a tool-neutral process interchange format to enable the capabilities described below.

     Enables an efficient process interchange/conversion from N to 1 and then 1 to N instead of N-to-N conversion. That is, convert heterogeneous proprietary process formats to one interchange format with enriched attributes, and then convert the interchange format to various target proprietary process formats.
choice of intelligently filtering to (1) rules to trim down model by selectively copying a collection of elements useful to the target model , or (2) copy all regardless of the bulk elements of the source model

     Enable further transformation into various proprietary process formats to be viewed and used by proprietary tools, including shared semantics that may be above the common baseline information

     Enables easy process standardization and maximize interoperability, i.e. tool-neutral process interchange format can be easily transformed to conforming to a standard, e.g. BPMN format

Provides tool specific extensions


Add metadata and data for tool-specific extensions to:
1) enable downstream transformation to the format used by the creating tool or other tool
2) re-imported into the originating tool with Vendor-proprietary model data
3) Vendor's own extensions to a standard such as BPMN
4) Extension elements can be arranged either in an aggregated in one element types, e.g. AppExtensions, or in a dispersed...