An airbag that unfolds several
minutes after its triggering is absolutely useless.
We ??™ ve already collected requirements, including functional requirements, such
as rent car without staff assistance . Use cases help us refi ne these requirements
and describe them in greater detail. A use case itself is not a requirement.
Ours is a top-down approach, which means that we can achieve a broad collection
of requirements in an early project phase. It also helps us obtain a full
picture rather early. This provides us with a good basis, e.g., for cost and time estimates,
in an early project phase [57].
65
One of the most important benefi ts of our approach is scalability. The depth of
details of our model can be adapted to the project. Each step is realizable and achievable,
from a superfi cial analysis to get a rough insight, e.g., for a feasibility study, to
very detailed executable models. This allows us to further detail a superfi cial analysis
model at a later point in time. And a very detailed model can appear like a super-
fi cial analysis model in suitable diagram views.
Pages:
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166