Case Study 79
Case Study 79
On
One Pacific Health Club
Submitted By
Ankit Pangeni
Kushal Subedi
Surya Lamsal
Submitted To
Raghu Gyawali
CHAPTER ONE
INTRODUCTION
1.1 Introduction
One Pacific Health Club is a health club located in Pokhara. The aim of this
club is to promote a healthy lifestyle. It offers an extensive selection of club
facilities and classes such as aerobics, yoga and fully-equipped gymnasium
with well-trained instructors experienced in tailoring individual and group
programme. Our team has developed a system to facilitate the club. This
system helps to manage various operations in One Pacific Health Club.
1.3 Objectives
The objective of this case study is to develop a system for One Pacific Health
Club in order to automate all the operations. The main objectives are given
below:
Membership management
Payment and billing management
Members attendance management
Management of instructors and classes details
Report management
1.4 Scope and Limitation
Scope:
The scope of this case study is to analyse and study all the operations of the
club which were all manually done previously and try to automate them
through our system. The main scopes are given below:
Limitation:
Our system will be only available to Windows but not to Linux or any
other operating systems.
Each and every part of the system is not described here.
This case study report is separated into different chapters. Each chapter consists
of various sub-chapters with the content. The opening section of the report
consists of cover page.
In this case study report, the first chapter contains the introduction and its sub
chapters. The sub chapters of Introduction part include Introduction, Problem
statement, Objectives, Scope and Limitation, Development Methodology and
Report Organization.
CHAPTER TWO
BACKGROUND STUDY AND LITERATURE REVIEW
Here below is explained about the similar project by Herald Robinson. The gym
management system project is designed to facilitate a gymming and fitness center
to automate its operations of keeping records and store them in form of a large and
user friendly database further facilitating easy access to the personnel
This Manually Managed system of the store was also heavily pronged to
data loss due to certain causes Misplacement of Registers, Destruction of
Registers, Unauthorized access to registers etc. which can bring in disastrous
Consequences.
Data Redundancy is no more the problem now. The data modified from one
particular data entry form will reflect the modifications at the other related
forms too. This has thus reduced the chances of data inconsistency in our data
storage.
There is no need to manage bulky registers now as data stored in the backend
database can be readily retrieved either from the frontend form itself or directly
from the database.
CONCLUSION
The objective of this project was to build a program for maintaining the details of
all the members, employees and inventory .The system developed is able to meet
all the basic requirements. The management of the records (both members and
employees) will be also benefited by the proposed system, as it will automate the
whole procedure, which will reduce the workload. The security of the system is
also one of the prime concerns.
There is always a room for improvement in any software, however efficient the
system may be. The important thing is that the system should be flexible enough
for future modifications. The system has been factored into different modules to
make system adapt to the further changes. Every effort has been made to cover all
user requirements and make it user friendly.
Goal achieved: The System is able provide the interface to the owner so that
he can replicate his desired data. .
User friendliness: Though the most part of the system is supposed to act in
the background, efforts have been made to make the foreground interaction
with user (owner) as smooth as possible. Also the integration of the existing
system with the project has been kept in mind throughout the development
phase.
CHAPTER THREE
SYSTEM ANALYSIS
6. Create a system definition that forms the foundation for all the subsequent
engineering work.
3.1.1 REQUIREMENT ANALYSIS
Functional requirements are the specific features and capabilities that the system
must possess to perform its intended functions. They describe what the system
should do and how it should behave.
Non-functional requirements, on the other hand, describe the qualities that the
system must possess in order to be effective and efficient. They are often referred
to as the system's "quality attributes" and include characteristics such as usability,
performance, security, scalability, reliability, and maintainability.
Below are some functional and non functional requirements for our project
8. User Interface: The system should have an intuitive user interface that is
easy to use for both staff and members. It should be accessible from any
device, such as desktop computers, tablets, and smart phones.
9. Security: The system should have strong security features to protect member
and staff data. It should have password protection, data encryption, and
backup and recovery capabilities.
3.1.2 FEASIBILITY ANALYSIS
1. Technical feasibility: In this project, all the necessary cautions have been
taken care to make it technically feasible. We evaluated the availability and
suitability of the necessary technology to implement and operate the system.
It includes existing infrastructure, hardware, software, and other IT
resources needed to manage the club's operations. We also considered the
ability of technical team to develop and maintain the system, as well as any
potential technical risks or obstacles that may impact the success of the
project.
4. Schedule feasibility: Schedule feasibility analysis for the fitness health club
project involved evaluating the project timeline and determining whether it
is realistic given the project's scope and available resources. We identified
any potential scheduling conflicts, estimating the time and resources needed
to complete each phase of the project, and created a detailed project plan
with clear timelines and milestones. We also considered the availability and
capacity of the team members responsible for implementing the system, and
any potential delays or obstacles that may impact the project timeline.
3.1.3 STRUCTURED ANALYSIS
CONTEXT DIAGRAM
F
ig: Context Diagram
DATA FLOW DIAGRAM