GYM MANAGEMENT SYSTEM

Project done by
S. JANARTHANAN ( Reg.No.21CS0519)
V. NAVEEN ( Reg.No.21CS0528)
K. SUGUMAR ( Reg.No.21CS0550)
Under The Guidance
of
Mr. SHANMUGAM, MCA.,
Assistant Professor
Department of Computer Science
Project report submitted in partial fulfilment of the requirements for the Degree
of
BACHELOR OF SCIENCE
Of
Pondicherry University

DEPARTMENT OF COMPUTER SCIENCE

RAJIV GANDHI ARTS AND SCIENCE COLLEGE
Run by the Pondicherry Society for Higher Education
Accredited by NAAC with ‘B’ Grade
GOVERNMENT OF PUDUCHERRY
THAVALAKUPPAM, PUDUCHERRY-605 007.
MAY -2024

1
 BONAFIDE CERTIFICATE

This is to certify that the project work entitled “GYM MANAGEMENT

SYSTEM” is a Bonafide record of work done by JANARTHANAN S (Reg.No.21CS0519),

NAVEEN V(Reg.No.21CS08), SUGUMAR K(Reg.No.21CS0550) in partial fulfilment for the
degree of Bachelor of Computer Science of Pondicherry University.

This work has been submitted elsewhere for the award of Similar for any other Degree to the
best out knowledge.

INTERNAL GUIDE HEAD OF THEDEPARTENMENT

Mr. SHANMUGHAM, MCA., DR.N. GNANAMBIGAI, M.SC.,
Assistant Professor M. Phil, Ph.D.
Department of Computer Science Department of computer science
Rajiv Gandhi Arts and Science College Rajiv Gandhi Arts and Science College
Thavalakuppam. Thavalakuppam.

Submitted for the University Examination held on. ......................................at Rajiv Gandhi
Arts and Science College, Thavalakuppam, Pondicherry.

INTERNAL EXAMINER EXTERNAL EXAMINER

2
 ACKNOWLEDGEMENT

First and foremost, I would like to thank the Almighty for showering his blessings and
helping me to pursue and complete this project “GYM MANAGEMENT SYSTEM”
successfully.

The successful completion of any task would be incomplete without mentioning the
people who it possible. We thank this privilege to express a few words of gratitude and respect
to all those who helped us in completion of this project.

With profound gratitude, I thank Dr. J. HANNAH MONISHA, M.Sc., M.Phil., Ph.D.,
Principal of Rajiv Gandhi Arts and Science College, Thavalakuppam, Puducherry, who
has always been a constant source of inspiration not only during the project period, but also in
academic activities.

I am greatly indebted to thank DR.N. GNANAMBIGAI, M.SC., M.Phil., Ph.D. &

Head, Department of Computer Science time support for his valuable time support,
encouragement, excellent guidance and ideas, which enabled me for the successful completion
of this project work.

I express my deep sense of gratitude to Mrs. M. SHANMUGHAM, MCA., Assistant

Professor, Department of Computer Science for his valuable guidance, advice, support and
encouragement he had offered throughout my project work.

It’s my duty to thank my parents and my family members for their rich source of
inspiration and advice.

Last but not least I wish to thank all my friends for their constant source of
encouragement and motivation to carry out this project and for their timely help at critical
situation.

3
 ABSTRACT

A gym management system is basically software that is designed to seamlessly

integrate all aspects of your day to day activities of gym, allowing you to more easily and
efficiently run your gym management. The ultimate goal of a gym is to help make its members
healthier. Some health clubs require that new members undergo a health assessment. You will
be weighed and a staff member will measure your body fat composition.

4
 LIST OF TABLE

TABLE NO TITLES PAGE NO

TABLE 1 USER 35

TABLE 2 EQUIPMENT 36

TABLE 3 MEMBER 37

TABLE 4 SCHEDULE 38

TABLE 5 FEES 39

TABLE 6 ATTENDANCE 40

5
 LIST OF FIGURES

FIGURE NO TITLES PAGE NO

FIGURE 1 USE CASE DIAGRAM 43

FIGURE 2 DATAFLOW DIAGRAM 44, 45

6
 TABLE OF CONTENT

CHAPTER TITLE PAGE

NO NO

ACKNOWLEDGMEN
ABSTRACT
LIST OF TABLES AND FIGURES
1
INTRODUCTION
11
ABOUT THE PROJECT
PLAN OF THE PROJECT

PROBLEM DEFINITON AND FEASIBILUTY ANALYSIS

INTRODUCTION
PROBLEM DEFINITION

2 EXISTINGSYSTEM 13
PROPOSED SYSTEM
FEASIBILITY ANALYSIS
1. Economic Feasibility
2.Technical Feasibility
3. Social Feasibility

7
 SYSTEM REQUIREMENTS SPECIFICATION
INTRODUCTION
REQUIREMENT ANALYSIS
3 HARDWARE REQUIREMENT
SOFTWARE REQUIREMENT
17
FUNCTIONAL REQUIREMENT
TECHNICAL ISSUES
OTHER REQUIREMENTS
SOFTWARE ENVIRONMENTS

SYSTEMDESIGN –PRELIMINARY
INTRODUCTION
BASIC DESIGN APPROACH
USER INTERFACE DESIGN
4 DATABASE DESIGN 32
Table: USER
Table: FEES
Table: MEMBER
Table: EQUIPMENT
Table: ATTENDANCE
Table: SCHEDULE

8
 SYSTEM DESIGN- DETAILS
INTRODUCTION
MODULE
5 41
MODULE DESCRIPTION
USECASE DIAGRAM
DATAFLOW DIAGRAM

TESTING AND IMPLEMENTATION

INTRODUCTION
UNIT TESTING
6 INTEGRATION TESTING 47
VALIDATION TESTNG
SYSTEM TESTING
RECOVERY TESTING
PERFORMANCE TESTING

7 50
SCREENSHOTS

8 57
CONCLUSTION AND FUTURE ENHANCEMENTS
REFERENCES
9 59

9
INTRODUCTION

10
 CHAPTER – I
INTRODUCTION

1. ABOUT THE PROJECT

The title of the project is “GYM MANAGEMENT SYSTEM”. The aim of creating this
project is to bring every manual activity of the gym to the systematic. This helps making work
more easy for the gym admin and trainers as well as for user which is little bit complex because
doing it in manual manner.

Also helps to register the new gym member and also view the details of member and
their fee respectively.

Throughout the project the focus has been on presenting information and view details in
an easy and intelligible manner. The project is very useful for those who want to know about
“Gym Management System”.

1.2 PLAN OF THE PROJECT

To provide a view on the project, the report as been organize according to the develop
stages. It brings out all that was accomplished to implement the project.

CHAPTER-2:”Problem definition and feasibility analysis” gives a brief definition of the

problem persisting and the various feasibility measures needed to be adopted to solve the
problem.

CHAPTER-3:”software requirement specification” discusses the stated problem, the scope

of the application to be developed, existing system with its limitations and general description
of the desired solution.

CHAPTER-4:”System design” discusses the various design issues such as preliminary

design, detailed design and physical ad system architecture.

CHAPTER-5:”Testing and implementation” discusses about the Admin using application

and comfortable for using the software to manage the gym administration and their
implementation.

CHAPTER-6:”Conclusion and future enhancements” discusses the concluding remarks and

possible by which the system can be enhanced.

11
PROBLEM DEFINITION AND FEASIBILITY
ANALYSIS

12
 CHAPTER – II

PROBLEM DEFINITION AND FEASIBILITY ANALYSIS

2.1 INTRODUCTION

This chapter deals with the problem definition and feasibility analysis, which is an
important phase in the development of the project. Problem identification influences the whole
project and must be processed perfectly. The software requirement specification is produced at
the culmination of the analysis tasks. The function and performance allocated to software as a
part of system engineering are refined by establishing a complete information description,
detailed functional description, and design constraints, appropriate validation criteria and other
information pertinent to requirements. The proposed system handles all the essential activities
in the existing system. It is designed to speed up the existing process and provide the ability to
the user access the system on the move and ensures better user friendliness

The process of system analysis involves gathering of fact and figures about the
organization for which the new application is being developed. The process of system analysis
includes existing system along with the gathering of ideas that lead to the formation of the new
system. Analysis is the process of discovery, refinement, modeling and specification. The
information domain of the problem must be understood during analysis. The function and
behavior is to be defined. The analysis process should move form essential information toward
implement detail.

2.2. PROBLEM DEFINITION

The primary goal of our project is to replace the existing manual system. By a project it
is ensured that all necessary data are, available at all times. The existing manual system is time-
consuming process and laborious task. This finally result in large volume of data. The purpose
of our project in general is to reduce lot of paper work.

Economic expenditure, recovering nature and to provide quick and timely services are
considered as primary object of our project. The objective also extends to develop User -
friendly environment. This is to admin and user efficiently by giving accurate and up to data
information regarding all the factors existing related to our project.

13
2.2.1 EXISITING SYSTEM

In the present scenario, people have to physically visit the gym to know the detail about the
Equipment in a venues ..

In this method they have to do the work manually and they need to maintain the Gym
member data securely.

In this method, It require more time for admin of the Gym venue.

Also, the storing and retrieving an information is a difficult task, it also requires much
amount of unnecessary worker to do the task.

Generally, there is delay in the admission process, this is due to number of admission they
receive each day.

2.2.2 PROPOSED SYSTEM

Member can view themselves directly on the view user type option on application
through the their own id in desktop application

Admin will maintain the record by using the proper table to save records so that no
one can access it and make the data safe.

Member can check new information related to gym and health through the
application which will motivate them and all things would be uploaded from the admin's end.

2.3 FEASIBILITY ANALYSIS

The feasibility of the project is analyzed in this phase and business proposal is put forth
with a very general plan for the project and some cost estimates. During system analysis the
feasibility study of the proposed system is to be carried out. This is to ensure that the proposed
system is not a burden to the company. For feasibility analysis, some understanding of the
major requirements for the system is essential.

Three key considerations involved in the feasibility analysis are :

ECONOMICAL FEASIBILITY

TECHNICAL FEASIBILITY

SOCIAL FEASIBILITY

14
2.3.1 Economical Feasibility

This study is carried out to check the economic impact that the system will have on the
organization. The amount of fund that the company can pour into the research and development
of the system is limited. The expenditures must be justified. Thus the developed system as well
within the budget and this was achieved because most of the technologies used are freely
available. Only the customized products had to be purchased.

2.3.2 Technical Feasibility

This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on the
available technical resources. This will lead to high demands on the available technical
resources. This will lead to high demands being placed on the client. The developed system
must have a modest requirement, as only minimal or null changes are required for
implementing this system.

2.3.3 Social Feasibility

The aspect of study is to check the level of acceptance of the system by the user. This
includes the process of training the user to use the system efficiently. The user must not feel
threatened by the system, instead must accept it as a necessity. The level of acceptance by the
users solely depends on the methods that are employed to educate the user about the system
and to make him familiar with it. His level of confidence must be raised so that he is also able
to make some constructive criticism, which is welcomed, as he is the final user of the system.

15
SYSTEM REQUIRMENTS SPECIFICATION

16
 CHAPTER – III
SOFTWARE REQUIRMENTS SPECIFICATION

3.1 INTRODUCTION
Requirement specification involves studying the current business system to find out how
it works and where improvements should be made. The requirement is the feature that must be
included in a new system. The analysis of requirements should study and collecting the details
of existing system. Software requirements specification (SRS) is the technical way of

expressing the requirements for software product. It is treated as the first task of development
Process. The proposed system handles additional activities in the existing system.

The software requirements specification is produced at the conclusion of the analysis

tasks. The function and performance allocated to software as part of system engineering are
refined by establishing a complete information description, detailed functional description, and
a representation of system behavior, on indication of performance requirements and design
constraints, appropriate validation criteria and other information relevant to requirements.

3.2 REQUIREMENT ANALYSIS

The requirement analysis can build to generate the development of the project
requirements and the purpose of the document may involve maintain the details in performance
of the requirement specification .

3.2.1 Purpose

This project is aimed to develop the “Gym Management system ” for reducing the manual
evaluating the performance of the admin and give the accurate result for the gym member up
to date data performance.

3.2.2 Scope

Developing a desktop application for gym management presents a wide scope for
addressing various needs within the fitness industry. Here are several areas where such an
application could be valuable. By addressing these aspects comprehensively, a gym

17
management desktop application can streamline operations, enhance member experience, and
contribute to the overall success of fitness businesses.

3.2.3 Overview

The SRS document for the system covers the following two sections.

General description, this section provides overall description of the system, which
includes an overview of the .net components, functions and features. It describes user’s
characteristics, general constraints, and all assumption and dependencies.

Specific requirements, this section describes both functional and non- functional
requirements of the system. The functional requirement of the system. The functional
requirements section defines the system’s requirement specifications form functionalities point
of view. The non- function requirements section defines the system’s external interface, general
requirements, performance requirements, design constrains, etc. Which are dealt in
corresponding sub-sections.

3.2.4 General Description

The general description specify the software functionally and constraints on its defined
operation. The project construction shall be designed to run on a deployment or comparable
processor. The host computer shall have at least 2GB of installed STORAGE is preferable. The
host computer shall run Microsoft Windows.

3.2.5 Functional Requirement

This sub-section of the SRS provides a summary of the functions that the individual
modules should perform. The functional requirement may include technical status of the
project, risk analysis and economical issues.

3.2.5.1 Technical Issues

It checks whether the proposed system can be by built with the existing technologies. It
includes the study of functions, performance and constraints that may after the ability to
achieve and acceptable system.

18
3.2.5.2 Risk Analysis

Risk analysis and management are a series of steps that helps us understand and manage
uncertainly. We should identify assets, manage and monitor the risk that are involved in our
project. The basic risk that was encountered by our team is to deliver the software product
within the stipulated time.

3.3 HARDWARE REQUIREMENTS

• Processor : intel i5
• Input Devices : Keyboard, Mouse
• Ram : 4GB

3.4 SOFTWARE REQUIREMENTS

• Operating System : Windows . 11
• Coding Language : Application Window(vb.net)
• Tool : Visual Basic
• Database : Micro Soft Access

3.5 FUNCTIONAL REQUIREMENTS

The relationship between Input and Output to the system is determined by the functional
requirement of the Software Requirement Specifications. The system should provide how the
system should react to particular inputs and how the system should behave in particular
situations. Functional requirements may be calculations, technical details, data manipulation
and processing and other specific functionality that define what a system is supposed to
accomplish.

3.5.1 Behavioral Requirements

Behavioral requirements explain what has to be done by identifying the necessary behavior
of a system. Behavioral requirements used to tell about both the functional and non-functional
requirements of the system.

The behavioral part of the requirements specification language distinguishes between

functional and behavioral Requirements.

19
3.6 TECHNICAL ISSUES

The proposed system is developed with:

VB.NET - Front End

MICRO SOFT ACCESS - Back End

The front end with .NET is platform dependent and its user friendly. The login detail of
the user is used for authentication. So, Server is used as the back end. It acts as the back end
with security of the Data. This has the filename and secret key as its set of datasets. Each new
set of user has the datasets of filename and secret key details.

3.7 OTHER REQUIREMENTS

3.7.1 Performance Requirements

The performance requirements are specified below:

The prime requirement is that no error condition causes a project to exit abruptly.

All the system generated errors is directed to a separate page through proper ‘try
and catch’ block. The response to any sort of query is fairly fast.

Any error occurred in any process should return an error messages about the
nature of the error that is clear to the user.

3.7.2 External Interface Requirements

External interface requirements specify hardware, software, or database elements with

which a system or component must interface. It provides information to ensure that the system
will communicate properly with external components. A complex system with multiple
subcomponents should use a separate interface specification or system architecture
specification.

This is used to estimate the effort required to identify and document the interfaces to
other systems and external entities within the project scope. The effort to identify and document
the external interface requirements includes defining business elements for each external
interface.

20
3.7.3 Design Constraints

When designing and creating constraints, it is a good idea to use a naming convention that
properly identifies the different types constraints. This is particularly important for diagnosing
errors that might occur.

3.7.4 Security Requirements

Network Applications are available via network access, it is difficult, if not impossible,
to limit the population of end-users who may access the application. In order to protect sensitive
content and provide secure modes of data transmission, strong security measures must be
implemented. Security has to be enforced at two levels. At first level, no one other than the
person, who knows the user name and password, can be able to logon to the system. At the next
level, measures have to be taken so that any normal person does not exercise any of the
administrator rights.

3.7.5 Maintainability Requirements

The term software maintenance is commonly used to refer to the modifications that are
made to a software system in its initial release. This system is developed with ease of
maintenance in mind. The modules in this project are clearly documented and have power over
the least degree of coupling so that they can be modified independently.

3.7.6 Usability Requirements

Since the system is placed on for network users, any type users can use the system. The
system provides GUI interface for the users. The system provides in for to the users according
to their accessibility level.

3.7.7 Portability Requirements

Portability in high-level computer programming is the usability of the same software in

different environments. The pre requirement for portability is the generalized abstraction
between the application logic and system interfaces. When software with the same functionality
is produced for several computing platforms, portability is the key issue for development cost
reduction.

21
3.7.8 Efficiency Requirements

This system is highly efficient in providing the required functionalities through efficient
coding that utilizes less time and storage. Quick time and time services are also provided.

3.8.2 THE .NET FRAMEWORK

The .NET Framework has two main parts:

1. The Common Language Runtime (CLR).

2. A hierarchical set of class libraries.

The CLR is described as the “execution engine” of .NET. It provides the environment within
which programs run. The most important features are

Conversion from a low-level assembler-style language, called Inter mediat

Language (IL), into code native to the platform being executed on.

Memory management, notably including garbage collection.

Checking and enforcing security restrictions on the running code.

Loading and executing programs, with version control and other such
features.

The following features of the .NET framework are also worth description.

Managed code

The code that targets .NET and which contains certain extra information - “metadata” to
describe itself. While both managed and unmanaged code can run in the runtime, only managed
code contains the information that allows the CLR to guarantee, for instance, safe execution
and interoperability.

Managed Data

With Managed Code comes Managed Data. CLR provides memory allocation and Deal
location facilities, and garbage collection. Some .NET languages use Managed Data by default,
such as C#, Visual Basic.NET and Jscript.NET, whereas others, namely C++, do not.

22
Targeting CLR can, depending on the language you’re using, impose certain constraints on the
features available. As with managed and unmanaged code, one can have both managed and
unmanaged data in .NET application – data that doesn’t get garbage collected but instead is
looked after by unmanaged code.

Common Type System

The CLR uses something called the Common Type System (CTS) to strictly enforce
type-safety. This ensures that all classes are compatible with each other, by describing types in
a common way. CTS define how types work within the runtime, which enables types in one
language to interoperate with types in another language, including cross-language exception
handling. As well as ensuring that types are only used appropriate ways, the runtime also
ensures that code doesn’t attempt to access memory that has not been allocated to it.

Common Language Specification

The CLR provides built-in support for language interoperability. To ensure that you can
develop managed code that can be fully used by developers using any programming language,
set of language features and rules for using them called the Common Language Specification
(CLs) has been defined. Components that follow these rules and expose only CLS features are
considered CLS-compliant.

3.8.3 THE CLASS LIBRARY

.NET provides a single-rooted hierarchy of classes, containing over 7000 types. The root
of the namespace is called System; this contains basic types like Byte, Double, Boolean, and
String, as well as Object. All objects derive from system. Object. As well as objects, there are
value types. Value types can be allocated on the stack, which can provide useful flexibility.

There are also efficient means of conversion value types to object types if and when
necessary. The set of classes is pretty comprehensive, providing collections, file, screen, and
network I/O, threading, and so on, as well as XML and database connectivity. The class library
is subdivided into a number of sets (or namespaces), each providing distinct areas of
functionality, with dependencies between the namespaces kept to a minimum.

23
Languages Supported By .NET

The multi-language capability of the .NET Framework and Visual Studio.NET enables
developers to use their existing programming skills to built all types of application and XML
Web services. The .NET framework supports new versions of Microsoft’s old favorites Visual
Basic and C++ (as VB.NET and Managed C++), but there are also a number of new additions
to the family.

Visual Basic .NET has been updated to include many new and improved language
features that make it a powerful object-oriented programming language. These features include
inheritance, interfaces, and overloading, among others. Visual Basic also now supports
structured exception handling, custom attributes and also supports mult-threading.

Visual Basic.NET is also CLS compliant, which means that any CLS- compliant
language can use the classes, objects, and components you create in Visual Basic.NET.

Managed Extensions for C++ and attribute programming are just some of the
enhancements made to the C++ language. Managed Extensions simplify the task of migrating
existing C++ applications to the new .NET Framework.

Microsoft Visual J#.NET provides the easiest transition for Java- language developers
into the world of XML Web Services and dramatically improves the interoperability of Java
language programs with existing software written in a variety of other programming languages.

Other languages for which .NET compilers are available include

FORTRAN
COBOL
EIFFEL

24
C#.NET is also compliant with CLS(Common Language Specification) and supports structured
exception handling. CLS is set of rules and constructs that are supported by the CLR (Common
Language Runtime). CLR is the runtime environment provided by the .NET Framework it
manages the execution of the code and also makes the development process easier by providing
services.

3.8.4 CONSTRUCTIONS AND DESTRUCTIONS

Constructions are used to initialize objects, whereas destructions are used to destroy
them. In other words, destructions are used to release the resources allocated to the object. In
C#.NET the sub finalize procedure is available. The sub finalize procedure is used to complete
the tasks that must be performed when an object is destroyed. The sub finalize procedure can
be called only from the class it belongs to or from derived classes.

3.8.5 GARBAGE COLLECTION

Garbage collection is another new feature in C#.NET. The .NET Framework monitors
allocated resources, such as objects and variables. In addition, the .NET Framework
automatically releases memory for reuse by destroying objects that are no longer in use.

3.8.6 OVERLOADING

Overloading is another feature in C#. Overloading enables us to define multiple

procedures with the same name, where each procedure has a different set of arguments. Besides
using overloading for procedure. We can use it for constructors and properties in a class.

3.8.7 MULTITHREADING

C#.NET also supports multithreading. An application that supports multithreading can

handle multiple tasks simultaneously, we can use multithreading to decrease the time taken by
an application to respond to user interaction.

3.8.8 STRUCTURED EXCEPTION HANDLING

C#.NET supports structured handling, which enables us to detect and remove errors ata
runtime. In C#.NET, we need to use Try…Catch…Finally statements to create exception
handlers. Using Try…Catch…Finally statements. We can create robust and effective exception
handlers to improve the performance of our application.

25
3.8.9 THE .NET FRAMEWORK

The .NET Framework is a new computing platform that simplifies application

development in the highly distributed environment of the internet.

3.8.10 OBJECTIVES OF .NET FRAMEWORK

There are different types of application, such as Windows-based applications and Web-based
application.

To provide a consistent object-oriented programming environment whether object

codes is stored and executed locally on Internet –distributed, or executed remotely.

To provide a code-execution environment to minimize software deployment

guarantees safe execution of code.

Eliminates the performance problems.

VISUAL BASIC ( FORM APPLICATION )

A Windows Forms application in Visual Basic (VB) refers to a type of application built
using the Windows Forms framework within the Visual Basic programming language. Here's
a breakdown of its definition and explanation:

1. Windows Forms (WinForms): Windows Forms is a graphical user interface (GUI)

framework provided by Microsoft for creating desktop applications on the Windows platform.
It allows developers to create rich, interactive user interfaces using a drag-and-drop design
approach.

2. Visual Basic (VB) :Visual Basic is a programming language developed by

Microsoft. It's known for its simplicity and ease of use, making it a popular choice for
developing Windows applications. Visual Basic is often used in conjunction with the .NET
Framework, which provides a vast library of classes and functionalities for building Windows
applications.

3. Forms: In a Windows Forms application, a form is a window or dialog box that

serves as the primary user interface element. Forms can contain various controls such as
buttons, textboxes, labels, and more, allowing users to interact with the application.

4. Application: A Windows Forms application built in Visual Basic is a standalone

program designed to run on a Windows-based computer. It typically has a graphical user

26
interface that users interact with to perform tasks or access features provided by the application.

Key Components of a Windows Forms Application in Visual Basic

Form Designer: Visual Studio, the integrated development environment (IDE) for
Visual Basic, provides a Form Designer tool that allows developers to visually design forms
by dragging and dropping controls onto a design surface. Developers can then customize the
appearance and behavior of these controls using properties and event handlers.

Code-behind: Behind the visual design of forms lies the code-behind file, typically
written in Visual Basic. This file contains the logic and functionality of the application,
including event handlers for user interactions, data processing, and integration with other
components or services.

Controls: Controls are user interface elements such as buttons, textboxes, checkboxes,
listboxes, and more, which are placed on forms to provide functionality and interactivity.
Developers can customize the properties and behavior of these controls to suit the requirements
of the application.

Event-driven Programming: Windows Forms applications are typically event-driven,

meaning they respond to user actions or system events by executing specific blocks of code.
Developers write event handlers to define how the application should respond to events such
as button clicks, mouse movements, or form loading.

Data Access and Manipulation: Windows Forms applications often interact with data,
such as retrieving information from databases, processing user input, and displaying results.
Visual Basic provides libraries and tools for data access and manipulation, allowing developers
to integrate data-driven functionality into their applications.

In summary, a Windows Forms application in Visual Basic is a desktop application built

using the Windows Forms framework within the Visual Basic programming language. It
consists of forms, controls, code-behind logic, and event-driven programming to create
interactive and functional user interfaces for Windows-based computers.

27
Desktop applications offer several benefits that make them a preferred
choice for certain use cases:

1. Performance: Desktop applications typically run directly on the user's computer, leveraging
its resources fully. This can result in faster performance compared to web applications,
especially for tasks that require intensive processing or access to local hardware.

2. Offline Access: Unlike web applications that require an internet connection to

function, desktop applications can often operate offline. This is beneficial for users who need
to work in environments with limited or no internet connectivity.

3. Rich User Interface: Desktop applications can provide a more immersive and
feature-rich user interface compared to web applications. They can leverage native operating
system controls and graphics libraries to create visually appealing and highly interactive
interfaces.

4. Access to Local Resources: Desktop applications have access to the full range of
local resources on the user's computer, including files, hardware devices (such as printers and
scanners), and peripherals. This allows them to integrate more seamlessly with the user's
environment and perform tasks that web applications cannot, such as accessing USB devices
or interacting with system settings.

5. Security: Desktop applications can offer greater security and data privacy compared
to web applications. Since they run locally on the user's computer, sensitive data may be less
vulnerable to attacks such as cross-site scripting or SQL injection.

6. Customization and Integration: Desktop applications can be customized to meet

the specific needs of users or organizations. They can also integrate more deeply with other
desktop software or services, allowing for seamless workflow automation and interoperability.

7. Better Control: Users have more control over desktop applications, including
installation, updates, and configuration. This can be advantageous for businesses that require
strict control over their software environment or need to comply with regulatory requirements.

28
 8. Performance Stability: Since desktop applications are not dependent on external
factors such as internet speed or server availability, their performance tends to be more stable
and predictable.

9. Monetization Opportunities: Desktop applications can be monetized through

various models, including one-time purchases, subscriptions, or in-app purchases. This
provides opportunities for developers to generate revenue directly from their software.

10. Offline Data Storage: Desktop applications can store data locally on the user's
computer, allowing for faster access and reducing reliance on external servers. This can be
particularly useful for applications that handle large volumes of data or require frequent access
to stored information.

Overall, desktop applications offer a range of benefits that make them well-suited for
certain use cases, particularly those that require high performance, offline access, access to
local resources, and a rich user interface.

Desktop applications have several characteristics that distinguish them from

other types of software applications:

1. Platform Specificity: Desktop applications are designed to run on specific operating

systems, such as Windows, macOS, or Linux. They are typically developed using programming
languages and frameworks that are native to the target platform.

2. Installed Locally: Desktop applications are installed directly on the user's computer
and run locally, utilizing the resources of the user's device. This allows for faster performance
and access to local hardware.

3. Graphical User Interface (GUI): Desktop applications typically have a

graphical user interface (GUI) that allows users to interact with the software through visual
elements such as windows, buttons, menus, and dialog boxes. The GUI provides an intuitive
way for users to navigate and use the application.

4. Offline Access: Unlike web applications that require an internet connection to

function, desktop applications can often operate offline. They store data and resources locally,
allowing users to access and use the application even when disconnected from the internet.

29
 5. Access to Local Resources: Desktop applications have access to the full range of
local resources on the user's computer, including files, hardware devices (such as printers and
scanners), and peripherals. This allows them to interact with the user's environment and
integrate with other software installed on the system.

6. Customization: Desktop applications can be customized to meet the specific needs

of users or organizations. They can be tailored to fit different screen sizes, resolutions, and
hardware configurations, providing a more personalized user experience.

7. Security: Desktop applications can offer greater security and data privacy
compared to web applications. Since they run locally on the user's computer, sensitive data may
be less vulnerable to attacks such as cross-site scripting or SQL injection.

8. Performance: Desktop applications typically offer better performance compared to

web applications, especially for tasks that require intensive processing or access to local
resources. They can leverage the full power of the user's device, resulting in faster response
times and smoother user interactions.

9. Installation and Updates: Desktop applications require installation on the user's

computer, either through an installer or by copying files to the system. They may also require
periodic updates to add new features, fix bugs, or address security vulnerabilities.

10. Distribution: Desktop applications can be distributed through various channels,

including direct downloads from the developer's website, distribution platforms such as the
Microsoft Store or the Mac App Store, or physical media such as CDs or USB drives.

These characteristics make desktop applications well-suited for a wide range of use
cases, including productivity tools, multimedia applications, games, and business software.
They provide a rich user experience, high performance, and access to local resources, making
them a popular choice for both developers and users alike.

MICRO SOFT ACCESS (DATA BASE)

Features of SQL server Microsoft Access is a relational database management system

(RDBMS) developed by Microsoft. It provides a user-friendly interface and tools for creating,
managing, and using databases. Here's a breakdown of the key components and features of a
Microsoft Access database:

30
SYSTEM DESIGN – PRELIMINARY

31
 CHAPTER - IV

SYSTEM DESIGN - PRELIMINARY

4.1 INTRODUCTION

A System Requirements Specification (SRS) is a document where the of a system that

is planned is to be developed. To be used efficiently, all compute software needs certain
hardware components or other software resources to be present on a computer system. These
pre-requisites are known as system requirements.

This document describes the requirement of the system. It is meant for use by the
developers and will be on the basis for validating the final delivered system of the design. This
gives an overall developed plan for the process structure to be developed.

Any changes made to the requirements in the future will have to go through a formal
change approval process. The developer is responsible for asking for clarification. Wherever it
is necessary, and will not make any alteration without the permission of the client.

4.2 BASIC DESIGN APPROACH

The system follows “Water Fall Model” which demands a systematic, sequential
approach to software development with the following phases: Problem Definition, Analysis,
Design, Coding, Testing, Integration and Maintenance.

The water fall model follows the “Top-Down approach” to developing the software.
The Top-Down approach starts with a more general conceptualization of the system and then
elaborated the design in a more detailed manner.

4.2.1 Software Engineering Paradigm Applied

Software Engineering is a planned and systematic approach to the development of

software. It is a discipline that consists of methods, tools and techniques used for developing
and maintaining software.

To solve actual problems in an industry setting, a software engineer or team of engineers

must incorporate a development strategy that encompasses the process, methods and tool layers
and generic phases. This strategy is often referred to as a process model or Software
Engineering paradigm.

32
 It consists of various models. Each model has its own specific steps for software
development. A suitable development model is selected by considering several factors like
requirement, application type, and application software to be used for development etc.

Water fall model

In waterfall model, I proceed from one phase to the next in a sequential manner.
Requirement Analysis, Design, Implementation, Testing, Deployment and Maintenance are the
different sequential phases. The objective of testing is to uncover errors. Thus the waterfall
model insists that proceed to the next phase only after completing previous phase perfectly.
Waterfall model is also known as classic life cycle model. Iterative water fall model The
Iterative water fall model approach overcomes the problems associated with the waterfall
model approach. If any difficulty or problem encounter in any phase may require going back
to the previous phase and performing the required modifications and proceeds sequentially.

Iterative water fall model

Iterative water fall model approach overcomes the problems associated with the
waterfall model approach. If any difficulty or problem encounter in any phase may require
going back to the previous phase and performing the required modifications and proceeds
sequentially.

Prototyping model

After the requirement analysis a quick design is done. That is a working model of the
intended software is constructed. This focuses on a representation of the software that will be
visible to the user. This working model of the software is termed as a prototype. This prototype
is evaluated by the customer to ensure that all the requirements are incorporated.

The prototype will be modified according to the customer's suggestions. This process will be
repeated until I get a fully functional working model that satisfies all user requirements. Ideally
prototyping is a mechanism for identifying user requirements.

4.3 USER INTERFACE DESIGN

The format of the all interfaces was designed as possible as easy understanding and user
friendly. Pages were connected to each other in a consistent way. Operations that are done with
the system were repeatable. The design of the pages allows the users to use this easily.

33
4.3.1 Modularity

The concept of modularity in software has been espoused for almost 5 decades.
Software architecture embodies modularity ie, software is divided into separately name and
addressable, often called modules, which are integrated to satisfy problem requirements.
Modularity is the single attribute of software that allows a program to be intellectually
manageable.

4.3.2 Coupling

Coupling is an measure of the relative interdependence among modules. Coupling

depends on the interface complexity between modules, the point at which entry or reference is
made to a module, and what data pass across the interface.

4.3.3 Cohesion

Cohesion is a measure of the relative functional strength of a module. A cohesive

module performs a single task, requiring little interaction with other components in other parts
of a program. Stated simply, a cohesive module should (ideally) do just one thing.

4.4 DATABASE DESIGN

Usually, a collection of interrelated data referred to a database. The database contains

information about one particular enterprise. Database systems are design stir and manage large
volume of information. The management of data involves both the definitions of structure for
the storage of information provision of mechanism for manipulation of information. In addition
the database system must provide for safety information stored in the

database, despite system crashes or unauthorized access.

34
 4.4.1 TABLE DESIGN

Table name: USER1

FIELD NAME DATA TYPE SIZE CONSTRAINT DESCRIPTION

SNO

1 USERID TEXT 20 PRIMARY KEY USER ID FOR ADMIN

LOGIN ACCOUNT
2 PASSWORD1 TEXT 20 NOT NULL
PASSWORD

ADMIN OR
3 USERTYPE TEXT 20 NOT NULL
USERTYPE

4 GENDER TEXT 20 NOT NULL FIND THE GENDER

PHONE NUMBER FOR

5 PHONENO INT 10 NOT NULL
USER

7 EMAIL TEXT 30 NOT NULL EMAIL FOR USER

35
 Table name: EQUIPEMENT

SNO FIELD NAME DATA TYPE SIZE CONSTRAINT DISCRIPTION

1 EQUIPMENT TEXT 30 PRIMARY KEY NAME OF EQUIPMENT

2 COST INT 30 NOT NULL COST OF EQUIPMENT

3 DATE1 INT 10 NOT NULL DATE OF INTALLATION

4 QUANTITY INT 50 NOT NULL NO OF EQUIPMENT

5 WORKOUT TEXT 20 NOT NULL USE OF EQUIPMENT

36
 Table name: MEMBER (register)

SNO FIELD NAME DATA TYPE SIZE CONSTRAINT DISCRIPTION

USER ID OF REGISRTER
1 RID TEXT 30 PRIMARY KEY
PERSON

2 NAME TEXT 30 NOT NULL NAME OF THE MEMBER

3 FNAME TEXT 30 NOT NULL FATHER NAME

4 BG VARCHAR 10 NOT NULL BLOOD GROUP

5 ADD1 TEXT 20 NOT NULL ADDRESS OF MEMBER

CONTECT FOR
6 CON TEXT 30 NOT NULL
REGISTER MEMBER

37
 Table name: FEES (register)

SNO FIELD NAME DATA TYPE SIZE CONSTRAINT DISCRIPTION

USER ID OF
1 FID TEXT 30 PRIMARY KEY
REGISRTER PERSON

NAME OF THE
2 NAME1 TEXT 30 NOT NULL
MEMBER

3 FEES1 TEXT 30 NOT NULL FEES TYPE

4 AMOUNT1 INT 10 NOT NULL AMOUNT OF FEES

5 MONTH1 TEXT 20 NOT NULL FEES MONTH

STATUS OF FEES PAID

6 STA1 TEXT 30 NOT NULL
OR PENDING

38
 Table name: Schedule (register)

SNO FIELD NAME DATA TYPE SIZE CONSTRAINT DISCRIPTION

USER ID OF REGISRTER
1 TID TEXT 30 PRIMARY KEY
PERSON

2 NAM2 TEXT 30 NOT NULL NAME OF THE MEMBER

WORKOUT DATE OF
3 DT2 INT 30 NOT NULL
MEMBR

4 SES2 TEXT 20 NOT NULL SESSION OF WORKOUT

HIGHT FOR THE

5 HGT2 INT 20 NOT NULL
MEMBER

WEIGHT FOR THE

6 WGT2 INT 30 NOT NULL
MEMBER

39
 Table name: ATN (register)

SNO FIELD NAME DATA TYPE SIZE CONSTRAINT DISCRIPTION

USER ID OF
1 TID TEXT 30 PRIMARY KEY
REGISRTER PERSON

NAME OF THE
2 NAME3 TEXT 30 NOT NULL
MEMBER

WORKOUT DATE OF
3 DATE3 INT 30 NOT NULL
MEMBR

4 SESSION3 TEXT 20 NOT NULL SESSION OF WORKOUT

5 DAY3 TEXT 20 NOT NULL DAY OF PRESENT

6 STATUS3 TEXT 30 NOT NULL PRESENT OR ABSENT

40
SYSTEM DESIGN DETAILS

CHAPTER – V

41
 SYSTEM DESIGN DETAILS

5.1 INTRODUCTION
This project consists of three modules namely,

1. Login Module
2. Admin Module
3. Register Module
4. User attendance Module

5.2 MODULES-PURPOSE AND DESCRIPTION

Login Module:

In this module, the administrator can add the account details like as the
admin name , contact person , address . The module also enable the admin to add
the user type account . The login module to save in data base to authentication of
user name, password , and user type to login move to verified the admin or user
type and show the form of admin form or user form.

a. Login form--------→ admin form

b. Login form-------→ user type form

Admin Module

In this module enable the admin to register the new member and created
the data in database connection.

• Register
• Fees register
• Equipment
• Time and schedule
• View details

42
User type Module

This module enable the user type login to show the view form . It contains
with the view details and attendance register of the member in gym academy. And
also see the data to search and see from with data base

• Attendance
• View details

USECASE DIAGRAM:

43
DATA FLOW DIAGRAM

Admin Activity:

44
USER ACTIVITY:

45
TESTING AND IMPLEMENTATION

46
 CHAPTER – VI
TESTING AND IMPLEMENTATION
6.1 INTRODUCTION
Coding is the process of converting the design specifications in to source code.
Implementing the design properly makes the system complete. Although the time spent in
coding is small when total sequence of software development, cost is considered. The cost of
testing and maintenance are highly dependent on coding phase.

A typical visual basic application development environment is adopted to develop the

system logic and the user interface of the software.

Coding Standards:

The first few lines are used for comments that describe the purpose of the form.

Description names are used for all variables, function names and constants.

Variable names start with lowercase.

Multiword identifiers are internally separated by underscore.

Single letter identifiers are used as counter variable in looping constructs.

Enough spacing is used to separate logical sections of code.

All the functions and subroutines names begin with a lowercase letter

To create function for text validation

To create the event for the tool bar properties

To connect data base with code line using the provider

6.2 TESTING

The performance of any system reflects the amount of testing done on it. In every project
a crucial part is testing the activities, which help to access and improve the quality of product
that generates during the expansion and modification of the software. Quality attributes include
correctness, reliability efficiency and performance of standards and overall cost effectiveness.
Software testing is a critical element of software quality assurance and signifies the final review
of specification, design and coding. The testing objectives are

47
 To finding an error while executing a program in the process of testing.

To finding an as-yet undiscovered error is an excellent test case.

A successful test is one that expose an as-yet undiscovered inaccuracy.

6.3 UNIT TESTING

Unit testing comprises the set of test cases performed by an individual programmer prior
to combination of the unit into a large system. All four categories of test involving the unit
testing were performed. Applying the code with small input values for which the expected
results were known performed functional tests.

Performance tests were conducted to determine the program throughout and response
time stress and structural tests were also conducted to intentionally break the system and to
check the execution parts of the system respectively.

Test Cases

If a module is data coupled with another module, the unit testing was performed with dummy
values. For all modules, confirmation to consistent user interface was mainly checked.
Validations are done at each and every stage. Checks have been made in each and every unit
by giving invalid data and the system is found to found to function successfully in all units.
Thus unit-wise testing uncovers most of the errors.

6.4 INTEGRATION TESTING

Integration testing was performed in a regressive way. As and when a module was developed
and tested, it was integrated with the remaining modules. Bottom-up testing strategy was
followed in each case. Modules were integrated moving upward the control hierarchy. In
“GYM Management System” all the modules were tested individually first with testing in all
cases. Then they were integrated with the next higher level module. Within a module, the
subsystem was focused on those modules, which were tightly coupled. After a full-fledged
integration of all the modules to the main form, the application was tested for interface errors;
a correction error etc., and was corrected to work

successfully.

48
6.5 VALIDATION TESTING

Validation testing plays an important role. The application was developed especially for the
company and so it is necessary to confirm, whether the right details have been entered? Each
and sub-module was tested, whether it is provided the required functionalities? Each input field
was tested with the validation rules specified.

6.6 SYSTEM TESTING

The main purpose of a system testing is to fully exercise the computer- based system. The
following are the types of system tests that are performed in this application.

6.7 RECOVERY TESTING

The system was forced to fall in a variety of ways and verified whether recovery was properly
performed.

6.8 PERFORMANCE TESTING

Performance testing is designed to test the run-time performance of the software within the
environment of an integrated system. Performance testing determines the amount of execution
time spent in various parts of the program throughout and response times.

Implementation

Implementation is the final stage of the project when theoretical design is turned into a working
system. It involves careful planning, investigation of current system and its constraints on
implementation, design of methods to achieve the changeover, training of staff in the
changeover procedures and evaluation of changeover methods. The programs, which are
developed earlier, are linked properly and put into operation with test data. The phase concludes
with the maintenance of the resources necessary, both hardware and software. The project was
implemented after completion of the coding and testing in the developer’s workplace and
proved to satisfy the user requirements.

49
SCREEN SHORT

50
Figure 1: LOGIN Page

Figure 2:ADMIN ACCESS Page

51
Figure 3: NEW MEMBER REGISTER Page

Figure 4: FEES UPDATE Page

52
Figure 5: HEALTH AND TIME UPDATE Page

Figure 6: VIEW DETAILS Page

53
Figure 7 : USER ACCESS Page

Figure 8 : USER ATTENDANCE Page

54
Figure 9 : EQUIPMENT Page

Figure 10 : DATA BASE Page

55
CONCLUSION

56
 CHAPTER – VII

CONCLUSION AND FUTURE ENHANCEMENTS

This project is developed for managing a GYM management system and it

has successfully runs, such points are out of knowledge of its developer, but the
every included parts of this project is enough efficient to use it on a Gym
management system. Mostly used in this project to calculate necessary outputs as
needing. Nevertheless, the user should benefit enormously from the automating
management processes of Academy management. Also, the probability of error
should be reduce a significantly. The project makes a small beginning with a small
foray into the field of accounting. It shall be our endeavor to pursue the project
further and develop newer application from it, offering an enhanced courses.

57
REFERENCES

58
 CHAPTER VIII
BIBLIOGRAPHY
REFERENCES
Books:
1. Robert J. Oberg, Introduction to vb.net using .NET ,PHI,2002.
2. Andrew Troelsen, C# and .NET Platform , A press, 1st edition,2001.
3. Ben Albahari, Peter Drayton and Brad Merrill, C# Essentials
,SPD,2001.
4. Microsoft C# Language Specifications, WP Publishers and
Distributors Pvt.Ltd.,2001
5. RogerS. Pressman, Software Engineering: A practitioner’s
Approach, McGraw-Hill Components Inc., 2001.
6. Richard E. Fairley, Software Engineering Concepts, Tata McGraw-
Hill
Publishing Company Limited, New Delhi, 1997
Websites:
http://www.w3schools.com

http://www.researchgate.net/publication/2862568_Temporal_Constraint_Reasoning_With_Pr
eferences
http://sherpa.hepforge.org/theses/diss_schaelicke.pdf
http://homepages.ius.edu/rwisman/C455/html/notes/Chapter22/TopSor
t.htm

http://www.personal.kent.edu/~rmuhamma/Algorithms/MyAlgorithms/GraphAlgor/topoSort.
htm

59