1 / 20

BTS330: Business Requirements Analysis using OO

BTS330: Business Requirements Analysis using OO. Lecture 8: Use Cases and Scenarios. Agenda. Looking for Use Cases Notes on Use Case Diagrams Scenarios. Looking for Use Cases. We used a table with three columns: Actor Function performed by actor

mercedes-holman
Télécharger la présentation

BTS330: Business Requirements Analysis using OO

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BTS330: Business Requirements Analysis using OO Lecture 8: Use Cases and Scenarios

  2. Agenda • Looking for Use Cases • Notes on Use Case Diagrams • Scenarios

  3. Looking for Use Cases • We used a table with three columns: • Actor • Function performed by actor • Use Case that contains (or carries out) the function

  4. Looking for Use Cases

  5. Actor • A person, software system, department, role, device…etc…. outside of the system that interacts with the system

  6. Use Case Diagram System Boundary Association Actor Use Case

  7. Agenda • Looking for Use Cases • Notes on Use Case Diagrams • Scenarios

  8. Notes on Use Case Diagrams • Rational Rose Structure • Put your business area in a “package” • Segment your business area further as required—each “segment” should be a package within the business area package • Use Cases Included • If only actors outside of your business area are accessing a use case then the use case probably does not belong in your business area

  9. Notes on Use Case Diagrams • Use Case Naming • Name your use cases so that the verb comes first: • “Manage Prices” • “Generate Revenue Report” • “Search Solution”

  10. Agenda • Looking for Use Cases • Notes on Use Case Diagrams • Scenarios

  11. Use Case v.s. Scenario • Use Case • “a discrete stand-alone activity that an actor can perform to achieve some outcome of value” • “might encompass a number of similar tasks having a common goal” • “a collection of related usage scenarios” Text, p134

  12. (Usage) Scenario • A specific instance of a use case • One “path” through the use case logic

  13. Example: Natty Attire

  14. Usage Scenarios • Add Reservation • No Alteration Required • Alteration Required • Update Reservation • Cancel Reservation

  15. Usage Scenarios • Add Reservation, no alteration required • Provide customer information, specify garment, dates, occasion. • Collect deposit. • Create reservation record

  16. Add Reservation (no alteration) Precondition: system has authenticated actor.

  17. Usage Scenarios • Add Reservation, Alteration Required • Provide customer information, specify garment, dates, occasion. • Specify alteration information • Collect deposit. • Create reservation record

  18. Add Reservation (alteration) Precondition: system has authenticated actor.

  19. Update Reservation Precondition: system has authenticated actor.

  20. Cancel Reservation Precondition: system has authenticated actor.

More Related