College in Pimpri-Chinchwad, Maharashtra

Pratibha College of Commerce and Computer Studies

--------------------------------------------------------------------------------------------------------
Computer Application Project 2021_2022
Project Guide
Prof.Snehal Varadi

Project Name –
Gym Management System

Student Name –
Mr. Yogesh Dadasaheb Vidhate
Mr. Nitin Shivaji Mate
(Class-TY.BBA.CA)
 2.Introduction

2.1Existing (manual) System

Manual operating of the current system is having certain drawbacks.
Those are:
1. Difficult for anyone to remember details of each item i.e. tool (whether
available or not) and maintaining them
2. Due to manual work generation of report are to be delayed.
3. Sometimes failing to fulfill the customer’s requirement.
4. Time consuming for owner and customer.
5. Lot of paper work.
6. It is very difficult task to make updation in store data .
 2.2 Proposed (computerized) System

Our proposed system will help a lot to reduce the drawbacks as mentioned earlier
with the existing system. It is advantageous in numerous ways. Some of its advantages
are:

1. Easy to maintain tool details.

2. Time saving for owner as well as customer.
3. Efficient traceability.
4. User Friendly.
5. Data modification can done easily.
6. Easy maintenance.
7. Data is secure.
8. Less time consuming
 3. Problem Definition

The existing system is being completely manual. Due to this many

problem arises. It is very difficult to store
and retrieve the record. A staff has to enter the record in the admission file
manually & also has to calculate the total amount of each candidate who has
to take admission.
In Gym management system many registers are maintained manually
such as customer detail, admission detail, fees detail, course detail etc.
This is hard work & lengthy procedure. If any page of the register
washed out, then entire work is to be repeated. If we want detail or any
record then we have to go through all the registers. This leads to an error in
record & also someone may change the record without any permission of
management hence proposed system is helpful to avoid these drawbacks.
REQUIRMENT ANALYSIS
1.SYSTEM ANALYSIS

•FACTFINDINGTECHNIQUES:-

To Study the system we need to collect facts i.e. gathering information about
the system. The Proper use of tools for gathering information is the key to
success analysis.
•Various fact finding techniques are:
•Observation.
•Record Review.
•Interview.
Any number of these techniques can be used to develop a system which is
accurate & comprehensive.
We used the all of the Fact Finding Techniques /Data Collection Methods .
Observation:
This technique is used to collect information, which can’t be obtained by other
fact finding techniques. This method allows analyst to gain first hand information
about how activities are carried out etc.
.
Record Review:
Record review technique is used at beginning or at the end of
system. This Kind of record review provides very valuable information
to the analyst about the system, organizations and various procedures
and rules. In our project we had seen past records of customer’s. Also
we can search their records.
Interview:

To gather the information related to real world implementation, we had

interview sessions with few of the owners of local gym service providers. These
were small businesses but still had to deal with many no. of user registrations.
Owner of one such business outlined the drawbacks of the paper based system
he was using. He told us that his job was a cumbersome one and he had to spend
a lot of time on it. As customer was increasing, tasks like searching were
becoming difficult to manage.
The other owner also faced same difficulties and how they lose customers
because of this. He also provided some suggestions on what new facilities we
can provide in searching. So these two interviews gave us a direction to proceed
with the design phase of project.
 2 System Requirement

Hardware Requirement :-

•A Computer system with INTEL 2.4 GHZ processor.

•128 MB DDR RAM.
•40 GB Hard disk.
•Mouse.
•Key board.

Software Requirement :-

•WINDOWS XP Service pack 2

•Java Development Kit 1.5 Onwards
•Microsoft Access(2007 or higher)
/ODBC driver
 E-R Diagram

1 M
Admin Ha Trainer
1 s 1
1

Trai
Goe ns
s to
M
M Customer
M

Pay
s
to

1 1
Ha Account
s
 Use Case Diagram
Start System

Request for Info

Give info about acount

courses available

Select course
&Take Admission

Pay Fee

customer admin
Give
Training

Accept
Training

Update Details
trainer

Shut Down
System
 Class Diagram
Gym System
address
name
1 1
turn On()
TurnOff() Has
updateInfo()
Has

1 1 1.*
Account Trainer
acNo Tid
branch tname
UpdateFee() payment
Visited UpdateCource()
1
1
*
Pays to Customer Train
Cid
Cname
* Caddrres
1.*
AddCust()
DeleteCust()
UpdateInfo()
Object Diagram
gym

address 1
1 name Has

Has 1

1 1.*
account trainer
acNo, tid
branch tname
payment
Visited
1 *
*
customer
Pays
Train
Cid 1
* Cname
Caddrres
1
Activity Diagram

Customer request for information

Admin give info about a available cource

Customer select cource and take addmission

No Customer
pay fee

Yes
Trainner Give training to Customer

Customer Take training from Trainner

Admin update details of customer

 Seqence Diagram
:admin
|
:customer :trainer :database
| | |
| | | |
| Request For | | |
| information | | |
| | | |
| | |
|
Give |
| | |
| information | |
|
| Select cource | | |
| | | |
| and Take | |
Give |
| Addmision | | |
| | Training | |
| | | |
| | Take | Update |
| | Training | Customer |
| || | |
|
details |
|
| |
|
| | |
|
| | |
|
| | |
| |
| | |
| |
| | |
| |

×
| |
× ×
| | |
×
|
 Collaboration Diagram

9.Shut down
1.Start System
4.Select cource and Take addmission
2.Request For info
:Admin :Customer

3.Give info
8.Update Database

5.Pay
Fee
7.Take Training
:Database
6.Give Training

:Trainer :Account
 Component Diagram

admin

gym trainer

customer
 Deployment Diagram

admin

Gym.db
 Data Dictionary
A data dictionary is a catalogue repository of the elements in
a system. These dictionary mainly talks about data and the way
they are structured to meet user requirements and organizational
needs.
1) Admin:-
FIELD NAME TYPE SIZE CONSTRAINT
Admin Text 50
Pass Text 50

2)Addcustomer Details:-
FIELD NAME TYPE SIZE CONSTRAINT

Cno Text 50 Primary Key

Cname Text 70
Cdate Text 100
Addr Text 50
Ecodate Text 50
Tel Text 50
Cage Number Long Integer
Gender Text 50
Ht Text 50
WT Text 50
Thigh Text 50
Chest Text 50
Shoulder Text 50
Course Text 50
Feepaid Text 50
Coname Text 50 Foreign Key
Cno Text 50 Foreign Key
 3) Course Details:-
FIELD NAME TYPE SIZE CONSTRAINT
Coname Text 50 Primary Key
Fees Text 50
Codur_month Text 50

4) Diet Details:-
FIELD NAME TYPE SIZE CONSTRAINT

Result Text 50 Primary Key

Diet Memo

5) Tool
Details:-

FIELD NAME TYPE SIZE CONSTRAINT

Tid Text 50 Primary Key

Tname Text 50

Tqty Text 50
6) Updatecustomer Details:-

FIELD NAME TYPE SIZE CONSTRAINT

Cno Text 50 Primary Key

Ht Text 50
Wt Text 50
Chest Text 50
Thigh Text 50
Shoulder Text 50
7) Coach Details:-

FIELD NAME TYPE SIZE CONSTRAINT

Long Integer
Cno Number Primary Key
Cname Text 50
Caddress Text 50

Birth date Date/time

Ph no Number 50
Long Integer
Salary Number
Gengder Text 50
Long Integer
Age Number
Login screen
Main menu Screen
Cust.entry Screen
Diet info. Screen
Delete cust. Screen
Cust.record Screen
Update Screen
Phy. Update Screen
Fees update Screen
Tool info Screen
Tool update Screen
Coach info. Screen
Rule’s Screen
Gym Report
Coach Report
Customer Report
Tools Report
Developers info. Screen
TESTING

System Testing:-
Testing is the process to detect the defects and minimize the risks associated with the
residual defects. The objective of testing is to uncover as many bugs as possible.
Types of Testing :

•White Box Testing.

•Black Box Testing
•White Box Testing :-

In this the structure of a program is taken into consideration. The objective of this
testing is to ensure each and every line of the code is tested. It is also called logic
driven structural testing. The tester derives test data from an examination of program
logic and structure.
 •Black Box Testing:-

In this the structure of the program is not considered. Software is

considered as a black box to which defined inputs are given. From this the
defined outputs are obtained. In this the tester only knows what the software is
supposed to do but he cannot look in the box to see how it operates.

This testing has to be done in lab (Alpha Testing) and at users site (Beta
Testing). During planning stage the time for Alpha & Beta are fixed. The black
box testing finds the errors such as interface errors, incorrect and missing
functions, initialization and termination error, performance error,
errors in structure and external database access etc. It is also called
data-driven testing. To test our project, we used both black box and white box
Techniques. All possible test cases were prepared to detect errors and correct
them. Application was tested to see if it produces expected output for a range of
inputs
 BIBLIOGRAPHY

•The Complete Reference Java-2 Seventh Edition:

-By Herbert Schildth.

•System Analysis and Introduction to Software Engineering

-By Pressman

•Online Help.
THANK YOU