A

MINI PROJECT

(Based on MCA-C102 and MCA–C201)

[MCA-S271]
ON
GYM MANAGEMENT SYSTEM
Submitted
By
Student Name
(MASTER OF COMPUTER APPLICATION)
2ND SEM
Under the Guidance of

Teacher Name
PROFESSOR Department of Computer Science

Department of Computer Science

Faculty of Technology
G.K.V, Haridwar 249404
May, 2019
 CANDIDATE’S DECLARATION

I hereby declare that the mini project work being presented

in this report entitled “GYM MANAGEMENT SYSTEM”
submitted in the department of computer science, FACULTY
OF TECHNOLOGY, Gurukula Kangri Vishwavidyalaya,
Haridwar is the authentic work carried out by me under the
guidance of Teacher Name, Professor, Department of
Computer Science, Gurukula Kangri Vishwavidyalaya,
Haridwar

Date _ _/_ _/_ _ _ _ Student Name

MCA 2nd SEM
Department of Computer Science
Gurukula Kangri Vishwavidyala
Haridwar -249404(U.K)
 CERTIFICATE

This is to certify that this report represents the original work

done by Student Name during this project submission as a
partial fulfilment of the requirement for the System Design
Project of Masters of computer Application, II Semester, of
the Gurukula Kangri Vishwavidyalaya, Haridwar (UK-249404).

Date_ _/_ _/_ _ _ _ Student Name

MCA 2nd SEM
Department of Computer Science
Gurukula Kangri Vishwavidyala
Haridwar -249404(U.K)
 ACKNOWLEDGEMENT

I would like to express my special thanks of gratitude to my

teacher Teacher Name who Gave me the golden opportunity
to do this wonderful project on the topic GYM
MANAGEMENT SYSTEM, which also helped me in doing a lot
of Research and I came to know about so many new things I
am really thankful to them.

Secondly I would also like to thank my friends who helped me

a lot in finalizing this project within the limited time frame.

DATE: _ _/_ _/_ _ _ _ Student Name

nd
MCA 2 SEM
Department of Computer Science
Gurukula Kangri Vishwavidyala
Haridwar -249404(U.K)
 Synopsis

1. TITLE OF THE PROJECT:

Gym Management System
We have done a project on Gym Management and database
management and transactions. This stores employee, member,
payroll, receipts, and products information.This system provides
data storing & report generation with graphical user interface
(GUI).
2. OBJECTIVE OF THE PROJECT:
The main objective of the project is to design and develop a user
friendly system. Easy to use and efficient computerized system.
To develop an accurate and flexible system, it will eliminate data
redundancy. Computerization can be helpful as means of saving
time & money. To provide better graphical user interface. Less
chances of information leakage. Provides security to data by
using login & password.

3. PROJECT CATEGORY:
APPLICATION PROJECT
4. LANGUAGE AND SOFTWARE TOOL USED:
Front End: JAVA, SWING, AWT
Bank End: Mysql
Operating System: Windows 10

5. STRUCTURE OF THE PROJECT:

5.1. Proposed System:-
The proposed system is highly secured, because for login the
system it requires the username and password which is different
for each department therefore providing each department a
different view of the customer information. It provides wide range
of certain criteria in each window the client is working for better
and quicker solution. It maintains report for all criteria and
transactions.Manages member information separately for all
exercise and employee information separately for considering the
requirements of gym. Stores information about regular products.
This system can run on any windows operating system.
5.2. Module Description
5.2.1 Administration Module:-
REGISTRATION

This screen contains various fields like first name, last

name, address line1, address line2, city, state, pin code, contact
number, type of customer, username, password and weight and
height etc. At first, administrator should also register his/her
details. Choices for the type of customer are admin, individual
and commercial. If any field is left empty, a pop-up will be
displayed after submission. After the successful submission of
the details, a message named “Successfully registered” will be
displayed and login screen will appear.

LOGIN

This screen contains various fields like username and

password. There are two different buttons called login and
signup. A user has to register his/her details to use this scheme.
If he/she has already registered, only he has to login using
username and password, which he/she has entered during
registration. If the user is an administrator, admin screen will be
displayed. If the user is an individual customer or Trainer, billing
screen will be displayed. This will happen because of the
following inward processes. Once the user has logged in, type of
customer will be fetched from the database by comparing the
username and password entered. Based on the type of customer
the required screen will be called.

ADMINISTRATOR
 After the administrator has logged in, admin screen will be
displayed. This screen contains various fields like user id, Fees
details and exercise image charts, month and year. Administrator
has to fill the details of the above fields. He knows only the user
id of the customer. Bill amount will be calculated depending
upon the type of customer using the units entered by
administrator. There will be different types of tariffs for different
types of customers. Administrator has to update the details every
month.

CUSTOMER FEE

The fields in the billing screen include details of the

customer, latest fee information, fee history, logout button. Every
field is displayed using panel. So, totally four panels are
employed. Details of the customer, which is in the first panel
include name, address, contact number and type of customer.
Latest fee information, which is in the second panel displays the
fee details of current month and pay button. If the user has
already paid, pay button will not be enabled. If user has not paid,
he/she can pay by clicking the pay button. Bill history which is
in the third panel includes columns such as year, month,
payment date, payment status and units consumed. Once the
user has paid the bill amount, payment date and payment status
will be updated. Logout button is placed in fourth panel. The
layout used in this billing screen is Grid layout.

6. FUTURE SCOPE OF THE PROJECT

We can provide SMS based alerts and email notifications for Fee.
The wallet can be developed to handle discounts on the points
basis. It can also be used to provide referral code concept for
referring friends. We can come with a feature that will allow the
customer to save favourite routes and provide discounts for
same. Introduce coupon management for providing coupons
which customers can use to avail discounts. Storing information
of members, employees. Check validity of information provided by
user. Storing information of members according to their id.
Generating reports for different id
7. Feasibility Study

To analyze whether the software will meet organizational

requirements Feasibility isdefined as the practical extent
to which a project can be performed successfully.
Toevaluate feasibility, a feasibility study is performed.

To determine whether the software can be implemented

using the current technology and within the specified
budget and schedule A feasibility study is a preliminary
investigation of a proposed system to decide whether the
system can run smoothly with the organization.

To determine whether the software can be integrated with

other existing software.benefits that are expected and to
decide will the organization go for it.

8. Three Types of Feasibility Study

1. Technical Feasibility

Ascertains that the techonology chosen for software

development has a large number of users so that they can
be consulted when problems arise or improvements are
required.

2. Operational Feasibility

Analyzes whether users will adapt to a new software

Determines whether the organization is satisfied by the
alternative solution proposed by the software development
team.

3. Economical Feasibility

Cost of hardware, software, development team, and

training. Feasible only if tangible and intangible benefits
 outweight the cost. The cost for proposed online shopping
system is outweighting the cost and efforts involved.

9. Requirement Specification
User Requirements
There should be software which allocates
rooms automatically and maintains records of
customers.
System Requirements
There should be a database backup of the
hotel management system. There should be a Java
supported framework for the system. Operating
system should be WindowsXP or a higher version of
windows.
User Interface
The User interface required to be developed
for the system should be user friendly and
attractive.
There are two sets of java APIs for graphics programming:
AWT (Abstract Windowing Toolkit) and Swing.
□ AWT API was introduced in JDK 1.0. Most of the
AWT components have become obsolete and
should be replaced by newer Swing components.
□ Swing API, a much more comprehensive set of
graphics libraries that enhances the AWT, was
introduced as part of Java Foundation Classes
(JFC) after the release of JDK 1.1. JFC consists of
Swing, Java2D, Accessibility, Internationalization,
and Pluggable Look-and-Feel Support APIs. JFC
was an add-on to JDK 1.1 but has been integrated
into core Java since JDK 1.2.
For the development of this project both hardware and
software were required. The hard required is any
machine compatible for running the softwares and
resources required.
10. Database Tables
1. desc loginpage;
+----------+-------------+-------+-----+-----------+---------+
| Field | Type | Null | Key | Default | Extra |
+----------+-------------+------+-----+---------+-------+
| username | varchar(50) | YES | | NULL | |
| password | varchar(50) | YES | | NULL | |
+----------+-------------+------+-----+---------+-------+

2. desc add_customer;
+---------------+--------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+---------------+--------------+------+-----+---------+-------+
| recipt_no | int | YES | | NULL | |
| name | varchar(50) | YES | | NULL | |
| fname | varchar(50) | YES | | NULL | |
| email | varchar(100) | YES | | NULL | |
| address | varchar(100) | YES | | NULL | |
| contactNo | varchar(10) | YES | | NULL | |
| payments_plan | varchar(50) | YES | | NULL | |
| gender | varchar(10) | YES | | NULL | |
| height | float | YES | | NULL | |
| weight | float | YES | | NULL | |
| remarks | varchar(100) | YES | | NULL | |
| trainer_name | varchar(50) | YES | | NULL | |
| catogery | varchar(50) | YES | | NULL | |
+---------------+--------------+------+-----+---------+-------+
 3. desc add_trainer;

+---------------+--------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+---------------+--------------+------+-----+---------+-------+
| tid | int | YES | | NULL | |
| name | varchar(50) | YES | | NULL | |
| fname | varchar(50) | YES | | NULL | |
| email | varchar(100) | YES | | NULL | |
| address | varchar(100) | YES | | NULL | |
| contactno | varchar(10) | YES | | NULL | |
| emerggincyno | varchar(10) | YES | | NULL | |
| catogery | varchar(50) | YES | | NULL | |
| min_aggrement | varchar(20) | YES | | NULL | |
| gender | varchar(10) | YES | | NULL | |
| height | float | YES | | NULL | |
| weight | float | YES | | NULL | |
| remarks | varchar(100) | YES | | NULL | |
+---------------+--------------+------+-----+---------+-------+
4. desc customer_attendunce;

+------------+-------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+------------+-------------+------+-----+---------+-------+
| recepit_no | int | YES | | NULL | |
| time | varchar(50) | YES | | NULL | |
| attendunce | varchar(50) | YES | | NULL | |
| data | varchar(50) | YES | | NULL | |
+------------+-------------+------+-----+---------+-------+
 5. desc pay_customer;

+-----------+-------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-----------+-------------+------+-----+---------+-------+
| recipt_no | int | YES | | NULL | |
| name | varchar(50) | YES | | NULL | |
| catogery | varchar(50) | YES | | NULL | |
| fees | float | YES | | NULL | |
| month | varchar(20) | YES | | NULL | |
| tname | varchar(50) | YES | | NULL | |
+-----------+-------------+------+-----+---------+-------+

6. desc trainer_attendunce;

+--------------------+-------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+--------------------+-------------+------+-----+---------+-------+
| tid | int | YES | | NULL | |
| morning_attendunce | varchar(50) | YES | | NULL |
|
| evening_attendunce | varchar(50) | YES | | NULL | |
| data | varchar(50) | YES | | NULL | |
+--------------------+-------------+------+-----+---------+-------+

CONCLUSION

Gym Management System using Java Swing and MySQL

has been developed with the help of NetBeans IDE effectively. It is
simple and user friendly. Since this system is implemented in
Java, it is platform independent. It has wide scope for future
expansion. All the manual as well as paper works can be fully
eliminated in the gym branch. The accuracy and reliability are
surely increased. It makes sure that unauthorized personal
cannot execute this program. This system provides secured
processing without any threats.

HARDWARE REQUIREMENT
OS-Windows
Hard Disk-80 GB
RAM-1 GB

SOFTWARE REQUIREMENT
● Front End Java, NetBeans
● Back End MySQL

Yha par code likhana hai