However, this extension is
applicable to the internal block diagram only. We should switch to this diagram form
at the latest when identifying the system interaction points (Section 2.3.3). If you
include this step in your approach, then it would be a good idea to model the system
context diagram as an internal block diagram right from the outset.
Figure 2.26 shows the system context in the internal block diagram. In what
block are we, internally? We have to introduce a context element that encompasses
the system and all actors. This element is denoted with the stereotype
?«systemContext?» . You can see in Figure 2.27 how this context element is modeled;
note that this diagram does not show all actors.
FIGURE 2-24
Structuring information.
bdd [package] Information [user input]
?«information?»
PIN
?«represents?» ?«represents?»
?«information?»
User confirmation
?«information?»
User input
FIGURE 2-25
Information as a representative of design elements.
bdd [package] Information [key]
ID:String
wasRemoved:Boolean
?«represents?»
?«signal?»
KeySignal
?«information?»
Key
59 2.
Pages:
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156