Prev | Current Page 345 | Next

Tim Weilkiens

"Systems Engineering with SysML/UML: Modeling, Analysis, Design"

Pins function like buckets for object
tokens and bind them to the parameters of an action.
The notation for pins refl ects their name. It is a small rectangle that is pinned
to the action from the outside. Depending on whether a pin is connected with
incoming or outgoing edges, we distinguish between input pin and output pin
( Figure 3.39 ).
Next to the pin is the name of the object that the pin can accept. This is normally
the name of the object type. You can optionally add the state the object
should be in within square brackets next to that name ( Figure 3.40 ).
You can alternatively denote the input pin and the output pin between two
actions as one single rectangle if they have the same object. This allows you to
178 CHAPTER 3 UML??”Unifi ed Modeling Language
visually separate the object fl ow stronger from the control fl ow ( Customer in
Figure 3.39 ).
Unless otherwise specifi ed, a pin can accept an unlimited number of tokens.
You can limit the number to n tokens by stating {upperbound  n  } next to the
pin ( Figure 3.


Pages:
333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357