Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Use case diagrams @myassignmenthelp


Published on

myassignmenthelp is leading assignment help provider for use case diagrams. whenever any one needs help with any diagram related assignments feel free to get in touch with us

Published in: Software
  • Be the first to comment

  • Be the first to like this

Use case diagrams @myassignmenthelp

  1. 1. Use Case Diagrams
  2. 2. Use Case Diagrams • In order to signify external behavior • Actors signify functions, that's, a kind of user of the system Passenger PurchaseTicket
  3. 3. Use Case Diagrams • Use cases signify the sequence associated with interaction with regard to a kind of functionality, summary associated with scenarios • The use case model may be the set of all use cases. It's a total explanation from the functionality of the system and its environment Passenger PurchaseTicket
  4. 4. Actors • An actor models an external entity that convey using the system: – User – External system – Physical environment • An actor has a unique name as well as an optional explanation. • For Examples: – Passenger: A person in the train – GPS satellite: Provides the system along with GPS coordinates Passenger
  5. 5. Use Case The use case signifies the class of associated with functionality supplied by the actual system as an event flow. The use case includes: • Unique name • Participating actors • Entry conditions • Flow associated with events • Exit problems • Unique needs PurchaseTicket
  6. 6. Use Case Diagram: Example Name: Purchase ticket Participating actor: Passenger Entry condition: • Passenger standing in front of ticket distributor. • Passenger has sufficient money to purchase ticket. Exit condition: • Passenger has ticket. Event flow: 1. Passenger selects the number of zones to be traveled. 2. Distributor displays the amount due. 3. Passenger inserts money, of at least the amount due. 4. Distributor returns change. 5. Distributor issues ticket.
  7. 7. The <<extends>> Relationship • <<extends>> relationships signifies exceptional or even seldom invoked cases. • The exceptional event flows are factored out of the main event flow for clarity. • Use cases signifies exceptional flows can extend more than one use case. • The actual path of the<<extends>> relationship is to the extended use case Passenger PurchaseTicket TimeOut <<extends>> NoChange <<extends>>OutOfOrder <<extends>> Cancel <<extends>>
  8. 8. The <<includes>> Relationship • <<includes>> relationship signifies behavior that's factored from the use case. • <<includes>> is actually factored away with regard to reuse, not really since it is definitely an exception. • The actual path of the <<includes>> relationship would be to the actual utilizing use case (unlike <<extends>> relationships). Passenger PurchaseSingleTicket PurchaseMultiCard NoChange <<extends>> Cancel <<extends>> <<includes>> CollectMoney <<includes>>
  9. 9. Use Cases are useful to • Identifying needs – New use cases usually create new specifications because the system will be assessed as well as the layout will take condition. • Interacting along with customers – Their notational simplicity can make use case diagrams a good way with regard to developers to communicate with clients. • Generating test cases – The collection of scenarios for a use case may suggest a suite associated with test cases for those scenarios.
  10. 10. Use Case Diagrams: Summary • The use case diagrams symbolize external behavior • The use case diagrams are helpful because an index to the use cases • The use case explanations supply meat associated with model, not the use case diagrams. • All use cases need to being explained for the model to be useful.
  11. 11. Thank You Email Us at :