Functional Requirements List (Iteration 1) - djgamekid/GDP-Group-I-bearcatmanager GitHub Wiki

Project Functional Requirements: Darren Ross, Anthony Jack, Manikala Chevitipalli, Sai Achyuth Konda

Bearcat Manager – A Web application that hopes to create an application that can be used to create and manage events and allow users to get tickets to events.

The system SHALL

  1. The system SHALL allow the user to get a ticket for an event.
  2. The system SHALL allow the admin to create an event.
  3. The system SHALL allow the user to search for created events.
  4. The system SHALL allow the admin to delete events.
  5. The system SHALL allow the admin to edit events currently created.
  6. The system SHALL accept user credentials.
  7. The system SHALL allow for account creation using email.
  8. The system SHALL authenticate user credentials.
  9. The system SHALL NOT store user credentials in plain text.

The system SHOULD

  1. The system SHOULD provide some sort of feedback when the user is signing in.
  2. The system SHOULD have a QR code generated with a ticket.
  3. The system SHOULD notify the user with an email confirmation of the selected event.
  4. The system SHOULD have an on-site notification system after a user logs in.
  5. The system SHOULD be easily navigable.
  6. The system SHOULD allow users to edit their profiles.
  7. The system SHOULD allow participants to cancel the registration, freeing up the spots for others.
  8. The system SHOULD display a dashboard that hosts upcoming events and pre-selected events.
  9. The system SHOULD be able to filter events based on location and event type.
  10. The system SHOULD allow the user to submit feedback to developers.
  11. The system SHOULD allow the user to receive help on-site via chatbox.

The system MAY

  1. The system MAY play some sort of animation when logging in.
  2. The system MAY have a mobile format.
  3. The system MAY have pictures associated with each event.
  4. The system MAY need to redirect to another website when a user clicks external links.
  5. The system MAY have pictures associated with each event location.
  6. The system MAY have a trending carousel on the main page.