Books for you

This had been one of the goals of Ivar Jacobson when he
invented use cases back then.
Use cases, actors, and the include relationship will be described below. We will
not be looking at the ?«extend?» relationship though. It is not used in the SYSMOD
approach described in this book. I ??™ m following Martin Fowler ??™ s recommendation
for the extend relationship: ??? Just pretend it doesn ??™ t exist ??? [17].
3.5.1 Use Case
FIGURE 3-29
Example for ports.
Class Example ports
?«system?»
On-board computer
k
bc
comm
Receiver
ServerPort
Sender
:On-board
computer control
:Communication unit
Defi nition
A use case describes a coherent and targeted interaction of an actor with a
system, at the beginning of which there is a domain trigger, and at the end of
which there is a defined result of domain value.
169
A use case describes a service performed by the system for its environment. The
users of this service are actors. A use case is generally triggered by an actor. The
result of a use case is normally significant for the triggering actor (see exceptions
in Section 2.


Pages:
318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342