topanb11 / ticketbox

TicketBox

Built with:

Getting Started

Frontend

Change into frontend directory: cd frontend

Install dependencies: yarn install

Start frontend: yarn start

Backend

1. Download docker: https://www.docker.com/products/docker-desktop/
2. Open a terminal
3. Run the following:
   1. docker run --name postgres-spring -e POSTGRES_PASSWORD=admin -d -p 5432:5432 postgres:alpine
   2. docker ps
   3. docker exec -it <container-id from the docker ps command> bin/bash
   4. psql -U postgres
   5. CREATE DATABASE springdb;
   6. \c springdb
4. Database is now fully setup
5. Change into backend directory: cd backend
6. Run the following:
   1. brew install maven
   2. mvn spring-boot:run
7. Server should now be started on localhost:8080

Screenshots

Home Page

Movies Page

Seat Selection

Guest Checkout

Registration

Log In

ticketbox's Issues

#30 - GET seats by showtime

Systems Activity Diagram

POST /USER/LOGIN

#27 - POST cancelling a ticket from homepage

SQL statement + add movie cover column

POST /USER/CREATE

Movies Page

Movie page after searching

Requirements:

• Search bar works as intended
• List of all movies matching title show up (Case-insensitive and as long as an instance of the word matches)
• Movies are listed in list format

Annual Payment required notification for RU

On log in, check "validUntil" property for RU, and if its passed then prompt user to pay again.

Design Class Diagrams

• A class diagram without attributes and behavior that only shows the class name and
  the relationships among them. The purpose of this diagram is to show the entire
  system in one page. Please make sure lines never cross each other and the diagram
  is clear and easy to read
  NOTE:
  • You class diagram should be traceable in your use-case scenarios. Mark will
  be deducted for class that are not traceable in the use-case diagram.
  • In your class diagram you don’t need to show Java library classes such as
  Exceptions, Buttons, String, ArrayList, etc.
  • Make sure clearly identify the stereotypes of your classes (such as
  <>, <>, <>
  • Make sure the multiplicity/cardinality is properly indicated.
• A class diagram with no relationships, only showing the class details: attributes and
  behaviours. This diagram can be organized in multiple pages. Please try to keep
  them well organized, clear, and easy to read.
  Note: You don’t need to show constructor/destructor, getters/setters

POST /USER/REACTIVATE

#28 - POST user login info

GET /SEATS/BY/SHOWTIME

Package Diagrams

#31 - POST payment info

GET /MOVIES/ALL

check if showtime < 72 hours before canceling ticket

System Interaction Diagrams

System interaction diagrams for at least four major and important use cases in this system
(each team member must take responsibility for one and his/her name must appear on the
related page).

Must create four sequence diagrams

• Buying a ticket (Topan)
• Cancelling a ticket (Jason)
• Logging in (Topan)
• Registering for an account (Jason)

POST /CANCEL/TICKET

POST /CANCEL/ORDER

payment class + strategy pattern

#29 - POST register user info

System Use Case Diagram

Implement POST reactivate api

Deployment Diagram

Detailed "Scenario" for each use case

A detailed “Scenario” for each use case, having all candidate objects underlined, and all
candidate operations underlined (use single-underline for objects and double-underline for
operations)

Seat Selection

#26 - GET all movies on homepage

#21 - Link movie list page to seat selection

• After pressing VIEW SEATS, user is sent to seat selection page
• Seats are for selected movie and showtime

State Transition Diagrams

• Ticket Object (Dimitar)
• Payment Object (Ajay)
• Another Use Case: Seat Object (Dimitar)
• Another Use Case (Ajay)

POST /CHECKOUT