Prev | Current Page 126 | Next

Tim Weilkiens

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

e., elements outside of it, are called actors.
An actor is not a concrete system or a concrete individual, but a role, e.g., ??? operator ???
instead of ??? Miss Gabi Goldfi sh ??? or ??? temperature sensor ??? instead of ??? XY sensor article
number 4711. ???
The model element actor is too general for our purposes. We need a rough categorization
of actors and distinguish, e.g., between user, external system, mechanical
system, environmental effect, actuator, and sensor. This differentiation helps us
better understand the system and makes it easier to describe its services later on.
For example, a user has clearly different requirements than a sensor. The categories
are represented by different actor symbols.
A user is a human actor. When a human emerges as a direct interaction partner
with the system we need to provide a user interface within the system, e.g., the GUI 10
of a software application, or the HMI 11 of a technical system, such as a dashboard.
A user can and should be asked directly about their requirements to the system.


Pages:
114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138
pokoje nad morzem tanio pomiary wiatru hotel kredyt samochodowy santander remont warszawa