Abuse Misuse case - CSCI-360-2022/Software-Chasers GitHub Wiki
Abuse Case 1: Purchasing ticket with no money on card.
| Use Case Section | Comment |
|---|---|
| Use Case Name | Purchasing ticket with no money on card |
| Scope | Ticket Website. |
| Level | User-goal - the user tries to get ticket knowing there is no money on card |
| Primary Actor | User - trying to get a ticket.Card processor- checking card. |
| Stakeholders and Interests | User: trying to get free tickets.Card processor-this will affect the income |
| Preconditions | Have ticket in cart |
| Success Guarantee | Ticket is not given unless the card processor confirms payment information. |
| Main Success Scenario | Ticket not given until paid for |
| Extensions | Text given to the user on screen saying "processing payment" when a query does not yield any events. |
| Technology and Data Variations List | Card processor |
| Frequency of Occurrence | Everytime a purchase needs to be made. |
Misuse Case 1: Spam buying tickets.
| Use Case Section | Comment |
|---|---|
| Use Case Name | Spam buying tickets |
| Scope | Ticket Website. |
| Level | User-goal - putting tickets into cart |
| Primary Actor | User - a person wishing to buy an event. |
| Stakeholders and Interests | User: A registered user or guest wishes to buy events in the system. |
| Preconditions | User types information into search box and hits submit |
| Success Guarantee | The system displays a only one event in cart at a time |
| Main Success Scenario | Users are only able to purchase one ticket at a time. |
| Extensions | Text given to the user on screen showing one event in the cart at a time. |
| Technology and Data Variations List | A database that contains event info |
| Frequency of Occurrence | Every time a user wishes to buy an event. |