Books for you

This allows us to describe taxonomic 10 hierarchies between
actors. They can be abstract, just like use cases and classes. In this case, the actor ??™ s
name is written in italics. The adjective {abstract} can optionally be denoted
behind the actor ??™ s name.
A generalization is also used to model an OR semantics between actors and a
use case. The use case change soft-drink data in Figure 3.33 has only one actor,
service system . More specifi cally, this is either the maintenance system or the
confi guration system .
An information fl ow is another relationship that is permitted between
actors. You can use an information fl ow to describe the information your actors
exchange.
Associations between actors are not allowed.
Actors can alternatively be described in text form, just like use cases ( Table 3.3 ).
This is a textual representation of the model, but it ??™ s not standardized in UML.
10 Taxonomy means dividing things into groups.
Table 3.3 Description of actors.
Name: Customer
Type: User
Description: An individual who buys a soft drink at a
vending machine.


Pages:
324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348