Project Report

THE SUPERIOR COLLEGE LAHORE
Faculty of Computer Science & IT

Department of Software Engineering
Final Year Project

PROJECT REPORT (Part-1)
[GYM MANEGEMENT SYSTEM]
Project Team
Student Name Student ID Program Contact Number Email
Maham Allauddin Bcsm-f19-413 BSCS 03314562934 Bcsm_f19-424@sup.edu.pk
Sohaib Ilyas Bcsm-f19-424 BSCS 03034804503 Bcsm_f19-424@sup.edu.pk
Muneeb Butt Bcsm-f19-460 BSCS 03055552505 Bcsm_f19-460@sup.edu.pk
([Designation])
Project Report: < write Project title here>
Project Report
[GYM MANEGEMENT SYSTEM]
Change Record
Author(s) Version Date Notes Supervisor’s Signature
1.0 <Original Draft>
<Changes Based on
Feedback from
Supervisor>
<Changes Based on
Feedback From Faculty>
<Added Project Plan>
<Changes Based on
Feedback from
Supervisor>
Faculty of CS&IT, The Superior College Lahore, Pakistan 2

APPROVAL
PROJECT SUPERVISOR
Comments: ___________________________________________________________________
_____________________________________________________________________________
Name:______________________________
Date:_______________________________ Signature:__________________________
PROJECT MANAGER
Comments: ___________________________________________________________________
_____________________________________________________________________________
Date:_______________________________ Signature:__________________________
HEAD OF THE DEPARTMENT

Comments: ___________________________________________________________________
_____________________________________________________________________________
Date:_______________________________ Signature:__________________________

Dedication
This work is dedicated to my . . . . . .

Acknowledgements
I am really thankful to my supervisor who has . . . . . . . . . .
Executive Summary
This Gym Management System shall enable the user to add

members to a gym and manage the fee payment of the gym user.

It is a very simple interface developed. The user of the system

shall be able to add a new gym member. This shall add all the
necessary details like personal information, into the system. The
Gym Management System shall also monitor the exercises of
every member. It shall give the proper workout plan of the
member according to his/her body. This software shall hold all
the details of gym members. It shall enable the user to choose
the packages according to fee. It shall display the member
workout detail and make changes on the existing data.
.

Table of Contents
Dedication.......................................................................................................................................iv
Acknowledgements..........................................................................................................................v
Executive Summary.........................................................................................................................vi
Table of Contents...........................................................................................................................vii
List of Figures..................................................................................................................................ix
List of Tables.....................................................................................................................................x
Chapter 1.........................................................................................................................................1
Introduction.....................................................................................................................................1
1.1. Background.......................................................................................................................2
1.2. Motivations and Challenges..............................................................................................2
1.3. Goals and Objectives.........................................................................................................2
1.4. Literature Review/Existing Solutions................................................................................2
1.5. Gap Analysis......................................................................................................................2
1.6. Proposed Solution.............................................................................................................2
1.7. Project Plan.......................................................................................................................3
1.7.1. Work Breakdown Structure...........................................................................................3
1.7.2. Roles & Responsibility Matrix........................................................................................3
1.7.3. Gantt Chart....................................................................................................................3
1.8. Report Outline...................................................................................................................3
Chapter 2.........................................................................................................................................4
Software Requirement Specifications.............................................................................................4
2.1. Introduction......................................................................................................................5
2.1.1. Purpose..........................................................................................................................5
2.1.2. Document Conventions.................................................................................................5
2.1.3. Intended Audience and Reading Suggestions...............................................................5
2.1.4. Product Scope................................................................................................................5
2.1.5. References.....................................................................................................................6
2.2. Overall Description............................................................................................................6
2.2.1. Product Perspective......................................................................................................6
2.2.2. Product Functions..........................................................................................................6
2.2.3. User Classes and Characteristics...................................................................................6
2.2.4. Operating Environment.................................................................................................7
2.2.5. Design and Implementation Constraints.......................................................................7
2.2.6. User Documentation.....................................................................................................7
2.2.7. Assumptions and Dependencies...................................................................................7
2.3. External Interface Requirements......................................................................................8
2.3.1. User Interfaces..............................................................................................................8
2.3.2. Hardware Interfaces......................................................................................................8
2.3.3. Software Interfaces.......................................................................................................8
2.3.4. Communications Interfaces..........................................................................................9

2.4. System Features................................................................................................................9

2.4.1. System Feature 1...........................................................................................................9
2.4.1.1. Description and Priority.............................................................................................9
2.4.1.2. Stimulus/Response Sequences..................................................................................9
2.4.1.3. Functional Requirements...........................................................................................9
2.4.2. System Feature 2.........................................................................................................10
2.4.2.1. Description and Priority...........................................................................................10
2.4.2.2. Stimulus/Response Sequences................................................................................10
2.4.2.3. Functional Requirements.........................................................................................10
2.4.3. System Feature 3 (and so on)......................................................................................11
2.5. Other Nonfunctional Requirements...............................................................................11
2.5.1. Performance Requirements........................................................................................11
2.5.2. Safety Requirements...................................................................................................11
2.5.3. Security Requirements................................................................................................12
2.5.4. Software Quality Attributes.........................................................................................12
2.5.5. Business Rules.............................................................................................................12
2.6. Other Requirements.......................................................................................................12
Chapter 3.......................................................................................................................................13
Use Case Analysis...........................................................................................................................13
3.1. Use Case Model...............................................................................................................14
3.2. Fully Dressed Use Cases..................................................................................................14
Chapter 4.......................................................................................................................................15
System Design................................................................................................................................15
4.1. Architecture Diagram......................................................................................................16
4.2. Domain Model................................................................................................................16
4.3. Entity Relationship Diagram with data dictionary..........................................................16
4.4. Class Diagram..................................................................................................................17
4.5. Sequence / Collaboration Diagram.................................................................................17
4.6. Operation contracts........................................................................................................17
4.7. Activity Diagram..............................................................................................................18
4.8. State Transition Diagram................................................................................................18
4.9. Component Diagram.......................................................................................................18
4.10. Deployment Diagram..................................................................................................19
4.11. Data Flow diagram [only if structured approach is used - Level 0 and 1]...................19
Chapter 5.......................................................................................................................................20
Implementation.............................................................................................................................20
5.1. Important Flow Control/Pseudo codes...........................................................................21
5.2. Components, Libraries, Web Services and stubs............................................................21
5.3. Deployment Environment...............................................................................................21
5.4. Tools and Techniques......................................................................................................22
5.5. Best Practices / Coding Standards..................................................................................22
5.6. Version Control...............................................................................................................22
Appendices....................................................................................................................................23
Appendix A: Information / Promotional Material.........................................................................24

Reference and Bibliography..........................................................................................................27

Index..............................................................................................................................................29
List of Figures
1.1 Caption of first figure of first chapter 6

1.2 Caption of second figure of first chapter 7
2.1 Caption of first figure of second chapter 14
2.2 Caption of second figure of second chapter 22
2.3 Caption of third figure of second chapter 26
5.1 Caption of first figure of fifth chapter 49
5.2 Caption of second figure of fifth chapter 49

List of Tables
1.1 label of first table of first chapter 6

1.2 label of second table of first chapter 7
2.1 label of first table of second chapter 14
2.2 label of second table of second chapter 22
2.3 label of third table of second chapter 26
5.1 label of first table of fifth chapter 49
5.2 label of second table of fifth chapter 49


Chapter 1
Introduction

Chapter 1: Introduction
A Gym management project contains two logins one is for admin, who can edit, delete or
update the data and the other one is for members. The member can check the detail of result,
exercise and fee. Members can login using provided user id password and check their profile
details. The admin can register a new member and instructor too. Only the admin can insert,
update and delete the records.
1.1. Background
Gym management systems provide many benefits to fitness institutions, mostly stemming from
centralized data management and accessibility. Admins can more easily input, manage, and
access member data. Trainers get better visibility into how their member is performing in gym.
Admin and as earlier the details of the members were saved on paper and it was difficult to
manage the heaps of files.
1.2. Motivations and Challenges

When I was exercise in gym, I have seen there that there was no proper application for
managing records of their trainers and members. My fellows have observed the same thing in
those centers. The admin has to save the member information in different files and have to
work manually. Portals need to be designed to connect members, admin, and trainers
regardless of location or device. They need to be considered as an extension of the fitness
center. Well-designed application should provide timely and accurate information in a simple
format.
1.3. Goals and Objectives

Our major goal is to provide a application to the admin and as well as to the members where a
user save and check the updated information easily. Main objective of our project is to
Update the data of members in the records for the admin too so they can have check on their
members.
1.4. Literature Review/Existing Solutions

This project has come up with much functionality for fitness institutions to track the members
fee and managing attendance. It helps admin to keep track of member progress without visiting
to the gym. It also notifies member about the fee of the student. The member information has
the particulars (like register number, date-of-birth, parent phone number, address etc.) saved
in the project by the admin. All these particulars is stored in the database. Attendance is part of
any system to keep track of the particular person. In fitness institutes attendance management
is normally a manual process. This project can be use in other fitness institutions. It can be
customized as per the need. As member added to the fitness system it is difficult to manage

and track member details. To overcome difficulties we come up with this new approach
member portal management system with additional features. This new approach will provide
fast processing, efficient student tracking, and produces desired result.
1.5. Gap Analysis

The user must have a username and password for logging into the system. If there will be a
conflict in that then they cannot enter into the system and cannot check or update their details.
For logging in, you must have registered yourself from the admin in the system. The data will be
saved in database.
1.6. Proposed Solution

The gym management system aims to automate the manual working in fitness center by using
this system. The admin can easily save the details of members and instructors. The accessibility
and manageability will become easy for the users. So that their data can be saved for long
period of time and managed. The modules of the systems we provide are as:
• Members
• Admin
• Instructors
• Registration
• Exercise
• Attendance
• Fee
• Equipment
1.7. Project Plan

We are making a full-fledge project to be implemented in the fitness center. We will add the
additional features according to the requirement of the center.
1.8. Report Outline

Admins can more easily input, manage, and access member data. Members get better visibility
into how their exercise is performing in gyms. Exercise requirements are also much easier to
fulfill. It will become easy for members and admin, as earlier the details of the members were

saved on paper and it was difficult to manage the heaps of files. The users will access the
system through their logins.

Chapter 2
Software Requirement
Specifications

Chapter 2: Software Requirement Specifications

2.
2.1. Introduction
2.1.1. Purpose
The purpose of this software requirement specification document is to provide a detailed
description of the functional and working of the system. This document will cover each and
every feature of the application including data insertion, updating, deletion and all the
interfaces. This document will cover all intended feature and technical dependencies.
2.1.2. Document Conventions
Standard rules of documentation have been followed in order to standardize the work.
This software requirement document uses the following conventions.
Description Appearance
Website Armour fitness
Desktop Application JAVA
Database Microsoft SQL Server
SRS Software Requirements Specification
2.1.3. Intended Audience and Reading Suggestions

The intended audience for this gym Management System document is the internal guides of the
organization where the team has developed the project. Further modifications and reviewing
will be done by the team and deliver a final version. The final version of this document is
reviewed by the team and Head of the institution.
For that,
• For developers there is a need to start from introduction and understand workflow
diagrams.
• The project manager sequence of reading is from introduction to class diagram and use
cases.

• For users of a website there is a need to read from introduction and read all descriptions
including scope and functionalities.
2.1.4. Product Scope
Gym Management System is capable of managing each and every data regarding member,
payments etc. Gym Management System helps us in managing in an extremely efficient way.
We have two modules in this project. One is admin and other member.
• Admin can maintain the fee details of members
• User module can edit their personal details
• Can view fee details
• Can view attendance of the members
• Members can check the exercise.
• This project can be used in Gym.
2.1.5. References
No reference
2.2. Overall Description

2.2.1. Product Perspective
Gym Management System is capable of managing each and every data regarding member, fee,
attendance etc. Gym Management System helps us in managing in an extremely efficient way.
This gym Management System works in an efficient manner. We have two logins in this project.
One is admin and other is member. Admin can maintain the fee details of member and can
generate the remaining fee. User module can view their exercise details and can view the fee
details.
2.2.2. User Classes and Characteristics
In our project, we are going to keep the information regarding our product which can be
understandable by a new person who is going to use it. If a new member is using it in gym
help will be provided in that we are going to explain each and every step clearly by our
product can be useful for any user.

Classes Characteristics
Admin Admin can register a new member, instructor and equipment.

He can update , insert and delete the record according to the
given situation.
Member Users will go through a certain course for registration or
downloading the fee receipt. He/she can view exercise, fee and
their attendance.
Developer Responsible for optimization, SEO, Inbound & outbound linking,
navigation setup and ad-placement.
2.2.3. Operating Environment

The operating environment of our project is as follows:
 Database
 Desktop application
 Client/server system
 Operating system: Windows.
 database: sql+ database
 platform: vb.net/Java/PHP
2.2.4. Design and Implementation Constraints

• The global schema, fragmentation schema, and allocation schema.
• SQL commands for above queries/applications
• Implement the database at least using a centralized database management system.
• The data should be updated all the time so that it does not contain any issue for low
availability.

2.2.5. Assumptions and Dependencies

We made no assumptions
2.3. External Interface Requirements
2.3.1. User Interfaces

3. Front-end software: Vb.net version
4. Back-end software: SQL+
The website is developed for making the user navigation through panels and view as simple as
possible. The font family which we used in our website is Times New Romans.
The admin will have an add, delete and update button of trainer member fee and equipment.
Whereas, members have the view button on the system. Through which they can interact with
the project.
Responsiveness: The website is responsive across all the devices and desktop that are
manufactured across the world.
4.1.1. Hardware Interfaces

A user can access this website by using the following devices.
● Computer
● Laptop
As it’s a desktop application. It is not mandatory to connected the internet for using the real
time enrollment and updating.
4.1.2. Software Interfaces
Website is an easy to use platform designed and developed for native usage. Website’s running
scripts are coded with Java and design is managed by CSS and bootstrap. The Application
version of our project is made with Java. The backend of the website is done in Php version 7.2
hosted on a Linux server. The components we are using in firebase are:
1. Net beans
2. SQL
3. XAMP

4.1.3. Communications Interfaces

The communications functions required by this product are LAN connection within the whole
company so that the Admin, member can interact with each other. We use TCP/IP protocol.
4.2. System Features

This Student Management System project is divided into 2 logins.
1. Admin
2. Student
Admin:
 Admin is a person whose responsibility is to maintain the database that contains each and
every data regarding the all the student. Admin can add student details into the database can
be able to delete student details and can update the student fee details.
Admin has some other responsibilities they are
 Maintain the fee and Register, delete the student
 Generate the results of the students
 Attendance updating
User: Here the user means the member. The responsibility of the member is to login into the site
and can view his/her fee details and can able update his/her personal details if there is any wrong
details are present. Whenever the member will register his/her name then the member will be
given by one individual username and password. When the member will type the correct
username and password then the will enter into another page. In that page, the member can select
two options that are exercise details. A student can able to view the fee details, attendance
update.
4.2.1. System Feature 1

The system feature 1 is named as login of admin.

4.2.1.1. Description and Priority

The log in of admin is top most priority of our project as many of the important work
are done by the admin like insertion, deletion, updation and viewing. We have to
make this feature of log in validate so that the admin’s log in will be secured
Stimulus/Response Sequences
 At first, when the admin logs in to the system, the message of “login successfully” should
be popped up. Then the next page of dashboard will be opened which contains modules
like registration, instructor, member, fee, attendance and result.
 Then the admin can select the module according to it’s need that which of the module
should be used. For example, if he wants to edit the attendance of any member so he will
click the attendance module. He will search the reg no. of the member in the search bar
and can change the fee. Click on the update button and the data will be updated.
4.2.1.2. Functional Requirements

 Registration
 fee management
 Attendance
 member management
 Instructor management
 exercise
4.2.2. System Feature 2

The system feature 1 is named as login of user (student and parents).

4.2.2.1. Description and Priority

The priority of this module is also high as the member have their own log in. After
registration a username and a password will be assigned to them by which they can
easily access the system and can view their details.
4.2.2.2. Stimulus/Response Sequences
At first, when the user logs in to the system, the message of “login successfully” should be
popped up. Then the next page of dashboard will be opened which contains modules like fee,
exercise.
 Then the user can select the module according to it’s need that which of the module
should be used. The members can only view the details like view exercise, view
attendance and view fee.
4.2.2.3. Functional Requirements
The functional requirement for this feature are as follows:
• fee management
• Exercise management
• Attendance
4.2.3. System Feature 3 (and so on)

All the system features are discussed at System feature 1 and 2.
4.3. Nonfunctional Requirements

4.3.1. Performance Requirements
A) E-R DIAGRAM
The E-R Diagram constitutes a technique for representing the logical structure of a database in
a pictorial manner. This analysis is then used to organize data as a relation, normalizing relation
and finally obtaining a relation database.
 ENTITIES: Which specify distinct real-world items in an application.

 PROPERTIES/ATTRIBUTES: Which specify properties of an entity and relationships.

 RELATIONSHIPS: Which connect entities and represent meaningful dependencies between
them.
 B) NORMALIZATION:
 The basic objective of normalization is to reduce redundancy which means that information
is to be stored only once. Storing information several times leads to wastage of storage
space and increase in the total size of the data stored
4.3.2. Safety Requirements

4.3.3. Security Requirements
Security systems need database storage just like many other applications. However, the
special requirements of the security market mean that vendors must choose their
database partner carefully. There should be a backup of the queries and the data so that if
the data is crashed due to some reason so it can be managed again.
4.3.4. Usability Requirements

There can be large numbers of users for using the system and the system should satisfy
the needs of the customers.
4.3.5. Reliability Requirements

The system should be reliable and easy to use for a long time.
4.3.6. Maintainability/Supportability Requirements

The system should maintain the saved records into the system.
4.3.7. Portability Requirements

The system should be portable to use.
4.3.8. Efficiency Requirements
The project should be efficient and easy to manage.

4.4. Domain Requirements

<Define any other requirements not covered elsewhere in the SRS. This might include database
requirements, internationalization requirements, legal requirements, reuse objectives for the
project, and so on. Add any new sections that are pertinent to the project.>
Chapter 3
Use Case Analysis

Chapter 3: Use Case Analysis

This chapter is all about the roles and functionalities of the system and its actors in the use case
form. All the primary and secondary actors with respect to their responsibilities. We have made a
use case diagram in which we’ve properly defined each and every functional and nonfunctional
requirement according to the respected id or levels. In the use case given below explains the relation
between actors and their functionalities.
3.1. Use Case Model

. A use-case model is a model of how different types of users interact with the system
to solve a problem. As such, it describes the goals of the users, the interactions
between the users and the system, and the required behavior of the system in satisfying
these goals.

3.2. Use Cases Description
.Use Case Name:

Login
Use Case Description:

A user (Admin, Member) login to the system and use the

functionality of the system.
3. Actors:
Admin, Member
4. Pre-Condition:
a. User should be registered.
b. System should be connected with internet.
5. Post-Condition:
After successful login you can access the
homepage.
6. Main Scenario:
a. Enter valid Username.
b. Enter valid Password.
c. Enter submit button.
d. Validate username and password.
e. System will give access to homepage.
7. Alternatives:
User may enter invalid Username.
User may enter invalid Password.
System will show an error message.
Invalid password for four times Application closed.
1. Use Case Name:

Member Details
2. Use Case Description:
Admin will click on the member detail button to perform

functions on member i.e Add Member, Update/delete
Member, view Members.
3. Actors:
Admin
4. Pre-Condition:
a. Admin must login successfully.
b. Admin must have an account.
c. System should be connected with internet.
5. Post-Condition:
After successful login and click on Member Details
button Admin can access the Page where you can add,
update/delete and view members.
6. Main Scenario:
c. Validate username and password.
d. System will give access to member details Page.

e. Admin will press the member details button to add,

update/delete and view button.
f. Fill all the required fields.
g. Press add button, update/delete and view button.
7. Alternatives:

Leave field empty system will show a message to fill

all the fields.
Admin will press the wrong button.
1. Use Case Name:

Equipment Details
2.Use Case Description:

Admin will click on the Equipment button to perform

functions on Equipment i.e Add Equipment, View
Equipment.
3. Actors:
Admin
4. Pre-Condition:
5. Post-Condition:
After successful login and click on Equipment button you
can access the Page where you can add, and view
Equipment.
6. Main Scenario:
d. System will give access to Equipment Page.
e. Admin will press the equipment details button to add
and view button.
g. Press add equipment button and view equipment
button.

7. Alternatives:

Leave field empty system will show a message to fill
all the fields.
1. Use Case Name:

Trainer Details
Admin click the trainer detail button to perform functions
on trainer e.g. Add trainer, Update/delete trainer, View
trainer.
3. Actors:
Admin
4.Pre-Condition:

5. Post-Condition:
After successful login and click on trainer Details button
Admin can access the Page where you can add,
update/delete and view trainer.
6. Main Scenario:
d. System will give access to trainer details Page.
e. Admin will press the trainer details button to add,
update/delete and view button.
g. Press add button, update/delete and view button.
7. Alternatives:


Leave field empty system will show message to fill all
the fields.
Admin will press the wrong function button.
1. Use Case Name:

Fee Details
2.Use Case Description:
Admin click the Fee detail button to see
that which members pay fee or not.
3. Actors:
Admin
4.Pre-Condition:
5. Post-Condition:
After successful login and click on fee Details button you

can access the Page where you can view the paid
members or not paid.
6. Main Scenario:
d. System will give access to fee details Page.
e. Admin will press the fee details button
f. Press balance button the paid member’s details will
show and if he press fee button it will show the unpaid
member’s details.
7. Alternatives:

Admin will press the wrong function button.
1. Use Case Name:

Attendance
Member click the Attendance button to mark his
attendance.
3. Actors:
Member
4.Pre-Condition:
a. Member must login successfully.
b. Member must have an account.
5. Post-Condition:
After successful login and click on Attendance button you
can access the Page where member can mark his
attendance.
6. Main Scenario:
d. System will give access to Attendance Page.
e. Member will press the Attendance button to Mark
attendance.
g. Press save button to save attendance.
7. Alternatives:
Member may enter invalid Username.
Member may enter invalid Password.

Leave field empty system will show a message to fill all
the fields.
1 .Use Case Name:

Workout
Member will click the workout button to view work out
details.
3. Actors:
Member
4.Pre-Condition:
a. Member must login successfully.
b. Member must have an account.

5. Post-Condition:
After successful login, Member will press the workout
button and the details of workout will show.
6. Main Scenario:
d. System will give access to Attendance Page.
e. Member will press the workout button to view the
workouts.
7. Alternatives:
Member may enter invalid Username.
Member may enter invalid Password.

Chapter 4
System Design

Chapter 4: System Design

[System design is the process of defining the components, modules, interfaces, and
data for a system to satisfy specified requirements. System development is the
process of creating or altering systems, along with the processes, practices, models,
and methodologies used to develop them.]
4.1. Domain Model

Domain modeling is a technique used to understand the project problem description
and to translate the requirements of that project into software components of a solution.


4.2. Entity Relationship Diagram with data dictionary

4.

4.1. Class Diagram

4.2. Sequence / Collaboration Diagram











4.3. Activity Diagram

5.


4.1. DFD Diagram

6.

7.



4.1. Deployment Diagram

Chapter 5
Implementation

Chapter 5: Implementation
This document describes the project implementation for developing our project
Resources Point’s website and application. The project implements SQLServer, JAVA
for desktop application PHP, HTML, CSS, JavaScript for web application and other
analytical technologies. The project will be capable of running on phones, laptops and
devices. The interface for the project will provide a single platform where you can get
learning resources.
5.1. Important Flow Control/Pseudo codes

A Control flow is the graphical representation of control flow or computation
during the execution of programs or applications. Control flow graphs are
mostly used in static analysis as well as compiler applications, as they can
accurately represent the flow inside of a program unit.
User
Home Page Post Grid / Menu Updates
User visits
User surf around the post grid or meu for choosing a fee attendance home page
or exercise
User visits any course or source code for downloading or reading its description
Main Page Publish Your attendance Share or feedback Download fee receipt
User visits and perform edit delete enter new details on different modu
User downloads the receipt
User fills up the information and submit a request for publishing his attendance
User shares the course or any learning resource at any social media platform

5.2. Deployment Environment

We deployed this project in Windows 10 and We’ve connected NetBeans setting up our
Application theme and we’ve provided a solution that is both web and Desktop Application
based.
5.3. Tools and Techniques

The tools that are required are Listed below
Development Tools
1. NetBeans
2. Visual Studio
3. Microsoft SQLServer
4. Xampp (Database Testing)
Auditing and Analytics Tools
5. Oracle Database
6. Exchange
7. Window Server
8. VMware
9. Google Analytics
10. Search Console
Front End:
For our Application we’ve used comprehensive languages like JAVA and SQL queries for Little
alteration in third party plugins. Desktop Application is based in Java & XML. Both of them are
responsive for every browser, device and operating system. With increasing end user
expectations in relation to the quality, expressiveness and performance of web-based
applications, we have given more attention to satisfy the customer.
Back End:

For our website We’ve used database with PHP that is secured with Let’s Encrypt X3.
The CDN serves the purpose of loading media files from the closest data network.
For Desktop Application we are using NetBeans and Microsoft SQLServer
5.4. Best Practices / Coding Standards

 Defined Life Cycle and Milestones
 Stable Requirements and Scope
 Defined Organization, Systems, and Roles
 Quality Assurance
 Planned Commitments
 Scope and mission
 Search Engine Optimization – On-Page
 Search Engine Optimization- Off-Page
 Ad-Placement
 Structure Data Setup
5.1. Version Control

We have this complete documentation that completely represents all the factors that are
related to our project. In addition, we’ve used technical frames in our application and the
application we’ve developed consists of web links to them too. And website will consist of all
the privacy policies, sitemap and about us pages. The name of our document that we are
currently writing is Project Report Documentation.

Appendices

Appendix A: Information / Promotional Material

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
[Between 4 to 8 lines describe what is this appendix all about ]
A.1. Broacher
A.2. Flyer
A.3. Standee
A.4. Banner

A.5. First Level heading [16 pt, Calibri, Bold, Left aligned]
A.5.1. Second level heading [14 pt, Calibri, Bold, Left aligned]
A.1.1.1. Third level heading [12 pt, Calibri, Bold, Left aligned]

Appendix [no.]: Appendix Title

[Between 4 to 8 lines describe what is this chapter all about ]
A.1. First Level heading [16 pt, Calibri, Bold, Left aligned]
A.1.1. Second level heading [14 pt, Calibri, Bold, Left aligned]
A.1.1.2. Third level heading [12 pt, Calibri, Bold, Left aligned]

Reference and
Bibliography

Reference and Bibliography
[1] M. Sher, M. Rehman, “Title of the Paper” Conference name/Journal Name, Edition,
Volume, Issue, ISBN/ISSN, PP, Publisher/City-Country, Year.
[2] ……

Index

Index
[A]
[B]
[C]



Project Report

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

Project Report

Uploaded by

Copyright:

Available Formats

THE SUPERIOR COLLEGE LAHORE

Faculty of Computer Science & IT

Final Year Project

[GYM MANEGEMENT SYSTEM]

Maham Allauddin Bcsm-f19-413 BSCS 03314562934 Bcsm_f19-424@sup.edu.pk

Sohaib Ilyas Bcsm-f19-424 BSCS 03034804503 Bcsm_f19-424@sup.edu.pk

Muneeb Butt Bcsm-f19-460 BSCS 03055552505 Bcsm_f19-460@sup.edu.pk

Faculty of CS&IT, The Superior College Lahore, Pakistan 2

HEAD OF THE DEPARTMENT

Faculty of CS&IT, The Superior College Lahore, Pakistan 3

This work is dedicated to my . . . . . .

Faculty of CS&IT, The Superior College Lahore, Pakistan 4

I am really thankful to my supervisor who has . . . . . . . . . .

This Gym Management System shall enable the user to add

Faculty of CS&IT, The Superior College Lahore, Pakistan 5

It is a very simple interface developed. The user of the system

Faculty of CS&IT, The Superior College Lahore, Pakistan 6

Faculty of CS&IT, The Superior College Lahore, Pakistan 7

2.4. System Features................................................................................................................9

Faculty of CS&IT, The Superior College Lahore, Pakistan 8

Reference and Bibliography..........................................................................................................27

1.1 Caption of first figure of first chapter 6

Faculty of CS&IT, The Superior College Lahore, Pakistan 9

1.1 label of first table of first chapter 6

Faculty of CS&IT, The Superior College Lahore, Pakistan 10

Faculty of CS&IT, The Superior College Lahore, Pakistan 11

Faculty of CS&IT, The Superior College Lahore, Pakistan 12

1.2. Motivations and Challenges

1.3. Goals and Objectives

1.4. Literature Review/Existing Solutions

Faculty of CS&IT, The Superior College Lahore, Pakistan 13

1.5. Gap Analysis

1.6. Proposed Solution

1.7. Project Plan

1.8. Report Outline

Faculty of CS&IT, The Superior College Lahore, Pakistan 14

Faculty of CS&IT, The Superior College Lahore, Pakistan 15

Faculty of CS&IT, The Superior College Lahore, Pakistan 16

Chapter 2: Software Requirement Specifications

2.1.3. Intended Audience and Reading Suggestions

Faculty of CS&IT, The Superior College Lahore, Pakistan 17

2.2. Overall Description

Faculty of CS&IT, The Superior College Lahore, Pakistan 18

Admin Admin can register a new member, instructor and equipment.

2.2.3. Operating Environment

2.2.4. Design and Implementation Constraints

Faculty of CS&IT, The Superior College Lahore, Pakistan 19

2.2.5. Assumptions and Dependencies

2.3. External Interface Requirements

2.3.1. User Interfaces

4.1.1. Hardware Interfaces

Faculty of CS&IT, The Superior College Lahore, Pakistan 20

4.1.3. Communications Interfaces

4.2. System Features

4.2.1. System Feature 1

Faculty of CS&IT, The Superior College Lahore, Pakistan 21

4.2.1.1. Description and Priority

4.2.1.2. Functional Requirements

4.2.2. System Feature 2

Faculty of CS&IT, The Superior College Lahore, Pakistan 22

4.2.2.1. Description and Priority

4.2.3. System Feature 3 (and so on)