Workflow integration to the model

CAUTION: THIS IS OUTDATED! An update should come when the core model will be finalized.

This page shows how the workflow data map to the general EasySOA Core model.

Note: before even starting to talk about integration, it would be wise to define the point of the BPM aspect in EasySOA. This definition can be found on page EasySOA and workflow build process (this pages also provides some hints about the vocabulary).

Mapping

As a reminder, here is the current version of the EasySOA Core model.

• Workflow: ServiceClient. A workflow can be seen as an "application" that "requires" services, since some of its activities consist in calling services.
• Business workflow diagram: RequirementsDocument.
• Technical workflow diagram: RequirementsDocument.
• Executable workflow: Deliverable.
• Sub-workflow: the link between a workflow and the sub-workflows it calls can be represented by references from RequirementsDocument. That means we only represent links between diagrams (to ease navigation), since workflows are not central to our model: services are.
• Activities, Actors, Lanes, etc. (workflow diagram items): not modeled. Details about a workflow are available in a workflow diagram, and users should refer to it, would they need to.
• Connectors: only partially modeled. As EasySOA is mainly about SOA, we focus on services used in workflows (potentially by the means of connectors). This is represented by the link requires from ServiceConsumer (the workflow) to ServiceReference (the service).