Stardust/Enhancing and Embedding Stardust/Browser Modeler/BPMN Mapping

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

Tasks

Task (Abstract / None)

Spec: OMG p.156f

BPMN Modelling Conformance Subclasses: Descriptive / Analytic

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

Supporting Classes (Common Executable Conformance Sub-Class)

Spec.: cp. OMG p.7

• StandardLoopCharacteristics (id, loopCondition): Stardust Loop (While|Repeat with Loop Condition) (Todo)
• MultiInstanceLoopCharacteristics (id, isSequential, loopDataInput, inputDataItem): no direct support - tbd
• Rendering: not used (cp. userTask)
• Resource (id, name): Performer (see userTask and Resource)), further resources: tbd
• ResourceRole (id, resourceRef, resourceAssignmentExpression): Performer (see userTask and ResourceRoles))
• InputOutputSpecification (id, dataInputs, dataOutputs): Task Data Flow (see Data)
• DataInput (id, name, isCollection, itemSubjectRef): Data Flow (see Data)
• DataOutput (id, name, isCollection, itemSubjectRef): Data Flow (see Data)
• ItemDefinition (id, structure or import) [XSD Complex Type structure]: Data Flow (see Data)
• Operation (id, name, inMessageRef, outMessageRef, errorRefs): Applications / Interactive Applications (see serviceTask, userTask, (Message-) Events)
• Message (id, name, structureRef): not used for execution.
• Error (id, structureRef): tbd
• Assignment (id, from, to): used for Stardust DataMapping (Application Tasks / Interactive Tasks), ParameterMapping (Triggers) (see dataAssociation
• MessageEventDefinition (id, messageRef, operationRef): operationRef only (see (Message-) Events
• TerminateEventDefinition (id): tbd
• TimerEventDefinition (id, timeDate): timeDate plus timeCycle plus stopTime extension (see [[#timerStartEvent|timerStartEvent])

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.