Student DoHomework Textual Use Case Description Example 1. Passenger PurchaseMultiCard PurchaseSingleTicket > CollectMoney NoChange > Cancel Two use cases are related by an include relationship, if one of them includes the second one in its own flow of events. The direction of a > relationship is to the using use case (unlike the direction of the > relationship). > behavior is factored out for reuse, not because it is an exception. > relationship represents common functionality needed in more than one use case. Passenger PurchaseTicket > OutOfOrder TimeOut Cancel NoChange > relationships model exceptional or seldom invoked cases The exceptional event flows are factored out of the main event flow for clarity The direction of an > relationship is to the extended use case Use cases representing exceptional flows can extend more than one use case. Special requirements: None.Įxtends Relationship To represent seldom invoked use cases or exceptional functionality Includes Relationship To represent functional behavior common to more than one use case. Passenger inserts money, at least the amount due 4. Ticket Distributor displays the amount due 3. Passenger selects the number of zones to be traveled 2. Entry condition: Passenger stands in front of ticket distributor Passenger has sufficient money to purchase ticket 4. Passenger Textual Use Case Description Example PurchaseTicket 1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |