Use Case view - CSCI-360-2023/smh GitHub Wiki
Fully Dressed Use Case #1

Fully Dressed Use Case #2

Discussion: The Use Case View focuses on the "Checking Availability" and "Purchase Ticket" functionalities, which are pivotal to our application's operation. These use cases have been elaborated to cover all the necessary steps and alternatives, offering a comprehensive perspective of the system's capabilities and interactions with its users.
Motivation: Our Use Case View is driven by the need to provide a system that is:
- Reliable, ensuring that ticket availability is accurately reflected in real-time to avoid overbooking.
- Secure, guaranteeing that transactions are processed safely and users' data is protected.
- Adaptable, allowing for easy updates and changes to the event catalog or ticketing policies without disrupting the overall system performance.
By providing a detailed discussion and strong motivation for our Process and Use Case Views, we aim to build a robust foundation for the development, scalability, and maintenance of the Sports Event Ticketing App. This approach aligns with our commitment to delivering a quality service that meets the needs of both event organizers and attendees, ensuring a seamless ticketing experience.