:Functional Requirements

:User
 All users of the software shall have the ability to create an account using email
address, password and mobile number that is used to store user data and manage user
actions to a user alias.
 The system shall ask for an email address and password for login.

 The system shall notify the user if incorrect characters are used in the email or
password fields.
 The system should notify the user if their email has already been used.
 The system should notify the user if any required fields are left empty.
 The system should not allow the user to create weak or unsecured passwords.
 Without requiring create an account, the users can view the gym's offerings
and the cost of Gym membership.
 The system must render it simple and quick to switch between the various routines in
the list.
 The system can handle your fitness-related daily, weekly, and monthly expenses.

 The system shall display full details of an exercise routine once one is selected by the
user.
 Users will be able to easily find the most recent list of workout routines uploaded by
other users according to the system's user-friendly navigation.

Admin:

 Admin will be able to manage (Add delete update view) transactions of members by
using just a unique ID. The system will make it visible when a member's status has
been modified.
 The admin can see the registration of new members in the gym as soon as they
register, and send an overview about the gym's activities and the customer's payments

Non-functional Requirements:
 Performance: The system should be capable of managing multiple users at
once.
 The system would be able to perform efficiently to any transaction in fewer
than 6 seconds.
 Reliability: To prevent inconsistent data, database update should come after
transaction processing.
 Accessibility: Since the project will be installed on a distant server, there will
be minimal disruption and high accessibility.
 Security: User ID and passwords have been implemented for security purposes
member login.
 Accessibility throughout the program is also limited based on user levels.
 Usability: On average, the number of errors made by trained users shall not
exceed three per hour of system use.