0% found this document useful (0 votes)
12 views30 pages

Gym Management System Project Overview

Uploaded by

Uttam Kumar Sah
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
12 views30 pages

Gym Management System Project Overview

Uploaded by

Uttam Kumar Sah
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Tribhuvan University

Faculty of Humanities and Social Sciences


Model Multiple College JanakpurDham-4

Supervisor’s Recommendation

I hereby recommend that this project prepared under my supervision by Uttam Kumar
Sah & Pujan Kumari Mandal entitled “GYM MANAGEMENT SYSTEM” in partial
fulfilment of the requirements for the degree of Bachelor of Computer Application is
recommended for the final evaluation.

…………………

SIGNATURE
Mr. Ravi Roshan

SUPERVISOR
Class Teacher
Humanities and Social Science
Model Multiple College-JanakpurDham-4 (Nepal)

i
Tribhuvan University
Faculty of Humanities and Social Sciences
Model Multiple College JanakpurDham-4
LETTER OF APPROVAL
This is to certify that this project prepared by Uttam Kumar Sah & Pujan Kumari
Mandal entitled “GYM MANAGEMENT SYSTEM” in partial fulfilment of the
requirements for the degree of Bachelor in Computer Application has been evaluated. In
our opinion it is satisfactory in the scope and quality as a project for the required degree.

SIGNATURE of Supervisor SIGNATURE of Principal

……………………Mr. Ravi Roshan Class …………………….. Mr. Dharmendra


Teacher ThakurPrincipal

Humanities and Social Science Humanities and Social Science

Model Multiple College-JanakpurDham-4 Model Multiple College-JanakpurDham-4

(Nepal) (Nepal)

…………………….. SIGNATURE of ......…………………. SIGNATURE of


Internal ExaminerInternal Examiner External Examiner External Examiner

ii
ABSTRACT

The Gym management system is an service that can be setup for your gym to help
manages Classes, memberships, receive payments (merchant and cash), keep track
with detailed statisrices , customer management, surveys and it even has an stores so
you can sell products to your customer. The usage of the traditional method is not
efficient because the method consumes time whenever an updated or searching of gym
member record is performed. Therefore, this system is proposed to solve the stated
problem. Besides, this system is also proposed to enable the gym members or non-
members to perform either registration, reservation or purchased activity on any of the
gym services without have to come to the counter. The development of the proposed
system has been planned thoroughly by referring to the project’s main objectives. The
methodology that has applied during the development of the project is the Agile
methodology.

iii
ACKNOWLEDGEMENT

We are very thankful to Mr. Er. Binay Kumar Yadav (Lecturer, Bachelors in Computer
Application Department) to give us the opportunity to build this project. We are also
very thankful to our teacher guide because without his guidance it would not be
possible to build this project.
Last but not the least we would like to thank the entire Model Multiple College,
Bachelors in Computer Application (BCA) Department for allowing us to proceed with
the project.

iv
TABLE OF CONTENTS

CHAPTER NO. TITLE PAGE NO.

iii
CERTIFICATE APPROVAL

ABSTRACT iii

ACKNOWLEDGEMENT iv

1 INTRODUCTION

1.1 Introduction 1
1.2 Problem statement 1
1.3 Objectives 1
1.4 Scope and Limitation 2
3
1.5 Methology 3
1.6Report Organization 3
2 Background study and literature 4
2.1 Background Study 4
2.2 Literature Review 4-5
3 System Analysis 5
3.1. System Analysis 6-7
3.1.1 Requirement Analysis 7-8
[Link] Analysis 9
ER Digram
10
10-11
Process Modelling DFD
3.2System Design 11
3.2.1 Architectural Design 11
12
3.2.2 Database schema design 12-14
Interface Design(UI/UX) 14
15
Physical DFD
15
3.3 Algorithm deatils
4 Implementation and Testing 16

4.1 Implementation 16

v
Tools used 16
Implementation details of mF Modules 17-18
Testing 18
Test case for unit testing 19
Test cases for system testing 19
5 Conclusion and future enhancement 20
Conclusion 20
Lesson learnt/ Outcome 20
future enhancement 20
21
APPENDIXS
REFERENCES 22

vi
CHAPTER-1

INTRODUCTION

1.1 INTRODUCTION

A fully functional project based on Gym Management System Project which uses PHP
Language with MySQL Database. It has a number of features that will allow users to
manage gym memberships, services, and daily records. This web application’s concept is
all clear. It’s the same as real-life scenarios and well- implemented on it. the system helps
to keep track of customers and track activities with respect to their chosen services. Also,
the system displays all the available service packages. In addition, the system allows online
registration for the customers. Evidently, this project contains an admin panel with
customer and staff panels.
The Gym Management System is a comprehensive web application designed to streamline
and automate the operations of a fitness center or gym. It provides gym owners, staff
members, and clients with a user-friendly platform to manage various aspects of their
fitness journey.

With our Gym Management System, you can efficiently handle membership management,
class scheduling, trainer assignments, billing and payments, attendance tracking, and much
more. The system is built using PHP, a popular server-side scripting language, known for its
flexibility and wide community support.
The Gym Management System is a powerful web-based application that allows gym
owners, staff members, and clients to efficiently manage various aspects of a fitness center.
This system leverages the capabilities of the Apache Server, widely used and highly reliable
web server software.

1.2 PROBLEM STATEMENT


Presently, Gym is still using the manual method in their gym’s management. The

registration of new members is done by filling out registration form paper. The

management staff also keep their members’ record by using papers and files, despite

the increasing number of the gym’smember. The execution of the traditional method is

7
not efficient because it will lead to difficulty for the staff in order to keep track of their

members’[Link] will also complicate the staff during membership renewal process as

they must search for the files of respective members to make updates. The same

procedures also occur for the personal trainers’services where the process of booking a

personal trainer must be done manually at the counter as booking system is not

provided by the management staff. Overall, the manual management system that is

being used by the gym is currently not efficient as it did not ease to gym management

into a seamless operation. Due to the ineffective operations, a lot more procedures are

taken in order to perform any process while it can be resolve easily using appropriate

and better system.

1.3 OBJECTIVES
• To developa web-based system to replace the manual(paper-based) system used by

the gym’s management.

• To enable gym members to select, self-book and communicate directly to their

personal trainers through the management system.

• To enable the gym management to add, edit, delete the membership details, gym

details, trainer details, health product details, payment details and others.

• To generate the monthly usage and income report.


.
1.4 Scope and limitation
Scope
The web-based system is developed to solve the issue of ineffective and inefficient

management for Gym. It is improvement process in terms of management whereas

previously the gym manages the membership registration by paper-based and is

transform into a web-based system. By using the web-based system, all members’record

can be kept digitally and securely. It will also ease the management staff if there have to

8
do up dates as they can look for respected members’ record easily through the system.

The system also will be developed with purpose to include all services provided by the

gym, therefore members of the gym can reserve personal trainers directly via the

management system without have to refer to the management staff like previously. Any

payment transaction such as purchases of health supplement or membership renewal

payment also can be done through the system. Generally, the development of the web-

based system will totally transform the old poor management system into a new system

which will ease the gym management for a better and seamless operation.

Limitation

• Purchasing, setting up, and customizing a gym management system can be


expensive, especially for small gyms


• with limited budgets.

• Advanced features may require staff training, and test tech-savvy employees might
struggle with operating the sytem.

• Many systems lack flexibility, meaning they may not meet the unique needs of
specific gyms without costly customization.

• Storing updates, maintenance, or unexpected bugs cause the sytem to be temporarily


unavailable.

• Difficulty in integrating the system with third-party apps, payment gateways, or


existing tools can limited its effectiveness.

• Subscription fees for web –based systems, updates , and technical support can
increase the operational expenses over time.

• Staff or members accustomed to manual process may resist transitioning to a digital


system.

9
10
1.5 Development methodology
1.5.1 WaterFall Methodology
Many consider the waterfall method to be the most traditional software
development method. The waterfall method is a rigid linear model that consists
of sequential phases (requirements, design, implementation, verification,
maintenance) focusing on distinct goals. Each phase must be 100% complete
before the next phase can start. There’s usuallyno process for going back to

modify the project or direction.

Fig:1.5.1 WaterFall Methodology

Report Organization

This report document contains five chapter including this chapter [Link] two
defines and described Background study and Literature review. Chapter three
present the System Analysis, System Designed, System Requirement Analysis
including uses of Algorithms. Chapter four presents the Implementation, Testing
are explained. In chapter five, Conclusion, lession learnt & future Recommendation
are explained.

11
CHAPTER-2
BACKGROUND STUDY AND LITERATURE REVIEW

2.1 BACKGROUND STUDY

A background study is a crucial components of any project, research, or report. It


provides a foundation by examining the context, existing knowledge, and previous
work related to a specific topics or problem. The process typically involves the
following components:
 Login: Customer easily login who already registered.

 Sign up: New Customer their signup account with suggested


docs& necessary details.
 Member Details: In member detail we store all the details of
the customer, both new and existing customer.
 Evaluate sources: E nsur e a ll info r mat io n co es fr o m
r e lia ble a nd up - t o - dat e so ur ces.
 Organize the Data: Group information into logical section
based on thems or chronology.

2.2 Literature Review


The review and comparison based on existing or similar system to the proposed

system. The study is done in many aspects to help provide a clear view of the

proposed system. Studies related to the existing system is done based on various

sources, such as articles, journals, websites and manual books. Besides, limitation of

the existing systems is also included by showing comparison between the existing and

proposed systems.

12
CHAPTER-3
SYSTEM ANALYSIS & DESIGN
3.1 System Anaylsis

System Analysis for Gym mangement System involves the process of understanding,
modelling, and desiging the various components and functionalities of the system.
Here’s a step-by-step breakdown of how system analysis might be conducted for such
s system:

Problem Definition
It is celar and concise statements that identifies the specific issues or challenge that
a project, research, or system is attempting to address. It sets the foundation for
understanding the scope and direction of the work.

2. Requirements Gathering

 A central database that’s store all information

 Identify what users or stakeholders need from a system, product, or project.



 Collecting quantitative or qualitative data through surveys, interviews ,
observation, or experiments.

 Assembling materials, personnel, or tool required for a project.

3. Modeling:

Create various models to represent the system:


 Use Case Diagrams: Identify user roles (e.g., member, administrators)and the
actions they can perform.
 Data Flow Diagrams: Show how data (e.g., register, membership) flows
within the system.
 Entity-Relationship Diagrams: Define the data entities (e.g., users) and their
relationships.
 Sequence Diagrams: Illustrate the interactions between users and the system
during various scenarios.

13
4. Analysis of Requirements

Analyze the gathered requirements to ensure they are complete, consistent, and
feasible. Address any conflicts or ambiguities.

5. Documentation

Create detailed documentation, including system requirements


specifications, architectural diagrams, and user manuals.

6. Testing and validation


 Develop a testing strategy to ensure the system function correctly and
reliably.
3.1.1 Requirement Analyis

Requirement Analysis for the web-based project is divided into two catagories. They are:

i. Functional Requirement

ii. Non-Functional Requirement

I Functional Requirement

Functional Requirement are those requirements that are used to illustrate the internal
working nature of the system, the description of the system, and explanation of each
subsystem. It consists of what task the system should perform, the processes involved,
which data should the system holds and the interfaces with the user. The functional
requirements identified are:
a. Customer's registration: The system should allow new users to register
online and generate membership card.
b. User logins: The system provides facility to the user to login into the system

II Non-Functional Requirement

It describes aspects of the system that are concerned with how the system provides the
Non-functional requirements. They are:
a) Security

The subsystem should provide a high level of security and integrity of the data held

14
by the system, only authorized personnel of the company can gain access to
the company’s secured page on the system and only users with valid password
and username can login to view users page.
b) Performance and Response time

The system should have high performance rate when executing users input and
should be able to provide feedback or response within a short time span
usually 9: seconds for highly complicated task and 2: to 29 seconds for less
complicated task.
c) Error handling
Error should be considerably minimized and an appropriate error message that
guides the user to recover from an error should be provided. Validation of users
input is highly essential. lso the standard time taken to recover from an error
should be around 10 second.

a. Availability

This system should always be available for access at 6am to 12 am 365 days.

b. Case of use

Considered the level of knowledge possessed by the users of this system, a


simple but quality user interface should be developed to make it easy to
understand and required less training.

Log
in GYM
U ADMIN
S MANAGEM
E
user-case diagramsENT
R
SYSTEM

15
Feasibility Analysis

Feasibility study is made to see if the project on completion will serve the purposeof
the organization for the amount of work, effort and the time that spend on it.
Feasibility study lets the developer foresee the future of the project and theusefulness.
A feasibility study of a system proposal is according to its workability, which is the
impact on the organization, ability to meet their user needs and effective use of
resources. Thus when a new application is proposed it normallygoes through a
feasibility study .The document provide the feasibility of the project that is being
designed and lists various areas that were considered very carefully during the
feasibility study of this project such as Technical, Economic and Operational
feasibilities..
i) Technical Feasibility

The system must be evaluated from the technical point of view first. The
assessment of this feasibility must be based on an outline design of the system
requirement in the terms of input, output, programs and procedures.
Havingidentified an outline system, the investigation must go on to suggest the
type of equipment, required method developing the system, of running the system
once it has been designed.
ii) Operational Feasibility
The proposed project is operational feasible this webpage is flexible with aI the
present exisiting system. This application can be run on aI platform such as Mac,
Windows, LINUX. The implementation of this application is also very easy and
can be updated and modified according to need after some time.
iii) Economic feasibility

The developing system must be justified by cost and benefit. Criteria to ensure
that effort is concentrated on project, which will give best, return at the earliest.
One of the factors, which affect the development of a new system, is the cost it
would require.
.

16
Data Modelling : ER-Diagrams

An entity-relationship model describes inter-related things of interest in a specific


domain of knowledge. An ER model is composed of entity types and specifies
relationships that can exist between instances of those entity types.

Fig:3.1.3 ER Diagrams

Process Modeling: Data Flow Diagrams(DFD)

When the application will be started, the login interface will appear. User have to login
to the application using their email id and password in case if user is new to application
or is not the member of the application then he/she have to signup first by filling up the
necessary details mentioned on the signup interface. Only after that one will be able to
take benefits or be able to use the application in future.

Fig 3.1.4 DFD

17
b. System Design
System design is a critical phase in software development where the overall structure
and organization of a software system are planned in detail. It involves translating the
requirements gathered during the earlier stages of analysis and design into a structured
andorganized design.t encompasses various aspects such as architectural design,
database schema design, interface design, and physical data flow diagrams (DFD).
Here's anoverview of each component:

Architectural Design

Fig: 3.2.1 Architectural design

18
Database Schema

Database Schema

Interface Design (UI/UX)

HOMEPAGE

SIGN UP PAGE

19
LOGIN PAGE

Trainer Register

20
Physical DFD

Physical DFD goes one step deeper than level one DFD where user account is created
when user enter all details correctly and user data is stored in the database. User could
have logged in to the system after successfully creation of an account and could have
perform the membership of Gym.

physical DFD

Class Diagram

Fig: 3.2.5 class diagram

21
3.3 Algorithm details

• Define a function that takes the sorted list and the target criteria as
parameters. This function will perform the binary search.
• Initialize two pointers, one at the beginning (left) and one at the end(right) of
the sorted list.
• Calculate the middle index between the left and right pointers.
• Compare the item at the middle index with the target criteria:
 If the item matches the criteria, return it (e.g., the available seat
or train schedule).
 If the item is less than the criteria, update the left pointer to the
middle index + 1 and repeat the search in the right half of the
list.
 If the item is greater than the criteria, update the right pointer
to the middle index - 1 and repeat the search in the left half of
the list.
• Continue this process until the item is found, or the search range
becomes empty (left pointer is greater than the right pointer). In the
latter case, indicate that there is no match.

22
CHAPTER 4

IMPLEMENTATION AND TESTING

4.1 Implementation

In the first phase, data were collected. Data collection took longer time than other
phases. Itwas the critical stage in project,s development. All the physical design of the
project is turned into working computer code .Many tools and technologies that were
uilized to develop the system were discussed in the preceeding chapter.

Tools Used

The various system tools that have been used in developing both the front-end and
back-end of the project are being discussed in this chapter.
Front-end

Bootstrap, HTML5, CSS3, and JavaScript are used for developing the front-end.

HTML5 (Hyper Text Markup Language)

HTML is used for structuring webpage design in our project and it provides us with
overallskeleton structure of webpage. HTML is the main presentation language of our
project because it helps us to show the structure of our page in the browser which helps
us to debugeasily and efficiently.
CSS3 (Cascading Style Sheets)

CSS is used to style the HTML document in our project. It is used to make our
webpagesresponsive however bootstrap is used to make our webpages responsive.
Bootstrap

Bootstrap is the most popular HTML, CSS, and JavaScript framework for
developingresponsive, mobile-first websites.
Backend

The backend is implemented using PHP and MySQL. MySQL used to design the
database.

23
Implementation Details of Modules

The proposed system is composed of different module such as user module, admin
module, login module. In register and login the system and can perform test and can
get logout from the system likewise admin also can login the system and manage
user and can logout from the system and in login module only registered user
canlogin the system.
• User Module(Admin)

In user module account is created by filling the form detail which includes the field
like name, username, email name, mobile number, gender, password, confirm
password. While filling the input field user must fill the all data in the input field
so thatit would not throw an error message. User data is stored in the database
after filling correct details in the registration form while creating an account. After
successfully creating an account user can login to the system.
• Login Module

In Login Module user can login to the system after successfully creating an
account. Login module consist of two field such as email field and password field.
User is only logged in to the system when email and password entered by user is
matched with database email and password. In this module user can login through
email and password. User must enter correct email and password to login into the
system. If user enter wrong email and password, then it throws an error message
and in order to login in the system user must enter correct email and password.

4.2 Testing

On the basis of the software requirement specification document, testing was


performed to investigate and validate the behaviour of a fully intergrated
software product. Before deploying an application or website, it must be
throughly tested. As a result, this application’s test cases were written. Some of
the types of testing that wedid were described below.

24
4.2.1 Test cases for Unit testing

Focuses on individual software units, groups of related units.

 Units- smallest testable piece of software.

 A unit can be compiled/assembled/ linked/loaded; and put under


a test harness.

 Unit testing done to show that the unit does not satisfy the
application and /or its implemented software does not much the
intended structure.

Test Case for System Testing

Check system behavior,

 If the site launches properly with all the relevant pages, features and logo.

 If the trainer can register/login to the site.

 If the main features, such as deposit, withdrawal, fund transfer, transaction


detail, balance inquiry, and so forth, function as expected.
 If the site works properly in the newest versions of all major browsers.

 If the content of pages is properly aligned, well managed and without


spelling mistakes.
 If session is working as expected.

 If a user is satisfied with the site after utilizing it, or if the user does not
find it difficult to utilize it.

25
CHAPTER-5

CONCLUSION AND FUTURE RECOMMENDATION

CONCLUSION

Gym management system project objective of this project was to build a program
for maintaining gym management system project details of all gymmanagement
system project members, employees and inventor. Gym management system project
systemdeveloped is able to meet all gym management system project basic
requirements. Gym management system project management of gymmanagement
system project records(both members and employees) will be also benefited by
gym management system project proposed system, as it will automate gym
management systemproject whole procedure,which will reduce gym management
system project workload. Gymmanagement systemproject security of gym
management system project system is also one of gymmanagement system project
prime concerns.

Lession Learnt/ Outcomes


After the successful completion of this project, application should be able to receive the
queries and solve them at different levels or not. If a user successfully logged in to the
application then he\she should be able to post their queries and find better assistance of
other members in the community. Also, they will be able to receive the different news
related to IT field all over the world. The application is expected to bring all the IT
personnel under a common ground.

Future Recommendation

• We can even further make it private and secured by implementing Log- in IDs
and encrypting them with passwords.

• We can give away this software for more number of people and organization to
conduct a Beta testing and based upon the results we can just make those change
and be assured of the application developed.

• We can make it more space and resource efficient so that this application
consumes lesser RAM and ROM and battery power(If available).

26
Appendix

index page:

<!DOCTYPE html>
<html lang="en">
<head>
<!-- Required meta tags -->
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-
fit=no">

<!-- Bootstrap CSS -->


<link rel="stylesheet" href="[Link]
beta/css/[Link]" integrity="sha384-
/Y6pD6FV/Vv2HJnA6t+vslU6fwYXjCFtcEpHbNJ0lyAFsXTsjBbfaDjzALeQsN6M"
crossorigin="anonymous">
</head>
<style type="text/css">
#inputbtn:hover{cursor:pointer;}
</style>
<body style="background:url('images/[Link]'); background-size: cover;">
<div class="container-fluid" style="margin-top:60px;margin-
bottom:60px;color:#34495E;">
<div class="row">
<div class="col-md-1"></div>
<div class="col-md-4">
<div class="card">
<img src="images/[Link]" class="card-img-top">
<div class="card-body">
<center>
<h5>Admin Login</h5><br>
<form class="form-group" method="POST" action="[Link]">
<div class="row">
<div class="col-md-4"><label>Username: </label></div>
<div class="col-md-8"><input type="text" name="username" class="form-
control" placeholder="enter username" required/></div><br><br>
<div class="col-md-4"><label>Password: </label></div>
<div class="col-md-8"><input type="password" class="form-control"
name="password" placeholder="enter password" required/></div><br><br><br>
</div>
<center><input type="submit" id="inputbtn" name="login_submit"
value="Login" class="btn btn-primary"></center>
</form>

</center>
</div>
</div>
</div>

27
<div class="col-md-7"></div>
</div>
</div>

<!-- Optional JavaScript -->


<!-- jQuery first, then [Link], then Bootstrap JS -->
<script src="[Link] integrity="sha384-
KJ3o2DKtIkvYIK3UENzmM7KCkRr/rE9/Qpg6aAZGJwFDMVNA/GpGFF93hXpG5Kk
N" crossorigin="anonymous"></script>
<script src="[Link]
integrity="sha384-
b/U6ypiBEHpOf/4+1nzFpr53nxSS+GLCkfwBdFNTxtclqqenISfwAzpKaMNFNmj4"
crossorigin="anonymous"></script>
<script src="[Link]
integrity="sha384-
h0AbiXch4ZDo7tp9hKZ4TsHbi047NrKGLO3SEJAg45jXxnGIfYzk4Si90RDIqNm1"
crossorigin="anonymous"></script>
</body>
</html>

28
References

 [Link]
managemnet-system-in-php/

 [Link]
system- php-source-code

 [Link]
system-project

 [Link]

29

You might also like