Information Technology Reference
In-Depth Information
<bpmn2:dataOutput id="_3_ActorIdOutput" name="ActorId"/>
<bpmn2:inputSet id="_3b">
<bpmn2:dataInputRefs>
_3_requirementInput
</bpmn2:dataInputRefs>
<bpmn2:dataInputRefs>
_3_complexityInput
</bpmn2:dataInputRefs>
</bpmn2:inputSet>
<bpmn2:outputSet id="_3c">
<bpmn2:dataOutputRefs>
_3_ActorIdOutput
</bpmn2:dataOutputRefs>
</bpmn2:outputSet>
</bpmn2:ioSpecification>
<bpmn2:dataInputAssociation id="_3d">
<bpmn2:sourceRef>reqDescription</bpmn2:sourceRef>
<bpmn2:targetRef>_3_requirementInput</bpmn2:targetRef>
</bpmn2:dataInputAssociation>
<bpmn2:dataInputAssociation id="_3e">
<bpmn2:sourceRef>storyPoints</bpmn2:sourceRef>
<bpmn2:targetRef>_3_complexityInput</bpmn2:targetRef>
</bpmn2:dataInputAssociation>
<bpmn2:dataOutputAssociation id="_3f">
<bpmn2:sourceRef>_3_ActorIdOutput</bpmn2:sourceRef>
<bpmn2:targetRef>developerId</bpmn2:targetRef>
</bpmn2:dataOutputAssociation>
</bpmn2:userTask>
Inside the <bpmn2:ioSpecification> tag, we will define the information that will
be injected and generated inside our flow object. Using the bpmn2:dataInput and
bpmn2:dataOutput tags, we define the variables that will be available in the activity
context. From a business perspective, we can say that the bpmn2:ioSpecification
tag represents the information that will be required to execute the interaction. If we are
talking about a User task, this information will be probably displayed to the user so that he
or she can work with it. If it is an external system, it will probably be used as parameters
to invoke them.
Search WWH ::




Custom Search