Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 11:01: [STUB] Activity modelling extensions in SysML Tags and keywords Topic level ESSENTIAL UML keywords ParameterSet ObjectNode ActivityEdge SysML keywords Rate Rate::rate Continuous «continuous» Discrete «discrete» Probability Probability::probability NoBuffer «noBuffer» Overwrite «overwrite» ControlOperator ControlValueKind ControlValueKind::disable ControlValueKind::enable Optional «streaming» «nonStreaming» «effbd» Slide kind UML Profile Diagram Click on the image to view it full size Up next Next trail section 11:02: Activity Decomposition for functional allocation Notes Snippets (quotes/extracts) [SysML-1.6] When the «rate» stereotype is applied to an activity edge, it specifies the expected value of the number of objects and values that traverse the edge per time interval, that is, the expected value rate at which they leave the source node and arrive at ... [SysML-1.6] Rate ... When the stereotype is applied to a parameter, the parameter shall be streaming, and the stereotype gives the number of objects or values that flow in or out of the parameter per time interval while the behavior or operation is executing. [SysML-1.6] When the «optional» stereotype is applied to parameters, the lower multiplicity shall be equal to zero. This means the parameter is not required to have a value for the activity or any behavior to begin or end execution ... [SysML-1.6] Continuous rate is a special case of rate of flow (see Rate) where the increment of time between items approaches zero. It is intended to represent continuous flows that may correspond to water flowing through a pipe, a time continuous signal, or ... [SysML-1.6] Discrete rate is a special case of rate of flow ... where the increment of time between items is a non-zero. Examples include the production of assemblies in a factory and signals set at periodic time intervals. [SysML-1.6] The «rate» stereotype has a rate property of type InstanceSpecification. The values of this property shall be instances of classifiers stereotyped by «valueType» or «distributionDefinition» ... [SysML-1.6] When the «probability» stereotype is applied to edges coming out of decision nodes and object nodes, it provides an expression for the probability that the edge will be traversed. These shall be between zero and one inclusive, and add up to one ... [SysML-1.6] When the «probability» stereotype is applied to output parameter sets, it gives the probability the parameter set will be given values at runtime. These shall be between zero and one inclusive, and add up to one for output parameter sets of the same ... [SysML-1.6] A control operator is a behavior that is intended to represent an arbitrarily complex logical operator that can be used to enable and disable other actions. ... The «controlOperator» stereotype also applies to operations with the same semantics. [SysML-1.6] When the «controlOperator» stereotype is applied to behaviors, the behavior takes control values as inputs or provides them as outputs, that is, it treats control as data [SysML-1.6] When the «controlOperator» stereotype is not applied, the behavior may not have a parameter typed by ControlValue. [SysML-1.6] When the «nobuffer» stereotype is applied to object nodes, tokens arriving at the node are discarded if they are refused by outgoing edges, or refused by actions for object nodes that are input pins. [SysML-1.6] When the «overwrite» stereotype is applied to object nodes, a token arriving at a full object node removes one that is already there before being added (a full object node has as many tokens as allowed by its upper bound). [SysML-1.6] «effbd» Specifies that the activity conforms to the constraints necessary for EFFBD. [SysML-1.6] «streaming» Used for activities that can accept inputs or provide outputs after they start and before they finish. The activity has at least one streaming parameter. [SysML-1.6] «nonStreaming» Used for activities that accept inputs only when they start, and provide outputs only when they finish. The activity has no streaming parameters. Visit also Visit also (backlinks) Related slides (includes other tutorials) Figure 11-8: Abstract Syntax for SysML Activity Extensions UML2 Activity Diagram - essential metaclasses - ADVANCED REFERENCE ONLY UML2 Actions - metaclasses - ADVANCED REFERENCE ONLY UML2 simplified key metaclass hierarchy (excluding relationships) - ADVANCED REFERENCE ONLY UML2 simplified key "relationship" metaclasses hierachy - ADVANCED REFERENCE ONLY UML2 StateMachine - metaclasses - ADVANCED REFERENCE ONLY UML2 Types of Pins - metaclasses Figure 11-9: Control values Figure 11-10: Continuous system example 1 {ELIDED PINS} Figure 11-10: Continuous system example 1 {EXPLICIT PINS} Figure 11-11: Continuous system example 2 {ELIDED PINS} Figure 11-11: Continuous system example 2 {EXPLICIT PINS} Figure 11-12: Continuous system example 3 {EXPLICIT PINS} Starting an Action that has a ControlPin Related slides (backlinks, includes other tutorials) Flags Book traversal links for SysML Activity extension stereotypes - REFERENCE CARD Previous Up Next
