Books for you

If there is an interest in the details
of a model element we simply ??? zoom in. ??? This way we can make complex models
manageable. The modeler won ??™ t be overwhelmed by the model ??™ s intricacy and they
won ??™ t get lost in the details either; instead they can work on the details level they
need for their current task. Grady Booch calls this Illusion of Simplicity [6].
In Sections 2.4.1??“2.4.6, we will identify use cases, immerging into each of
them, and then analyze them from the superfi cial use case essence all the way to
the detailed fl ow description. The individual steps involved in use case modeling
are shown in Figure 2.31 . It is the detailing of the step, model use cases , from
Figure 2.1 .
2.4.1 Identify Use Cases
Identifying use cases is shown in Table 2.9 .
Our approach is service-oriented, which means that we fi rst look for the services
our system is to provide. The only thing of interest for the actors is actually
what functions the system offers or the services that will be requested from the
system.


Pages:
143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167