Difference between revisions of "Workflow Reference Model"
m (The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).) |
m |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | The | + | The Workflow Reference model has been developed from the generic workflow application structure by identifying the interfaces within this structure that enable products to interoperate at a variety of levels. All workflow systems contain a number of generic components which interact in a defined set of ways; different products will typically exhibit different levels of capability within each of these generic components. To achieve interoperability between workflow products a standardized set of interfaces and data interchange formats between such components is necessary. A number of distinct interoperability scenarios can then be constructed by reference to such interfaces, identifying different levels of functional conformance as appropriate to the range of products in the market. <ref>[ftp://ftp.ufv.br/dpi/mestrado/Wkflow-BPM/The%20Workflow%20Reference%20Model.pdf Defining Workflow Reference Model -WFMC]</ref> |
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | ==See Also== | ||
| + | *[[Reference Model]] | ||
| + | |||
| + | |||
| + | |||
| + | ==References== | ||
| + | <references /> | ||
Latest revision as of 17:27, 13 December 2022
The Workflow Reference model has been developed from the generic workflow application structure by identifying the interfaces within this structure that enable products to interoperate at a variety of levels. All workflow systems contain a number of generic components which interact in a defined set of ways; different products will typically exhibit different levels of capability within each of these generic components. To achieve interoperability between workflow products a standardized set of interfaces and data interchange formats between such components is necessary. A number of distinct interoperability scenarios can then be constructed by reference to such interfaces, identifying different levels of functional conformance as appropriate to the range of products in the market. [1]
See Also