Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 01:04: UML Behavior: Activities quick start Tags and keywords Topic level ESSENTIAL UML keywords Activity Diagram Activity Action ValueSpecificationAction ValueSpecificationAction::result OpaqueAction AcceptEventAction accept signal action InputPin OutputPin MultiplicityElement::/lower MultiplicityElement::/upper OpaqueBehavior CallBehaviorAction InitialNode ActivityFinalNode ValuePin ValuePin::value ValueSpecification Keywords Magic Model Analyst [Cameo Simulation Toolkit] Cameo Systems Modeler simulation Slide kind UML Activity Diagram Click on the image to view it full size fUML-1.4 EXCLUDES ValuePin fUML-1.4: 'ValuePin – Value pins are excluded from fUML because they are redundant with using value specifications to specify values.' Cameo Simulation Toolkit 19SP3 DOES NOT support ValuePin Up next Parameter vs ActivityParameterNode vs Pin Notes [CAVEAT] fUML-1.4 EXCLUDES ValuePin [CAPABILITY] Cameo Simulation Toolkit 19SP3 DOES NOT support ValuePin Snippets (quotes/extracts) [UML-2.5.1] isControl : Boolean [1..1] = false Indicates whether the Pin provides data to the Action or just controls how the Action executes. [fUML-1.4] If isControlType=true for an ObjectNode, ControlFlows may be incoming to and outgoing from the ObjectNode, objects tokens can come into or go out of the ObjectNode along ControlFlows, and these tokens can flow along ControlFlows reached downstream ... [UML-2.5.1] A control Pin (with isControl=true) must have a control type (isControlType=true), so that they may be used with ControlFlows. [UML-2.5.1] Control Pins are ignored in the constraints that Actions place on Pins (including matching to parameters for InvocationActions ...). [UML-2.5.1] Tokens arriving at a control InputPin have the same semantics as control tokens arriving at the Action, except that control tokens can be buffered in control Pins. [UML-2.5.1] An Action may accept inputs and produce outputs, as specified by InputPins and OutputPins of the Action, respectively. Each Pin on an Action specifies the type and multiplicity for a specific input or output of that Action. [UML-2.5.1] An Action cannot start execution if one of its InputPins has fewer values than the lower multiplicity of that InputPin. [UML-2.5.1] When completed, an Action execution provides any output data on the OutputPins of the Action, and it terminates. [UML-2.5.1] The Action execution consumes input data on all InputPins on the Action up to the upper multiplicity for each InputPin. [UML-2.5.1] Tokens consumed by an Action are immediately removed from its InputPins when the action begins an execution (except in some cases for StructuredActivityNodes, where tokens may remain on InputPins during the Action execution ...) [UML-2.5.1] The upper multiplicity determines the maximum number of values that can be consumed from an InputPin by a single execution of its Action. [UML-2.5.1] 16.4.3.5 Value Specification Actions - A ValueSpecificationAction is an Action that evaluates a ValueSpecification and places the resulting value on its result OutputPin. [fUML-1.4] ValuePin – Value pins are excluded from fUML because they are redundant with using value specifications to specify values. Visit also Visit also (backlinks) Related slides (includes other tutorials) UML2 Activity Diagram - essential metaclasses - ADVANCED REFERENCE ONLY UML2 Actions - metaclasses - ADVANCED REFERENCE ONLY Related slides (backlinks, includes other tutorials) Flags Book traversal links for Starting an Action that has a ValuePin - LIMITED SUPPORT Previous Up Next
