nilemekci / book_store Goto Github PK

As a manager, I want to be able to perform CRUD operation of my genre endpoints, so that admins can add, update and list writers.

Acceptance Criterias:

• Admins can be able to add new genres to the server which are associated with books.(Genre name cannot be null, blank, more than 80 characters and smaller than 3 character. )
• Admins/Users can be able to list genres by id.
• Admins/Users can be able to list genres by name.
• Admins/Users can be able to list all the genres in the server.
• Admins can be able to update a genre. (Genre name cannot be null, blank, more than 80 characters and smaller than 3 character)
• All the validations etc. have to be done in order to say this task is DONE

As a manager, I want to be able to perform CRUD operation of my writer endpoints, so that admins can add, update and list writers.

Acceptance Criterias:

• Admins can be able to add new writers to the server.
• Admins/Users can be able to list writers by id.
• Admins/Users can be able to list all the writers in the server.
• Admins can be able to update a writers.
• All the validations etc. have to be done in order to say this task is DONE
• Be careful make logical decision while determining unique writer in your system.

As a manager, I want to be able secure while using my product endpoints, so that I can manage roles and user sessions with ease.

Acceptance Criterias:

• User CRUD operations

  • Get user by ID
  • Get all users
  • Register/sign up to the system (add new user) Users have to login with email and password
  • Passwords have to be encrypted
  • Login to the system
  • Delete user (be careful not to break foreign key interactions of users)
  • User token have to expire after 30 minutes later

• Method based role structure implementation

  • Users cannot delete anything except their evaluations
  • Admins are able to delete everything in the system
  • Whole security operations have to be performed Spring Security 3.0 JWT you are free to use any external dependencies while implementing the structure

As a manager, I want to be able to perform CRUD operation of my book services, so that admins can add, update and list books.

Acceptance Criterias

• Admins can be able to add new books to the server.
• Admins/Users can be able to list books by id.
• Admins/Users can be able to list books by ISBN.
• Admins/Users can be able to list all the books in the server.
• Admins can be able to update a book.
• Admins cannot be able to update ISBN of a book.
• All the validations etc. have to be done in order to say this task is DONE