Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Stardust/Enhancing and Embedding Stardust/Browser Modeler/BPMN Mapping"
(→Applications (BPMN Interface / Endpoints)) |
|||
Line 1: | Line 1: | ||
=BPMN 2.0 Elements= | =BPMN 2.0 Elements= | ||
+ | |||
=Callable Elements= | =Callable Elements= | ||
==process== | ==process== | ||
− | Spec: OMG p.146f | + | '''Spec:''' OMG p.146f |
'''Stardust Support: ''' full | '''Stardust Support: ''' full | ||
Line 25: | Line 26: | ||
==globalTask== | ==globalTask== | ||
− | Spec: OMG p.187f | + | '''Spec:''' OMG p.187f |
+ | |||
+ | '''BPMN Modelling Conformance Subclasses:''' - | ||
'''Stardust Support: ''' partial | '''Stardust Support: ''' partial | ||
Line 50: | Line 53: | ||
== subProcess == | == subProcess == | ||
− | Spec: OMG p.173f | + | '''Spec:''' OMG p.173f |
− | '''Stardust Support: ''' | + | '''BPMN Modelling Conformance Subclasses:''' Executable (expanded) / Descriptive / Analytic |
+ | |||
+ | '''Stardust Support: ''' partial (collapsed subprocesses) | ||
BPMN Sub-Processes correspond to Stardust Sub-Processes. In Stardust, subprocess-activities call a process whilst BPMN subprocesses contain their process elements (i.e. they are flow element containers). However, by specifying the called process in stardust as 'synchronous with shared data', the behaviour and even data visibility are similar to BPMN. | BPMN Sub-Processes correspond to Stardust Sub-Processes. In Stardust, subprocess-activities call a process whilst BPMN subprocesses contain their process elements (i.e. they are flow element containers). However, by specifying the called process in stardust as 'synchronous with shared data', the behaviour and even data visibility are similar to BPMN. | ||
Line 78: | Line 83: | ||
== Task (Abstract / None) == | == Task (Abstract / None) == | ||
− | Spec: OMG p.156f | + | '''Spec:''' OMG p.156f |
'''Stardust Support: ''' full | '''Stardust Support: ''' full | ||
Line 191: | Line 196: | ||
OMG2011: Business Process Model and Notation (BPMN), Version 2.0, formal/2011-01-03, available from http://www.omg.org/spec/BPMN/2.0/ | OMG2011: Business Process Model and Notation (BPMN), Version 2.0, formal/2011-01-03, available from http://www.omg.org/spec/BPMN/2.0/ | ||
+ | Notice: The pages referred to primarily indicate where attributes and the object model are described. Further information about specific elements (e.g. execution semantics etc.) may be found elsewhere in the specification. |
Revision as of 06:44, 11 October 2012
Contents
BPMN 2.0 Elements
Callable Elements
process
Spec: OMG p.146f
Stardust Support: full
BPMN processes correspond to processes in Stardust.
Transformation: partial (related elements missing)
Testmodel(s): e.g. CollapsedSubprocess.bpmn (any testmodel contains at least one process).
see also callActivity
Related Elements
- Auditing: tbd
- Monitoring: tbd
- Property: Stardust Variable (Data)
- Resource role: tbd
- Artifact: tbd
- CorrelationSubscription: tbd
- Interface: tbd
globalTask
Spec: OMG p.187f
BPMN Modelling Conformance Subclasses: -
Stardust Support: partial
BPMN Global Tasks are not directly available in Stardust, however, a process with a corresponding 'global task' can be generated.
Transformation: TODO
Task call: see callActivity
Related Elements
- Property: Stardust Variable (Data)
- Resource role: tbd
- Interface: tbd
Specific types
- globalUserTask: see userTask
- globalManualTask: see manualTask
- globalScriptTask: see scriptTask
- globalBusinessRuleTask: see businessRuleTask
Activities / Subprocesses
subProcess
Spec: OMG p.173f
BPMN Modelling Conformance Subclasses: Executable (expanded) / Descriptive / Analytic
Stardust Support: partial (collapsed subprocesses)
BPMN Sub-Processes correspond to Stardust Sub-Processes. In Stardust, subprocess-activities call a process whilst BPMN subprocesses contain their process elements (i.e. they are flow element containers). However, by specifying the called process in stardust as 'synchronous with shared data', the behaviour and even data visibility are similar to BPMN.
Transformation: available
Testmodel(s): CollapsedSubprocess.bpmn
Related Elements
Specific types
- AdHocSubprocess: tbd
- EventSubprocess: tbd
callActivity
Process Call
GlobalTask Call
Tasks
Task (Abstract / None)
Spec: OMG p.156f
Stardust Support: full
BPMN unspecific task is not executable. It is mapped to a Route Activity in Stardust.
Transformation: available
Testmodel(s): AbstractTask.bpmn
userTask
Spec: OMG p.163,
BPMN Modelling Conformance Subclasses: Executable / Descriptive / Analytic
Stardust Support: full
BPMN user tasks correspond to Stardust Manual Activities or Interactive Activites respectively.
Transformation: available
Testmodel(s): Stardust Manual Activity (with performers): UserTask.bpmn, Stardust Interactive Task: UserTaskWebApp.bpmn
Attributes
- implementation: Manual Activity=“##unspecified", JSP=http://java.sun.com/JSP/Page, JSF=http://java.sun.com/jsf, JFC= http://java.sun.com/jfc
Related Elements
- resources [ResourceRole]: Stardust Participant (if ResourceRole type Performer). See also Resources
- Rendering: not used (see extension)
Extension Elements/Attributes
- StardustUserTask
- interactiveApplicationRef -> BPMN Interface, see also Interface
ServiceTask
sendTask
receiveTask
businessRulesTask
scriptTask
Services
Interface
Endpoints
Data
dataObject
dataAssociation
Flow Control
Gateways
Sequence Flow
Events
Start Events
startEvent (None)
timerStartEvent
messageStartEvent
Intermediate Events
Catching message Intermediate Event
Throwing message Intermediate Event
Catching timer Intermediate Event
Boundary error Intermediate Event
End Events
endEvent (None)
messageEndEvent
terminateEndEvent
Resources
Resource
ResourceRole
Performer
Human Performer
Potential Owner
Processes Collaboration
Participant
Lanes
References
OMG2011: Business Process Model and Notation (BPMN), Version 2.0, formal/2011-01-03, available from http://www.omg.org/spec/BPMN/2.0/ Notice: The pages referred to primarily indicate where attributes and the object model are described. Further information about specific elements (e.g. execution semantics etc.) may be found elsewhere in the specification.