njmarko / web-googolplex-tx Goto Github PK

• Create frontend component
• Implement backend methods

Make modification to the class model after considering all our options.

• Finish modification of the class model

• Add component on frontend for adding users by admin.
• Add methods on backend for registering customer and salesman by admin

Implement a basic set of methods for Ticket controller. Checks if the user has the right to access the data can be added after login is implemented.

• Find all tickets
• Find one ticket
• Save one ticket
• Edit one ticket
• Find all tickets by user
• Search
• Search by user

Implement a basic set of methods for Manifestation controller. Checks if the user has the the right to access the data can be added after login is implemented.

• Find all manifestations
• Find one manifestation
• Save one manifestation
• Edit one manifestation
• Delete one manifestation
• Find all tickets for one manifestation
• Find one ticket
• Save one ticket for one manifestation and user
• Edit one ticket
• Delete one ticket
• Find all comments for one manifestation
• Find one comment
• Save one comment for one manifestation and user
• Edit one comment
• Delete one comment

Design and create REST api in SPARK. Figure out how to create different controllers for different entities in SPARK.

• Create test data in memory
• Adapt model
• Design REST api (in txt format)
• Create adequate controllers for the REST api
• Test rest api with POSTMAN (it is too slow to test it from frontend at this stage)

• Find all users
• Find one user
• Save one user
• Edit one user
• Delete one user
• Find all tickets for one user
• Find one ticket (it can call the same method as the api/manifestations/{idm}/tickets/{idt} )
• Save one ticket for one manifestation and user
• Edit one ticket
• Delete one ticket
• Find all comments for one user
• Find one comment (it can call the same method as the api/manifestations/{idm}/comments/{idc} )
• Save one comment for one manifestation and user
• Edit one comment
• Delete one comment

• Add a component for adding new Manifestation
• Make sure no manifestation takes place at the same time on the same place.
• Manifestation status should be set to Inactive when created. Admin can change it later to active.

Make initial DTO objects that are needed for communication with the frontend

• Add equivalent DTO classes for the model
• Add search parameters DTOs
  • Manifestation Search DTO
  • Ticket Search DTO
  • User Search DTO
• Add validation method to DTOs where needed

Create a hash method in User Service

• Check this method https://stackoverflow.com/questions/2860943/how-can-i-hash-a-password-in-java
• Create method for generating hash
• Create method for checking hash

• When the reservation is made add points for the customer based on the formula price_of_one_ticket/1000*133

• REJECTED Change the password in user to binary representation
• Remove redundant fields from classes
• Merge address into location

• Download all required libraries
• Change links so they reference locally downloaded libraries

Config file could contain things like port, number of results per page (if pagination is implemented) etc.
Add new task for each option as needed.

• Port number
• Number of results per page returned (Pagination)

• Start using JSON web tokens for authorization.
• Modify UserDTO so it contains the attribute String JWT
• Add support class for conversion from User to UserDTO that contains String jwt
• Save logged in user that contains JWT in local storage
• Create a support method for sending JWT with each request.

Implement a full login/register form on the frontend

• Login Form
• Login Axios
• Register Form
• Register Axios

• Add search function for all manifestations
• Add average rating for the manifestation if it is finished (don't show if it is inactive)
• Add sort functionality
• Add filter functionality

• Connect manifestations and users with tickets
• Connect manifestations and users with comments
• Save all remaining entities in files

• Implement search functionality for customer tickets
• Implement sort functionality for customer tickets
• Implement filter functionality for customer tickets
• Implement these functionalities for salesman tickets
• Implement these functionalities for admin when viewing all tickets
• Implement these functionalities for customer when viewing all his tickets

Create a regular login and logout

• Implement logic for registration
• Implement logic for Login
• Implement logic for Logout
• Put login validation in before() method for certain paths

• Add reservation functionality for any active manifestation that has available tickets
• Allow for multiple tickets to be reserved by one customer
• Add a confirmation page that asks the user to confirm the order
• Show total price and the number of tickets before the reservation is confirmed
• Calculate the discount based on the customer Type
• Decrease the number of available seats in the manifestation

• Create Entities
• Add Class methods
• Add Enum methods
• Refactor model

• Enable viewing of user profile
• Enable editing of user profile
• Create a separate page for changing passwords

Create interfaces for the required classes, and implement their functionalities. Functionalities can be found in project specification.

• Create service interfaces
• Implement service interfaces (can be done in memory in local collections until saving and loading in persistence layer is implemented)

• Create a component that displays all tickets in the system (not just reserved) to the Admin. I used the same component that customer uses with different api call

• Selecting an manifestation should take you to the detailed view for that manifestation
• Make a detailed view component for the manifestation
• Make sure the image is displayed
• Show rating if it exists (if the manifestation is finished)
• Show comments if they exist (if the manifestation is finished)
• Add basic location information for now in the format, street number , city , zip code

• Add a component that allows the salesman to edit some of the fields in Manifestation
• Add an additional option for admin where he can change the status of the Manifestation.

• Add functionality to leave a comment by Customer if the ticket is RESERVED and manifestation has ENDED
• Add option to rate the manifestation
• Make sure one customer can only add one comment and rating per manifestation, even if he has multiple tickets for that manifestation.
• Set approved status on creating to PENDING
• Make sure only approved comments are shown on the manifestation detailed view

• Add Search
• Add Sort
• Add filter
• Search should return results based on combined search criteria

• Add map to the manifestation creating screen for Salesman
• Make sure user can choose the location from the map
• Forward the exact location to the backend

• Show the most recent manifestations at the top.

Methods for saving and loading files in JSON format should be created. Gson library can be used for this.

• Create methods for saving JSON files
• Create methods for loading JSON files
• Design persistence layer and how it should be used with service layer
• Add libraries used in the project

Add a few admin users for testing.

• Add admin user (admin admin)
• Add admin user (root root)

Create the basic java project for the backend. We will use SPARK in this project.

• Create a Java project in eclipse

Don't save images in base64 encoded string. Decode the image and save it in the adequate folder.

• Image in model should contain a path to the image on the backend
• Image could be encoded in base64 format and forwarded inside a DTO object for manifestation. (alternative is to send another separate request for image)

Learn SPARK and VUE

• Watch video on SPARK Marko
• Watch video on SPARK Milos
• Watch video on VUE.js Marko
• Watch video on VUE.js Milos

• Create a component for displaying all customer tickets

• Export class diagram image
• Add progress animation gif
• Update readme.md file

• Create frontend component
• Implement backend methods

Add basic files for Vue frontend that will display something simple like all manifestations.

• Add vue files and basic structure
• Create a method that will call rest service and display manifestations
• Display manifestations as simple tables for now
• Add bootstrap

Implement changes in code from the class model design

• Add autofocus for Login
• Add autofocus for Register

Learn how to use GSON library to serialize objects and de-serialize them properly. If one member figures it out, other member will learn really quickly how it is done.

• Marko - Learn how to serialize objects with GSON and save them to file
• Marko - Learn how to de-serialize objects with GSON and load from the file
• Milos - Learn how to serialize objects with GSON and save them to file
• Milos - Learn how to de-serialize objects with GSON and load from the file

• Add option for canceling the reservation (at least 7 days before the event)
• Increase the number of available seats for the manifestation.
• Reduce the number of points for the customer based on the formula
  Formula for reducing points is: reduce_by = price_of_ticket/1000*133*4

• Develop a basic class model

• Add option for Salesman to approve comments
• Make sure customers can only see approved comments on manifestation detailed view
• Admin and Salesman can see comments of all statuses

• Create frontend component
• Implement backend methods

• Replace static collections with regular collections
• Separate each collection into DAO object
• Have one class that is responsible for loading all the collections (it should have a reference to every DAO)
• Forward these collections to the service classes constructors where they are needed

• Create frontend component
• Implement backend methods

• Add location map to the detailed view for Manifestation