Operation Contracts - CSCI-360-2022/Team-Too GitHub Wiki

Operation: StateDatePicked, EndDatePicked

Cross References: UC2: Fan looks for group
Preconditions: Fan is on website

Postconditions:

  • Events that followed under event returned.

Operation: FilterBadge

Cross References: UC2: Fan looks for group
Preconditions: Fan on website.

Postconditions:

  • Event gets filtered and returned.

Operation: selectEvent

Cross References: UC4: Student buys tickets, links to Account

Preconditions: Eventgoer is on website

Postconditions:

  • Ticket gets selected

Operation: buyTicket()

Cross References: UC1: Actor buys tickets

Preconditions: Eventgoer has selected the event and number of tickets they wish to purchase

Preconditions:

  • The user is able to use their Stripe account to purchase the correct number of tickets

  • The user is emailed an electronic receipt of proof of their purchase

  • The system's catalog of tickets is adjusted for the amount of tickets remaining.

Operation: selectSeat(seatNum)

Cross References: UC3: Actor wants to buy specific seats for tickets

Preconditions: Eventgoer has selected an event, and has selected the number of tickets they wish to purchase.

Postconditions:

  • The user has been returned a seating map of the seats currently available for reservation
  • The user makes a selection of seats for reservation, and the system reserves them for the ticket holders

Operation: Sanitize(SEByDate(startDate,endDate) or Santized(SEByCateogry(CategoryTxt))

Cross Reference: Abuse Case Person Injects SQL

Precondition: SEbyDate() and SEByCategory*( must be submitted first

Postconditions:

  • It'll scrub for any usage of SQL injection.
  • We found that by using AWS Amplify, SQL injections would not be an issue.

Operation:finalizeOrder(totalCost,tickets)

Cross Reference: Misuse Case person accidentally buys too many tickets.

Precondition: must have tickets

Postconditions:

  • confirmation() is sent back to cart, confirming order.

Operation: confirmOrder(totalCost)

Cross Reference: UC4: Student buys tickets, links to account.

Preconditions: eventgoer has finished adding items to the cart, and is ready to complete purchase

Postconditions:

The user is able to use their Stripe account to purchase the correct number of tickets

The user is emailed an electronic receipt of proof of their purchase

The system's catalog of tickets is adjusted for the amount of tickets remaining.

The Google calendar sends a confirmation that the calendar has been updated.

Operation: completePurchase(totalcost, Tickets)

Cross Reference: UC4

Preconditions: User has confirmed their purchase.

Postconditions: confirmation is sent to sign into the google calendar

Operation: signIn()

CrossReference: UC4

Precondition: User has completed purchase, and has a google account.

Post condition: The system is ready to update the calendar

Operation: CalendarUpdate()

Cross Reference: UC4

Preconditions: User has signed into their Google account.

Postconditions: The calendar is updated, and confirmation is sent to the user.

⚠️ **GitHub.com Fallback** ⚠️