For this reason, there may be a major concept change coming up. Luckily,
this doesn ??™ t have an impact on our project in its current phase, since we haven ??™ t
analyzed the radio subsystem of the on-board computer in detail yet. We ??™ ve
modeled the other parts independently of it. This shows once again that a good
dependency management and a structured model pay in the end.
17 Note that the transition from the analysis to the design is flowing. This is the reason why there
are often discussions about the exact delimitation of the two terms that lead to no result. In fact,
we already took solutions, such as the card reader, into account in the analysis.
111 2.7 Realizing Use Cases
at the information fl ows between the blocks, and use interaction diagrams again
to derive interfaces (Section 2.7.3). This time they are the interfaces of the blocks.
The behavior of each of the blocks can be easily described in a state machine.
This approach will repeat itself if we want to detail a block. We treat a block as
we treated the system in the approach described above, and so on, until we reach
FIGURE 2-70
The approach model for ??? realizing use cases.
Pages:
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251