60 likes | 82 Views
This article explores the use case narratives of a retail sales system, including pricing, payment options, discounts, and decision-making. The author also discusses UML mechanisms such as branch and fork/join in activity diagrams, specialization of classes, regions in sequence diagrams, and states.
E N D
UML - Mechanisms for Variations by Brian Lawler Brian.Lawler@JHU.edu
Use Case Narratives Retail Sales System Purchase Items Use Case Begins: Ends: Base Case: Present items for pricing Total bill Pay bill Variations: Pay by cash, check or credit Discount for multiple items Decide not to buy an item <<System>>Retail Sales System Purchase Items Customer Brian.Lawler@JHU.edu
Branch and Fork/Join on Activity Diagrams Brian.Lawler@JHU.edu
Specialization of Classes Brian.Lawler@JHU.edu
Regions on Sequence Diagrams Brian.Lawler@JHU.edu
States – incl. Forks/Joins, Concurrency, etc. Brian.Lawler@JHU.edu