However it is more common to speak of
OR versus AND semantics.
?«controlOperator?»
act Enable/disable display
disable enable
[on] [off]
ControlValue
{probability0.5} {probability0.5}
Display
on/off
265
discipline of the system we model, and they do not contain any software-specific
elements. Every system, regardless of whether it is a software or hardware system,
or a social or biological system has states and state transitions that can be
described in a state model ( Figure 4.57 ).
4.10 Interaction Diagrams
In UML, this category includes four specific diagrams: the sequence diagram, the
communication diagram, the timing diagram, and the interaction overview diagram.
Of these diagrams SysML uses only the sequence diagram ( Figure 4.58 ).
While activity diagrams allow us to describe fl ows more or less independently
of the executing system elements, interaction diagrams show us who calls which
system behavior. In interaction, it is normally used to describe a concrete fl ow
(scenario).
4.11 General Modeling Elements
This section introduces model elements of SysML that do not belong entirely to
one of the categories discussed above, such as the requirement diagram.
Pages:
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484