Other members just mince along and
continue looking at the system from a very rough level.
I think a way in between these two extremes seems to be the most suitable,
as is often the case. It doesn ??™ t make sense to courageously jump at details, while
we still don ??™ t know whether or not they are relevant at all. On the other hand, it
doesn ??™ t make sense either to avoid getting specific and instead cowardly withdraw
to the rough abstract levels.
We should keep these considerations in mind as we start working on the
design.
2.7.3 Model System Structures
Modeling system structures is shown in Table 2.20 .
In this approach step we want to describe the system ??™ s structures that are
needed in order to realize the requirements. We are talking of the blocks our system
is composed of eventually.
The domain knowledge model shows us the structures of the domain-specifi c
objects that occur in the system. This model is primarily a model of terms and
does not represent the system structures. Based on our top-down approach, we
fi rst start looking for the next level below the system, where we will develop the
structures from the rough to the detail.
Pages:
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260