UML knows the model element
information . It is denoted as a frame with the name of the information in
the center and a black triangle in the upper right corner ( Figure 2.24 ). We distinguish
explicitly between information and its fl ow.
If you want to document that a fl owing piece of information consists of different
units you can use the UML relationship representation . For example, Figure 2.24
documents that the very generally formulated information user input represents
12 That??™s something you would call progress.
57
two pieces of information: PIN and user confi rmation . In general, however, I ??™ d
go about this matter very carefully. I suggest you model this only provided you
really see an immediate benefi t in it. Modeling should never become an end in
itself. SysML allows you to describe many different facts from your system ??™ s real
world. However, the decisive question is not what can be modeled, but what benefi
t you ??™ d have from it.
You can use the same relationship in a later point within the approach to connect
a piece of information with concrete design elements.
Pages:
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154