20bit0040 VL2022230101120 Pe003

GYM MANAGEMENT SYSTEM
A MINI PROJECT REPORT
Submitted by
ANUSHKA PATIL
20BIT0040
PREETI KUMARI
20BIT0299
in partial fulfillment for the award of the degree
of
BACHELOR OF TECHNOLOGY
in
INFORMATION TECHNOLOGY
SCHOOL OF INFORMATION TECHNOLOGY AND

ENGINEERING VIT UNIVERSITY: VELLORE 632 014
AUGUST, 2022
1
APPENDIX 2
VIT UNIVERSITY: VELLORE 632 014
BONAFIDE CERTIFICATE
Certified that this project report “GYM MANAGEMENT SYSTEM” is the

bonafide work of “ANUSHKA PATIL, PREETI KUMARI” who carried out
the project work under my supervision.
SIGNATURE
Gunasekaran G
GUIDE
Associate Professor Grade 2
SITE
X5C7+GHF, VIT University, Vellore, Tamil Nadu 632014
2
APPENDIX 3
TABLE OF CONTENTS
CHAPTER NO. TITLE PAGE NO.
ABSTRACT i
LIST OF TABLES ii
LIST OF DIAGRAMS iii
LIST OF SYMBOLS vi
1. INTRODUCTION
1.1 Motivation of your project 9
1.2 What is OOAD and UML? 10
1.3 Rational Unified Software Development Process 11
2. OBJECT ORIENTED REQUIREMENT WORKFLOW

2.1 Problem Statement 12
2.2 Flow chart for Object Oriented Requirement Workflow 12
2.3 Business Model
2.3.1 Use Case Model 13
2.3.2 Use Case Description 14
2.3.3 Initial UML diagrams 18
2.4 Initial set of requirements
3. OBJECT ORIENTED ANALYSIS WORKFLOW

3.1 Refinement of Object-Oriented Requirement Workflow 39
3
3.2 Flowchart for extracting classes 39
3.3 Functional Modelling
3.3.1 Normal Scenario 69
3.3.2 Exceptional Scenario 71
3.3.3 Extended Scenario 75
3.4 Class Modelling 78
3.5 Dynamic Modelling 79
4. OBJECT ORIENTED DESIGN WORKFLOW
4.1 Why need the Design Workflow? 90
4.2 Formats of the Attributes 91
4.3 Allocation of Operations to Classes 93
4.4 Allocation of Operations 93
4.5 CRC Cards technique 95
5. OBJECT ORIENTED IMPLEMENTATION WORKFLOW
5.1 Components Diagram 96
5.2 Deployment Diagram 96
6. CONCLUSION 97
7. REFERENCES 98
4
Abstract
This project is designed to facilitate a gymming and fitness centre to automate its operations
of keeping records and store them in the form of a large and user-friendly database further
facilitating easy access to personnel. As modernization permeates all systems, digitization
aids in their improvement in numerous specific ways. One of the technologies that aids
administration in accelerating activities and lowering complexity is the gym management
system. Digitalization and system automation would work perfectly here. Gym management
system is an online service that can be setup for your gym to help manage its branches,
trainers, payments, facilities and much more, keep track of detailed statistics, customer
management, surveys, etc. One of the primary objectives of gym management systems is to
streamline the overall member management procedure. Running a gym typically involves a
lot of administrative tasks like contracts, invoices, billing, membership cancellations, and
payments. It's designed to make running a health club simpler. You may more successfully
manage your business with the help of the programme, which compiles all data in one place,
including administrative tasks, automated billing, and online gym scheduling.
5
List of diagrams Page Number
Initial diagrams
Figure 1.1 Class diagram for online Gym Management System 18
Figure 1.2 Package diagram for online Gym Management System 19
Figure 1.3 Object diagram for online Gym Management System 19
Figure 1.4 Use case diagram for online Gym Management System 20
Figure 1.5.1 Sequence diagram for Apply for membership use case 21
Figure 1.5.2 Sequence diagram for Make payment use case 22
Figure 1.5.3 Sequence diagram for Managing equipments use case 23
Figure 1.5.4 Sequence diagram for Member’s schedule use case 24
Figure 1.5.5 Sequence diagram for Diet planner use case 24
Figure 1.6.1 Collaboration diagram for Apply for membership use case 25
Figure 1.6.2 Collaboration diagram for Make payments use case 25
Figure 1.6.3 Collaboration diagram for Managing equipments use case 26
Figure 1.6.4 Collaboration diagram for Managing schedule use case 26
Figure 1.6.4 Collaboration diagram for Diet planner use case 27
Figure 1.7.1 State chart diagram for Apply for membership use case 27
Figure 1.7.2 State chart diagram for Make payments use case 28
Figure 1.7.3 State chart diagram for Managing equipments use case 29
Figure 1.7.4 State chart diagram for Member's schedule use case 30
Figure 1.7.5 State chart diagram for Diet planner use case 31
Figure 1.8.1 Activity diagram for Apply for membership use case 32
Figure 1.8.2 Activity diagram for Make payments use case 33
Figure 1.8.3 Activity diagram for Managing equipments use case 34
6
Figure 1.8.4 Activity diagram for member's schedule use case 35
Figure 1.8.4 Activity diagram for Diet planner use case 36
Figure 1.9 Component diagram for online Gym Management System 37
Figure 1.10 Deployment diagram for online Gym Management System37
Refined diagrams
Figure 2.1 Class diagram for online Gym Management System 45
Figure 2.2 Package diagram for online Gym Management System 46
Figure 2.3 Object diagram for online Gym Management System 46
Figure 2.4 Use case diagram for online Gym Management System 47
Figure 2.5.1 Sequence diagram for Apply for membership use case 48
Figure 2.5.2 Sequence diagram for Make payments use case 49
Figure 2.5.3 Sequence diagram for Managing equipments use case 50
Figure 2.5.4 Sequence diagram for Managing member's schedule use case 51
Figure 2.5.5 Sequence diagram for Diet planner use case 51
Figure 2.5.6 Sequence diagram for Managing gym equipments use case 52
Figure 2.6.1 Collaboration diagram for Apply for membership use case 53
Figure 2.6.2 Collaboration diagram for Make payments use case 53
Figure 2.6.3 Collaboration diagram for Managing equipments use case 54
Figure 2.6.4 Collaboration diagram for Managing member's schedule use case 54
Figure 2.6.5 Collaboration diagram for Diet planner use case 55
Figure 2.6.5 Collaboration diagram for Managing gy, equipments use case 55
Figure 2.7.1 State chart diagram for Apply for membership use case 56
Figure 2.7.2 State chart diagram for Make payments use case 57
Figure 2.7.3 State chart diagram for Managing equipments use case 58
7
Figure 2.7.4 State chart diagram for Managing member's schedule use case 59
Figure 2.7.5 State chart diagram for Diet planner use case 60
Figure 2.7.5 State chart diagram for Managing gym equipments use case 61
Figure 2.8.1 Activity diagram for Apply for membership use case 62
Figure 2.8.2 Activity diagram for Make payments use case 63
Figure 2.8.3 Activity diagram for Managing equipments use case 64
Figure 2.8.4 Activity diagram for Managing member's schedule use case 65
Figure 2.8.5 Activity diagram for Diet planner use case 66
Figure 2.8.6 Activity diagram for Managing gym equipments use case 67
Figure 2.9 Component diagram for online Gym Management System 68
Figure 2.10 Deployment diagram for online Gym Management System 68
8
1. INTRODUCTION
1.1 Motivation of your project
Simplifying the entire member management process is one of the main aims of gym
management systems. Numerous administrative duties, such as contracts, invoices,
billing, membership cancellations, and payments, are frequently involved in running a
gym. It is made to make operating a health club easier. The programme gathers all
data into one location, including administrative responsibilities, automated billing,
and online gym scheduling, allowing you to manage your business more effectively.
9
1.2 What is OOAD and UML?
A method to software engineering called object-oriented analysis and design

(OOAD) models a system as a collection of interconnected objects. Each object,
which is defined by its class, state (a collection of data components), and behaviour,
represents a specific entity of interest in the system being modelled.
Applying object-modelling approaches, object-oriented analysis (OOA)
examines the functional requirements for a system. The analysis models are
developed further using object-oriented design (OOD) to create implementation
requirements.
The goal of object-oriented analysis (OOA) is to create a conceptual model of
the information that is present in the problem domain. Analysis models do not take
into account any potential implementation restrictions, including concurrency,
distribution, durability, or the design of the system. During object-oriented design,
implementation restrictions are addressed (OOD). Analysis is carried out prior to
design.
In order to account for the constraints imposed by the selected architecture and
any non-functional - technological or environmental - constraints, such as transaction
throughput, response time, run-time platform, development environment, or
programming language, object-oriented design (OOD) transforms the conceptual
model created in object-oriented analysis.
Unified Modeling Language, also known as UML, is a standardised modelling

language that consists of a collection of integrated diagrams. It was created to assist
system and software developers in defining, visualising, building, and documenting
the artefacts of software systems as well as business modelling and other
non-software systems. It is an amalgamation of best engineering approaches that
have been effective in simulating huge, complicated systems. Creating object-oriented
software and the software development process both heavily rely on it. It T primarily
employs graphical notations to convey software project design. Project teams can
communicate, explore new designs, and evaluate the software's architectural design
by using the UML.
10
1.3 Rational Unified Software Development Process (Brief
about workflows & Phase)
Inception
- Communication and plan were carried out.
- Identified actors and different use cases
- Made a use case model for all cases.
Elaboration
- Refined the use case model with respect to business and risk
- Created an executable architecture baseline.
Construction
- Project is developed and completed with all the diagrams
- Coding starts in this phase i.e source code is created.
Transition
- Final project shown.
- Beta testing is done.
- If defects found are removed from the project.
Production
- Final phase
- Project is maintained here.
11
2. OBJECT ORIENTED REQUIREMENT WORKFLOW
2.1 Problem Statement
This project is designed to facilitate a gymming and fitness centre to automate its
operations of keeping records and store them in the form of a large and user-friendly
database further facilitating easy access to personnel. As modernization permeates all
systems, digitization aids in their improvement in numerous specific ways. One of the
technologies that aids administration in accelerating activities and lowering
complexity is the gym management system.
Digitalization and system automation would work perfectly here.
Gym management system is an online service that can be setup for your gym to help
manage its branches, trainers, payments, facilities and much more, keep track of
detailed statistics, customer management, surveys, etc.
2.2 Flow chart for Object Oriented Requirement Workflow
12
2.3 Business Model
2.3.1 Use Case Model
13
2.3.2 Use Case Description (all use case Scenarios)
GLOSSARY
SNo Work Meaning
1 Equipments machines used for exercising
2 Diet plan Chart containing information about daily food

consumption
3 Schedule Exercises and diet assigned on a daily basis.
4 Trainer person assigned for assisting the members
5 Exercise Body movements
6 Treadmill Machine used for running inside the gym
7 Proteins Type of nutrient which helps in building muscles
8 premium Highest level
9 HIIT High-intensity interval training.
10 Core training Exercises to develop stabilizer muscles.
14
USE CASE DESCRIPTION
A. ADD MEMBERSHIP
Brief Description
The Add Membership use case enables Users to add membership in gym.
Step-by-step Description
1. User login the portal with username and password
2. User selects any membership package displayed on screen with all the details.
3. User enters his/her details i.e date,age,validity, eligibility.
4. Gets confirmation of selected membership package.
B. PAYMENTS
Brief Description
The payments use case enables Users to make payments for gyp facilities.
2. Various payments pending of the users will be shown on screen.
3. User selects payment mode for paying pending bills.
4. Users enter bank information in the portal.
5. Transactions are processed in banks.
15
C. MANAGE EQUIPMENT
Brief Description
The manage equipment use case enables admin to manage equipment for the gym.
1. Admin logins using username and password.
2. Admin selects equipment page.
3. Admin select operation to perform i.e either order, report defect or return.
4. Admin enters equipment id and in the database it checks if any operation is going on.
5. Confirmation from higher authority for these operations.
6. List of operations of that equipment id.
D. MANAGE MEMBERS SCHEDULE
Brief Description
The manage members schedule use case enables users to manage their workout schedule by
trainers.
1. User login using username and password.
2. Users will enter their preferences, select date and time.
3. Trainer will schedule various exercises according to their concerns.
4. In future if there are any other concerns trainer will add or remove exercises accordingly.
16
E. DIET PLANNER
Brief Description
The diet planner use case enables users to get a diet plan by trainer.
2. Users will add food allergies, daily nutrients needed.
3. Trainer will plan a diet for each day and meal.
4. Diet plan schedule will be displayed on screen.
17
2.3.3 Initial UML diagrams
Structural family
1. Class Diagram
Figure 1.1 Class diagram for online Gym Management System
18
2. Package Diagram
Figure 1.2 Package diagram for online Gym Management System
3. Object Diagram
Figure 1.3 Object diagram for online Gym Management System
19
Behavioural Family
1. Use Case Diagram
Figure 1.4 Use Case Diagram for online Gym Management System
20
2. Sequence Diagrams
Figure 1.5.1 Sequence diagram for Add membership use case
21
Figure 1.5.2 Sequence diagram for Make payments use case
22
Figure 1.5.3 Sequence diagram for Managing equipments use case
23
Figure 1.5.4 Sequence diagram for Managing member's schedule use case
Figure 1.5.4 Sequence diagram for diet planner use case
24
3. Collaboration Diagrams
Figure 1.6.1 Collaboration diagram for Apply for membership use case
Figure 1.6.2 Collaboration diagram for Make payments use case
25
Figure 1.6.3 Collaboration diagram for Managing equipments use case
Figure 1.6.4 Collaboration diagram for Managing member's schedule use case
26
Figure 1.6.5 Collaboration diagram for Diet Planner use case
4. State Chart Diagrams
Figure 1.7.1 State chart diagram for Apply for membership use case
27
Figure 1.7.2 State chart diagram for Make payments use case
28
Figure 1.7.3 State chart diagram for Managing equipments use case
29
Figure 1.7.4 State chart diagram for Managing member's schedule use case
30
Figure 1.7.5 State chart diagram for Diet Planner use case
31
4. Activity Diagram
Figure 1.8.1 Activity diagram for Apply for membership use case
32
Figure 1.8.2 Activity diagram for Make payments use case
33
Figure 1.8.3 Activity diagram for Managing equipments use case
34
Figure 1.8.4 Activity diagram for Managing member's schedule use case
35
Figure 1.8.5 Activity diagram for diet planner use case
36
Architectural Family
1. Component Diagram
Figure 1.9 Component diagram for online Gym Management System
2. Deployment Diagram
Figure 1.10 Deployment diagram for online Gym Management System
37
2.4 Initial set of requirements
Functional Requirements
1. Speed
2. Performance
3. Product quality
4. Assurance
5. Availability
Non-Functional Requirements
1. Admin users can search Branch, view description of a selected Branch, add Branch, update
Branch and delete Branch.
2. It shows the activity flow of editing, adding and updating of Gym.
3. User will be able to search and generate report of trainer, payment, facility
4. It shows full description and flow of Branch, Payment, Facility, Trainer, Gym.
38
3. OBJECT ORIENTED ANALYSIS WORKFLOW
3.1 Refinement of Object-Oriented Requirement Workflow
3.2 Flowchart for extracting classes

The technique we will use to extract conceptual classes from our use case texts is called
noun extraction. Participating classes/objects are found by examining each use case text and
extracting information from the text using the noun extraction table below.
Part of speech Model component Example
Proper noun Object Alice
Common noun Class Customer
Doing verb Association Creates, submits
Being verb Inheritance, specialization Is a kind of, is one of either
Having verb Aggregation/Attribute Has, consists of, includes
Adjective(phrase) Attribute Credit card info
39
3.3 Functional Modelling (Show all possible refined use case
model & iterations with respect to information systems)
A. ADD MEMBERSHIP
Brief Description
40
B. PAYMENTS
Brief Description
41
C. MANAGE EQUIPMENT
Brief Description
42
Brief Description
trainers.
43
E. DIET PLANNER
Brief Description
44
Structural family
1. Class Diagram
Figure 2.1 Class Diagram for online Gym Management System
45
2. Package Diagram
Figure 2.2 Package Diagram for online Gym Management System
3. Object Diagram
Figure 2.3 Object Diagram for online Gym Management System
46
Behavioural Family
1. Use Case Diagram
Figure 2.4 Use Case Diagram for online Gym Management System
47
2. Sequence Diagrams
Figure 2.5.1 Sequence diagram for Apply for membership use case
48
Figure 2.5.2 Sequence diagram for Make payments use case
49
Figure 2.5.3 Sequence diagram for Managing equipments use case
50
Figure 2.5.4 Sequence diagram for Managing member's schedule use case
Figure 2.5.5 Sequence diagram for Diet planner use case
51
Figure 2.5.6 Sequence diagram for Manage workshops use case
52
53
54
Figure 2.6.5 Collaboration diagram for Diet planner use case
Figure 2.6.6 Collaboration diagram for Manage workshops use case
55
56
57
58
59
Figure 2.7.5 State chart diagram for Diet planner use case
60
Figure 2.7.6 State chart diagram for Manage workshops use case
61
3. Activity Diagram
62
63
64
65
Figure 2.8.5 Activity diagram for Diet planner use case
66
Figure 2.8.6 Activity diagram for Manage workshops use case
67
Architectural Family
1. Component Diagram
2. Deployment Diagram
68
3.3 FUNCTIONAL MODELLING
3.3.1 Normal Scenario

A. ADD MEMBERSHIP
Brief Description
B. PAYMENTS
Brief Description
C. MANAGE EQUIPMENT
Brief Description
69
Brief Description
trainers.
E. DIET PLANNER
Brief Description
70
3.3.2 Exceptional Scenario
A. ADD MEMBERSHIP
A.a
Brief Description
4. Invalid entry leads to entry the details again
A.b
Brief Description
3. Cannot proceed further if any package is not selected.
B. PAYMENTS
B.a
Brief Description
71
5. Wrong information being processed.
B.b
Brief Description
4. No payment mode selected hence no payment being processed.
C. MANAGE EQUIPMENT
C.a
Brief Description
5. Confirmation rejected from higher authority.
72
C.b
Brief Description
5. Enters wrong equipment id, directed to equipment page.

D.a
Brief Description
trainers.
3. Trainer schedules wrong exercises.
D.b
Brief Description
trainers.
3. No preferences selected, no schedule.
73
E. DIET PLANNER
E.a
Brief Description
3. Trainer planned the same meal for every day.
E.b
Brief Description
4. Diet plan not displayed because the assigned trainer left.
74
3.3.3 Extended Scenario
A. ADD MEMBERSHIP
Brief Description
Optional
A. Invalid entry leads to entry the details again
B. Cannot proceed further if any package is not selected.
B. PAYMENTS
Brief Description
75
Optional
A. Wrong information being processed.
B. No payment mode selected hence no payment being processed.
C. MANAGE EQUIPMENT
Brief Description
Optional
A. Confirmation rejected from higher authority.
B. Enters wrong equipment id, directed to equipment page.
Brief Description
76
trainers.
Optional
A. Trainer schedules wrong exercises.
B. No preferences selected, no schedule.
E. DIET PLANNER
Brief Description
Optional
A. Trainer planned the same meal for every day.
B. Diet plan not displayed because the assigned trainer left.
77
3.4 Class Modelling (Show refined class diagram with all possible
iterations with respect to information systems)
78
3.5 Dynamic Modelling (Show refined state chart, activity,
sequence and collaboration diagrams with respect to information
systems)
79
80
Figure 2.6.5 Collaboration diagram for Diet planner use case
Figure 2.6.6 Collaboration diagram for Manage workshops use case
81
82
83
84
Figure 2.7.5 State chart diagram for Diet planner use case
Figure 2.7.6 State chart diagram for Manage workshops use case
85
3. Activity Diagram
86
87
Figure 2.8.5 Activity diagram for Diet planner use case
88
Figure 2.8.6 Activity diagram for Manage workshops use case
89
4. OBJECT ORIENTED DESIGN WORKFLOW
4.1 Why need the Design Workflow?
● Clear scheduling - Designing an effective workflow can help your team understand
what's expected of them at each stage of product development. This can help keep
your team's projects on schedule and help you reach your organisational goals.
● Increased accuracy - Clearly defined workflows can increase accuracy by providing
documented processes for each stage of the development process. Good workflow
design can also help enhance focus and communication by clearly delineating the
requirements of each task.
● Consistent transparency - An effective workflow design provides transparency
throughout the development cycle. In a quality workflow, leaders, team members and
stakeholders can identify and understand the status of a project throughout
development. This may be especially true when leveraging digital tools for creating
and communicating your workflow.
● Interdepartmental collaboration - Good workflow design can help departments work
together more successfully by improving communication. Strong workflow design
often establishes formal processes for interdepartmental collaboration, which can
enhance organisational outcomes. Workflow design might also highlight new areas
where different departments and individuals can work together.
90
4.2 Formats of the Attributes
Class Name Attributes: DataType
Role role_id: int

role_title: string
role_description: string
Permission permission_id: int

permission_role: string
permission_title: string
permission_module: string
permission_description: string
Branch branch_id: int

branch_type: string
brnach_name: string
brnach_city: string
branch_address: string
Trainer trainer_id: int

trainer_name: string
trainer_mobile: string
trainer_email: string
trainer_address: string
trainer_username: string
trainer_password: string
User user_id: int

user_role: string
name: sting
email: string
dob: string
user_address: string
91
Member member_id: int
member_name: string
member_mobile: string
member_email: string
member_address: string
member_username: string
member_password: string
Gym gym_id: int

gym_description: string
gym_type: string
gym_name: string
gym_address: string
Payment payment_id: int

payment_customer_id: int
payment_amount: int
payment_description: string
payment_data: string
92
4.3 Allocation of Operations to Classes
Basic operations include add ,edit ,delete , assign and search.
4.4 Allocation of Operations
Class Name Operations
Role addRole()
editRole()
deleteRole()
searchRole()
assignRole()
Permission addPermission()
editPermission()
deletePermission()
searchPermission()
Branch addBranch()
editBranch()
deleteBranch()
searchBranch()
Trainer addTrainer()
editTrainer()
deleteTrainer()
searchTrainer()
User addUser()
editUser()
deleteUser()
searchUser()
93
Member addMember()
editMember()
deleteMember()
searchMember()
Gym addGym()
editGym()
deleteGym()
searchGym()
Payment addPayment()
editPayment()
deletePayment()
searchPayment()
94
4.5 CRC Cards technique
Class-responsibility-collaborator cards (CRC cards) are not a part of the UML

specification, but they are a useful tool for organising classes during analysis and
design.
A CRC card is a physical card representing a single class. Each card lists the class's
name, attributes and methods (its responsibilities), and class associations
(collaborations). The collection of these CRC cards is the CRC model.
Using CRC cards is a straightforward addition to object-oriented analysis and design:
1. Identify the classes.

2. List responsibilities.
3. List collaborators.
CRC cards can be used during analysis and design while classes are being discovered
in order to keep track of them.
95
5. OBJECT ORIENTED IMPLEMENTATION WORKFLOW
5.1 Components Diagram
5.2 Deployment Diagram
96
7. CONCLUSION
This project is created to help a gym and fitness centre automate its record-keeping processes
and save them in the form of a sizable and user-friendly database, making it even easier for
staff to access. All systems are being modernised, and digitization helps to improve them in
many different ways. The gym management system is one of the technologies that helps
administration speed up operations and reduce complexity. System automation and
digitization would be ideal in this situation. An online programme called a "gym management
system" can be set up for your gym to assist in managing its branches, trainers, payments,
facilities, and much more. It can also be used to keep track of intricate statistics, manage
customers, conduct surveys, and more.
97
8. REFERENCES
[1]Boshra Naseria, Lila Rajabionb, Foroozndeh Zaravarc, Mohammad Worya Khordehbinand

and Fateme Moradi. (2019). A new model for evaluating the impact of ergonomic
architectural design of gym, social network and digital knowledge on the desire of students
for sport activities. Iran.
https://www.researchgate.net/publication/335898675_A_new_model_for_evaluating_the_im
pact_of_ergonomic_architectural_design_of_gym_social_network_and_digital_knowledge_o
n_the_desire_of_students_for_sport_activities
[2]Giornale Italiano di Medicina del Lavoro ed Ergonomia. (2019). The Digital Gym in the
neuromotor rehabilitation field. Europe. https://europepmc.org/article/med/31170342
[3]Pulagam Meena Surya Kumari, Karri Lakshmana Reddy. (2019). GYM Management
System. India. https://www.thinkindiaquarterly.org/index.php/think-india/article/view/19499
[4]Delgado, Royli Hernández. (2022). Gym-Suite An extensible platform for gyms

management. Leiria .https://iconline.ipleiria.pt/handle/10400.8/7304
[5]David Ward, Cathryn Peoples. (2019). An iOS Application With Firebase for Gym
Membership Management. IEEE.
https://ieeexplore.ieee.org/abstract/document/8707044/references#references
[6]S. Pasupathy, R. Bhavani. (2013). Measuring the Quality of Software through Analytical
Design by OOAD Metrics. India.
https://www.researchgate.net/publication/258789842_Measuring_the_Quality_of_Software_t
hrough_Analytical_Design_by_OOAD_Metrics
[7]Mr. S. Pasupathy,Dr. R. Bhavani.(2014). Analysing the efficiency of the program through

various ooad metrics. India. http://www.jatit.org/volumes/Vol61No2/14Vol61No2.pdf
98
[8]Mr. S. Pasupathy,Dr. R. Bhavani.(2015). An Efficient Methodology for Developing and
Maintaining Consistent Software Using OOAD Tools. India.
http://www.ijirset.com/upload/2015/february/51_19_An.pdf
[9]GongCheng, JunweiHan. (2016). A survey on object detection in optical remote sensing

images.IEEE
https://www.sciencedirect.com/science/article/abs/pii/S0924271616300144
[10] H. ElSawy, E. Hossain and M. Haenggi.(2013). "Stochastic Geometry for Modeling,

Analysis, and Design of Multi-Tier and Cognitive Cellular Wireless Networks: A Survey."
IEEE
https://ieeexplore.ieee.org/abstract/document/6524460
[11] Ali Bahrami, “Object Oriented Systems Development”, McGraw‐Hill, 1999
99

20bit0040 VL2022230101120 Pe003

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

20bit0040 VL2022230101120 Pe003

Uploaded by

Copyright:

Available Formats

GYM MANAGEMENT SYSTEM

A MINI PROJECT REPORT

in partial fulfillment for the award of the degree

SCHOOL OF INFORMATION TECHNOLOGY AND

VIT UNIVERSITY: VELLORE 632 014

Certified that this project report “GYM MANAGEMENT SYSTEM” is the

Associate Professor Grade 2

X5C7+GHF, VIT University, Vellore, Tamil Nadu 632014

2. OBJECT ORIENTED REQUIREMENT WORKFLOW

3. OBJECT ORIENTED ANALYSIS WORKFLOW

Figure 1.1 Class diagram for online Gym Management System 18

Figure 1.2 Package diagram for online Gym Management System 19

Figure 1.3 Object diagram for online Gym Management System 19

Figure 1.5.2 Sequence diagram for Make payment use case 22

Figure 1.5.3 Sequence diagram for Managing equipments use case 23

Figure 1.5.4 Sequence diagram for Member’s schedule use case 24

Figure 1.5.5 Sequence diagram for Diet planner use case 24

Figure 1.6.2 Collaboration diagram for Make payments use case 25

Figure 1.6.3 Collaboration diagram for Managing equipments use case 26

Figure 1.6.4 Collaboration diagram for Managing schedule use case 26

Figure 1.6.4 Collaboration diagram for Diet planner use case 27

Figure 1.8.2 Activity diagram for Make payments use case 33

Figure 1.8.3 Activity diagram for Managing equipments use case 34

Figure 1.8.4 Activity diagram for Diet planner use case 36

Figure 1.9 Component diagram for online Gym Management System 37

Figure 1.10 Deployment diagram for online Gym Management System37

Figure 2.1 Class diagram for online Gym Management System 45

Figure 2.2 Package diagram for online Gym Management System 46

Figure 2.3 Object diagram for online Gym Management System 46

Figure 2.5.2 Sequence diagram for Make payments use case 49

Figure 2.5.3 Sequence diagram for Managing equipments use case 50

Figure 2.5.5 Sequence diagram for Diet planner use case 51

Figure 2.6.2 Collaboration diagram for Make payments use case 53

Figure 2.6.3 Collaboration diagram for Managing equipments use case 54

Figure 2.6.5 Collaboration diagram for Diet planner use case 55

Figure 2.8.2 Activity diagram for Make payments use case 63

Figure 2.8.3 Activity diagram for Managing equipments use case 64

Figure 2.8.5 Activity diagram for Diet planner use case 66

Figure 2.9 Component diagram for online Gym Management System 68

Figure 2.10 Deployment diagram for online Gym Management System 68

1.1 Motivation of your project

A method to software engineering called object-oriented analysis and design

Unified Modeling Language, also known as UML, is a standardised modelling

2.1 Problem Statement

2.2 Flow chart for Object Oriented Requirement Workflow

SNo Work Meaning

1 Equipments machines used for exercising

2 Diet plan Chart containing information about daily food

3 Schedule Exercises and diet assigned on a daily basis.

4 Trainer person assigned for assisting the members

5 Exercise Body movements

6 Treadmill Machine used for running inside the gym

7 Proteins Type of nutrient which helps in building muscles

8 premium Highest level

9 HIIT High-intensity interval training.

10 Core training Exercises to develop stabilizer muscles.

D. MANAGE MEMBERS SCHEDULE

Figure 1.1 Class diagram for online Gym Management System

Figure 1.2 Package diagram for online Gym Management System

Figure 1.3 Object diagram for online Gym Management System

1. Use Case Diagram

Figure 1.5.1 Sequence diagram for Add membership use case