g., initial node, decision).
Model use case
flows
Use cases
[detailed]
Requirements
Use cases
[essential]
89
We achieved these results relatively quickly. Here, in this fi rst round, the iterative??“
incremental approach does not demand completeness either. It is suffi cient to
have found the core use cases. As soon as their details have been analyzed we can
also determine the remaining use cases easily.
In our analysis we normally spend the best part of our time describing
detailed fl ows for use cases. We are ready to start this job now. Starting from the
abstract essence description, we analyze and model fl ow details, exceptions, and variants.
This requires many domain details. You will come across open issues that cannot
be solved without the help of a domain expert. It is therefore always a good idea
to have access to appropriate stakeholders in this phase to clarify detail questions
in time.
We start our analysis by selecting a use case. If you haven ??™ t modeled use case
fl ows for the system yet, you should select a use case that contains the central
domain logic, and covers as large a system area as possible, and has a known fl ow.
Pages:
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210