Module Name : INFS7007 – SA&DMS

Lecturer Name :
Hand in Date : 12th Feb,2023
Project Name : Fitness Centre
Group No. :

Student ID Student Name

INFS7007 – SA&DMS Fitness Centre

Contents
1. Introduction:............................................................................................................................................4
2. Problems and proposed solutions:...........................................................................................................5
2.1 Proposed Solutions:...............................................................................................................................5
3. Project planning:......................................................................................................................................6
3.1 System Development Life Cycle (SDLC).......................................................................................6
3.1.1 Planning Phase:.............................................................................................................................6
3.1.2 Analysis Phase:.............................................................................................................................7
3.1.3 Design Phase:................................................................................................................................8
3.1.4 Implementation Phase:.................................................................................................................9
3.1.5 Maintenance Phase:......................................................................................................................9
3.2 Gantt Chart:...................................................................................................................................10
4.0 Feasibility Study:.................................................................................................................................11
4.4.1 Technical Feasibility...................................................................................................................11
4.4.2 Economical Feasibility................................................................................................................11
4.4.3 Operational Feasibility...............................................................................................................12
4.4.4 Behavioural Feasibility...............................................................................................................12
5. Requirement Definition:........................................................................................................................13
6. Design Diagram (Use Case and Process Model):..................................................................................15
6.1 ERD:...............................................................................................................................................15
6.2 GRD:...............................................................................................................................................17
6.3 Context diagram:...........................................................................................................................18
6.4 Level-0 DFD:..................................................................................................................................19
6.5 Use Case and Process Model:........................................................................................................20
7. Screen Design and Database:................................................................................................................21
Manager...........................................................................................................................................23
STAFF..............................................................................................................................................23
RECEPTIONIST.............................................................................................................................23
TRAINER.........................................................................................................................................23
MEMBERSHIPTYPE.....................................................................................................................24
CUSTOMER....................................................................................................................................24
CLASSES.........................................................................................................................................24

Page 2 of 30
INFS7007 – SA&DMS Fitness Centre

PAYMENT.......................................................................................................................................24
CLASSPLAN...................................................................................................................................25
8. Implementation:.....................................................................................................................................29
8.1. Hardware Requirement.......................................................................................................................29
8.2. Software Requirement........................................................................................................................29

Page 3 of 30
INFS7007 – SA&DMS Fitness Centre

1. Introduction:

The designed of this project is to facilitate the automate Fitness center during its operations so
that it keeps the records and would store them in form of a large database that provide facilitating
easy access to the personnel. It also offers an classes for extensive selection with experienced
trained instructors in tailoring group and individual programme.
This system helps in dealing with gyms and clubs inside the fitness industry that help them to
provide the potential to govern memberships, facilities and schedules. The systems also provide
the potential to manage financial records, reserve facilities, schedule lessons, and save the
Customer details in a database in form of tables.
Fitness Center Project is to make a fitness center easy. Software received records into database
that consist of computerized billing, admin obligations and online scheduling. It also help in
allowing to manage the business extra successfully.
System Features for Fitness Center
Fitness Center – This feature provides an information of amenities, Class schedules, Trainer,
Membership information to Customer while searching about the fitness centre.
Customer Management – Help to store the customers or the payment records, client
information, schedule classesm, sessions, manage financial, and reserve facilities that will help
them to provide the class schedules and the memberships along with the schedules and trainers.
Reports Creation – Reports will be used to get the complete information of the fitness centre
based on the activities happen during the day. As soon as data is updated in data base, user can
generate the report for multiple combinations. Reports are very useful to improve the process and
rectify the issue during process.
Transactions Management – Transaction management is the part of data managing in multiple
tables. This is the reason, project should atleast in 3 NF form of database. When Transaction
happens then some data will be inserted/updated/deleted into database. Based on the data,
multiple caluclation and logic took place in system. Project will handle multiple transaction
simultenously because Customer, Admin, Trainer and other users will use the application same
time. So It must be correct transaction stored in database. If correct transaction will be saved into
database so it will be useful to generate multipe kinds of report for different users. Project will
also provide the multiple dashboard which can be shown in Training session to identify the
weeekness and strgenth of the customers.

Page 4 of 30
INFS7007 – SA&DMS Fitness Centre

2. Problems and proposed solutions:

Currently there is not system available for handling the Fitness Centre. Manual data is
updating into ledger and files. So searching any information is not easy task and everybody has
to put more effort to get the appropriate data. More man powers required to handle the multiple
kind of process and same time if customers have any query so it will be resolved based on the
manual intervation along with delay in time. Manual followup require during the complete
process and no plan to develop the new finding to upgrade the process.

2.1 Proposed Solutions:

Registration done through online: Customers have the facility to search the multiple option
online. If everything is as per expectation then online registration facility is available. So
Customer will fill all the information by himself so in this case Staff members will not bothered
to maintain the register.

Centralized Database: SQL Server database will be installed centralized to access by the
application, reports and dashboard. Every processes are getting the data from common source so
not mismatch is there. Outsiders will not have the privileges to access the datbase in any form.
For accessing the datbase directly, admin has the privileges to give the permision to others.

Business & Finance Analysis: Once data is restored in the database. Now business has the
opportunity to analysis the data in multiple way to increase the business as well as revenue.
Online surey is also possible to recive the correct feedback.

Security: As described above that database is centralized and it is under the multiple security to
secure the database in case of disaster. Multiple backup on daily basis and differential backup
also available in case of any issue. So data will be always safe.

Financial Theft not possible: Every stakeholders or users are having the userid and password to
access the application. Every activity is logged along with the user information and time for
foture reference. So every steps are tracking in application in term of any theft.

Find & Search: User is having the facility to search the multiple kind of data in one click only.
User has to provide the multiple searhc criteria based on his/her requirement data and data will
be available in fraction of time as per expectation.
Page 5 of 30
INFS7007 – SA&DMS Fitness Centre

3. Project planning:

3.1 System Development Life Cycle (SDLC)

Project should be functioning and working properly as per expectation, there must be
some checklist to make the project success. To develop a project, there should be some standard
which can be maintain for every projects. System development life cycle (SDLC) is a very
popular method which used in maximum project to make the success. In this process, multiple
process will execute in sequence as Planning, Analysis, Design, Development, Testing,
Implementation and Maintenance as per the below snapshot.

Apply the SDLC methodologies to save the cost and time. It will increase the efficiency.

3.1.1 Planning Phase:

Planning stage is the initiation stage of SDLC which is the process to start the work, this
phase is to identify the feasibility study and map with the existing project along with
identification of the Risks. If risks are identified in beginning, then project will not be failed
in any case. Project Charter needs to prepare in the phase which have the objective and main
requirements of the projects. It also contains the project manager name along with the
stakeholders and approved by the sponsor. So, the output of this phase will be become the
Page 6 of 30
INFS7007 – SA&DMS Fitness Centre

input of the next phase. The more information and documents on the project goals, the more
outputs can be achieved such as, the management plan structure, emphasis on plan quality,
the overall project plan for the schedule and scope and finally the predictable results.

The planning phase in our proposed system is achieved by the selected team’s members to
get the details from the higher management and HR stakeholders. Now all the team members
will work on Fitness domain to understand the functionality so it will be beneficial for making
the initiation document for further phases.

3.1.2 Analysis Phase:

When Planning stage is successfully completed and approved by the sponsor and other
stakeholders then next stage will be initiated to match the requirement, this phase is also an
important part of SDLC. SO, this stage will be performed to understand the system requirement
and match with the exiting product or project, so final goal is to accomplish the goal on time. So,
document should be prepared clearly, and output of this phase is SRS (Software Requirement
Specification) which contains the all requirement and expectation from the project. It contains all
the hardware and software specification for development and deployment environment. So,
remove all uncertainty of this phase so it will become the milestone for the next phase. Multiple
methods are available to get all kind of the requirement as interviews, face to face discussion,
query sheet, , document review and observations through our stakeholders.

Page 7 of 30
INFS7007 – SA&DMS Fitness Centre

3.1.3 Design Phase:

Once the requirements are finalized in the above phase, then needs to convert the
requirement (SRS) into design documents. In this phase all kind of designs along with
documentation. So, needs to create the context diagram, multiple level of DFD, ER Diagram and
GRD diagram. It will have the complete information of the architecture on which it has to
develop. This phase is having all in technical aspect of the requirement and cover each in the
design documents. Design documents should be very clear and vast so no gap on requirement.
The best part of this phase is that data base is designing along with data dictionary and
normalization technique. So, once DB is ready then it will be the input of the next phase to
develop the screen/code based on the database structure.

Page 8 of 30
INFS7007 – SA&DMS Fitness Centre

3.1.4 Implementation Phase:

This phase is not the implementation phase but it should be development along with
testing phase. So based on the requirement, we need to design the screen and interface which will
save/extract the data from DB in the last phase. development need to complete to make the
deliverable for UAT/Implementation/ deployment. During the development, testing process is
parallel as testing and creating the multiple kind of the testing documents. This is the phase we
execute the multiple kind of test case to get rid of any error and mismatch with the requirements.
Once deliverables are ready to deploy at client location for UAT or LIVE then the task of this
phase is completed, and we have multiple documents for evidence purpose. Everything should be
baselined the TFS.

3.1.5 Maintenance Phase:

Once product/exe is deployed on the client environment then the project will come under
support or maintenance. In this phase, Client will provide the signoff after UAT done and LIVE
deployment done. The signoff meaning is that the product is fulfilling all the requirement which
are available in the SRS document. So, after Signoff, support will be provided free of cost for
some times as per the agreement between client and vendor. During this time, if any error occurs
on live environment, then developer has to fix based on the SLA, if there is any new changes

Page 9 of 30
INFS7007 – SA&DMS Fitness Centre

then it will not come under support mode. After agreed points, client will provide the AMC for
further support of the developed project.

3.2 Gantt Chart:

It contains the schedule with each activities’ s start and end date & time. It is having the
information of each head’s development completion date so it can be communicated to client for
delivery.

Page 10 of 30
INFS7007 – SA&DMS Fitness Centre

4.0 Feasibility Study:

Feasibility study is nothing but the way to work on the environment which can fulfill
the requirement of the client. If client is asking some requirement and it is not possible
to provide then should say NO to client along with the valid reason. Client will
understand and provide some refined requirement which can be developed and
delivered. So, 1st understand the complete scope of the project and work on the
feasibility report on the small requirements. Feasibility report should contains the PO
cost and time also, if the project is not developed during the time and money then we
should say it is not feasible. It should include the benefits also.
The below are some points which need to consider during the process:

1. Problem Statement:

A clear statement which provides the information of any problem. Problem statement
is very useful, but it should have some kind of evidence also.
2. Finding and Recommendations:
Always create a list of all recommendation and findings, it may be small or big. It
will provide the clear picture to each stakeholder.

4.4.1 Technical Feasibility

If discuss on technical feasibility, then always discuss on hardware and software side.
Checklist should be prepared based on the compatibility in multiple aspect and
combination of software and hardware. Even think about the support during warranty
period and after that also. License and expiry date (out of support) software should not
be used, if used then no support found in the market and will struck later on. necessary
steps have been considered to make it technically feasible.

4.4.2 Economical Feasibility

Cost is the important part of any system feasibility. Cost means not only hardware and
software, but it should consider the manpower also. The analysis of Economic should
be very frequently to identify the feasibility in term money and resources. It is called
cost/benefit analysis and it is mostly used to check the process of feasibility, Feasibility
should consider the profit also, it should not be on that theory that no profit not loss.

If developing the new product/software 1 st time then should be consider it for

reusability, if product can re-use then it will provide the more benefits to the
Page 11 of 30
INFS7007 – SA&DMS Fitness Centre

organisation so in this case 1st iteration can go in loss also because scope is there to gain
later on. The below points consider for Economic feasibility:
i. Should be full system validation and investigation.
ii. Software and hardware cost should be latest one with inclusive of all taxes.
iii. Make the common practice which can be used to reduce the cost on every
steps.
iv. Adhere the project scope 100%, if any new changes are there then re-calculating
the cost.

The below point will be proposed point to make system economically feasible.
i. Time factor should be less. The system requires very less time factors.
ii. System performance should be at par, if one invest to make the system fast in
term of performance then investment should be executed. This will save
the cost of time and man powers.
iii. Interface should be user friendly so less effort required for demo, training
and actual working.
iv. Multiple parameters should be captured for making the reports and other
story for decision making which can be used in future.
4.4.3 Operational Feasibility

GUI and interface should be designed for less effort or less click on the screen. It will
save the time of actual work hours. This kind of application is easy to operate along
with it is called user friendly screen/product. Main menu and other feasible GUI which
can provide the complete information of the software and user can easily move to
another module from one module.

4.4.4 Behavioural Feasibility

In the normal life, it is expected that behavioural should be as per expectation. It means
if any estimation is happening then it should be on the actual cost (no false addition of
any task or spend), If any estimate done by any vendor and client is having some gap of
estimation then client will ask the question, if vendor is not able to provide the
satisfactory answer then both parties will loose the trust to each other. So, any type of
the relation between one party to other party should have the behavioural feasibility.
Demo and support should provide as per the agreement before project gets started.

Page 12 of 30
INFS7007 – SA&DMS Fitness Centre

5. Requirement Definition:

5.1 Functional Requirements:

Functional requirements mean the expectation of client. It is a process to understand the
business logic of fitness Centre and each process in Gym industry. So it can be defined like that
what is the input of the process, processing and output of the process. The output of the 1st
process will become the input of next process. Functional requirements will be useful to
understand the estimation of project in terms of Money and time. Functional requirement is also
useful to provide the support to developer during the development.

Functional requirements for Fitness Centre:

- Registration of new customer should be as per expectation.

- Details of the class schedule and information along with addition of new classed.

- Payment processing and invoice availability along with the pending amount on each customer.

- Class schedule and information should be visible to customer, staff, and Trainer as per
authentication and authorization.

- Should capture the attendance of each person who belongs to the Fitness Centre.

- Customer should have the access to track the class along with the registration for any class.

- Admin should have the permission to add the trainer in any class as per customer’s
requirement.

- System should provide the option to capture the feedback from customer.

- System should provide the option to generate the multiple reports along with dashboard.

5.2 Non-Functional Requirements:

Non-functional requirements specify criteria that can be used to judge the operation of a
system, rather than specific behaviors. Non-functional requirements specify define how a system
is supposed to be. These are the features that don’t do anything but are important characteristics
of the system. For example, design, user interface, user experience, compatibility, etc.

Page 13 of 30
INFS7007 – SA&DMS Fitness Centre

Non-Functional requirements for our system:

- Downtime should me minimum and up time should be minimum 99.9%

- Should support multiple payment method to provide the ease to Customers

- All data and payment must be secured.

- System should be optimized in that way when data is more than it should give the same
performance which it was giving in initial stage.

- It should be capable to handle the load.

- Multiple validations should be applicable to remove the redundancy of data and transaction.

- User friendly interface along with good looking which can be very interest full.

- Should support for multiple notification to Customers.

Page 14 of 30
INFS7007 – SA&DMS Fitness Centre

6. Design Diagram (Use Case and Process Model):

6.1 ERD:

Fitness Center system project ER diagram example

Below is the Fitness Center’s ERD which shows the relationships of entity along with their
functionalities.

Page 15 of 30
INFS7007 – SA&DMS Fitness Centre

Weak Entity
It is having a attribute key which is unique in a entity set, Along with it, some kind of entity or entity type
which is not associated with Key attibute.
Generalization
Extract the properties from a entities set which is fixed, these properties should be common. To keep
these properties as a generalized way called Generalization. It is not mandatory that properties should be
exact match. It should mathed as higher level and funny thing is that it is called botton up approach.
Specialization
Based on their characteristics , an entity is divied into sub entitites called Higher and Lower level. When
higher level entity is bifirguated into two or more lower level entites is called Specialization which is a
top down approach.

Page 16 of 30
INFS7007 – SA&DMS Fitness Centre

6.2 GRD:

membershiptype *
[membership_id (PK)]
membership_name
membership_period
membership_amount
FK_MEMBERSHIPTYPE_STAFF_ID signup_fee
[staff_id (FK)]

FK_CLASSESPLAN_CLASS_ID

FK_CUSTOMERS_MEMBERSHIP_ID
classesplan * classes *
[plan_id (PK)] [class_id (PK)]
[customer_id (FK)] class_name
[class_id (FK)] amount
customers * FK_CLASSESPLAN_CUSTOMER_ID work_out_time
description
[customer_id (PK)]
work_out_date
customer_name
[trainer_id (FK)]
address
contact
email
age FK_CLASSESPLAN_TRAINER_ID

gender
joining_date
end_of_membership_date trainer *
FK_CUSTOMERS_STAFF_ID [membership_id (FK)] [Trainer_id (PK)]
staff * [staff_id (FK)] trainer_name
[staff_id (PK)] contact FK_PAYMENT_CLASS_ID
staff_name address
contact email
FK_TRAINER_STAFF_ID
address [staff_id (FK)]
username
FK_PAYMENT_CUSTOMER_ID
password
[manager_id (FK)]

FK_RECEPTIONIST_STAFF_ID
FK_STAFF_MANAGER_ID FK_PAYMENT_RECEPTIONIST_ID
payment *
receptionist * [payment_id (PK)]
[receptionist_id (PK)] [customer_id (FK)]
receptionist_name
manager * amount
[manager_id (PK)] contact payment_time
manager_name address payment_date
contact email [receptionist_id (FK)]
address [staff_id (FK)] [class_id (FK)]
username
password

Page 17 of 30
INFS7007 – SA&DMS Fitness Centre

6.3 Context diagram:

Page 18 of 30
INFS7007 – SA&DMS Fitness Centre

6.4 Level-0 DFD:

Page 19 of 30
INFS7007 – SA&DMS Fitness Centre

6.5 Use Case and Process Model:

In the above DFD, there are 3 main roles available as

a. Customer
b. Trainer
c. Receptionist
Every role is having the different responsibility and access of the system, based on the role, modules will
be provided for using the functionalities. Every project/product has admin module which controls the
roles of each user based on the requirement. If go through with each role’s responsibilities, then go with
in details.
a. Customer – Customer will sign-up for 1st time and second time onwards, he/she will put the user
id and password to login in the system. Customer can ask multiple process to the system as
Request for the availability of class, price of the class, instructor details, etc. Based on the
request, information is to share with the customer for further processing. The customer will
decide on the class and package for the payment. Once payment is successful then he will be able
to find out the complete details of the package for which he paid. So, in conclusion, he is having
the option to access Requests, Reservation, Payment, etc.
b. Trainer – He is having the same process to access the project with a User ID and Password. He
will be able to create and schedule the new class. He is having the authority to add the
new/existing customer in any class. He is having the complete information about the customer
and his payment. Once payment is done then he will be able to add the Customer to the agreed
class.
c. Receptionist – He is having all the information about the Class, instructor, package, and invoice.
If any customer demands any service, then Receptionist will get the information and he has to
respond ASAP. He is playing the main game between the customer and other stakeholders of the
center.

Page 20 of 30
INFS7007 – SA&DMS Fitness Centre

7. Screen Design and Database:

SAD

The main menu of the proposed system has been shown in below figure. It is classified to get access from
employees (instructors) and members and each one has different sub divided menus and different
permissions.

Members LOGIN:

All the members will get an password and username from the club management after they register in the
club sucessfully and it will allows them to get full access to the system.

Page 21 of 30
INFS7007 – SA&DMS Fitness Centre

Once the member of the club management get the access for the system than different activities can be
done that provide as easy ways in the business process in the one health club.

Page 22 of 30
INFS7007 – SA&DMS Fitness Centre

Below tables will be created to keep the data for Fitness Center.

Manager

STAFF

RECEPTIONIST

TRAINER

Page 23 of 30
INFS7007 – SA&DMS Fitness Centre

MEMBERSHIPTYPE

CUSTOMER

CLASSES

PAYMENT

Page 24 of 30
INFS7007 – SA&DMS Fitness Centre

CLASSPLAN

The below are the executable queries along with the snap shots:

Question a. How many Fitness Program (Classes) does this centre offer? What are their
names and prices?

Page 25 of 30
INFS7007 – SA&DMS Fitness Centre

Question b. List all Classes, their weekly time and day?

Question c. How many Customers have signed in for a particular Fitness Program?

Question d. Who is the Trainer of a particular Fitness program?

Page 26 of 30
INFS7007 – SA&DMS Fitness Centre

Question e. What is the average age of the Customers who signed into Zumba classes?

Question f. List the name of Customers and their corresponding chosen Classes.

Question g. List all Classes delivered on Monday.

Page 27 of 30
INFS7007 – SA&DMS Fitness Centre

Question h. List the name of all Customers who go to Pilates classes on Wednesday.

Question i. List the name of all Customers and their Trainers for each Class they signed in.

Question j. List the name of Trainers who work on Monday.

Page 28 of 30
INFS7007 – SA&DMS Fitness Centre

8. Implementation:

Once UAT is successfully finished and Client is ready for the implementation then
Implementation team must install the software as per project requirement on the client machine.
Need to install the .NET framework and SQL Server on client machine to implement the
developed project.

8.1. Hardware Requirement

Hardware configuration for executing the project. Every project is having some minimum
requirement to run the application on the machine/pc. So based on the Architecture, hardware
should be selected as per the future requirement as data is increasing everyday o performance
should be decreased. So, Hardware selection is very important to implement the Project.
Client-Side Hardware Requirement:

Intel Core 5 Processor

RAM: 4 GB
HDD: 512 GB
Monitor as per requirement.
Keyboards
Printer

8.2. Software Requirement

Software Requirement is defined here to install on Client machine as per the project requirement.
Operating System : Windows 10
Database (Back End) : Microsoft SQL Server 2018
Front-end : Visual Studio NET, C#, HTML, CSS, jQuery

Page 29 of 30
INFS7007 – SA&DMS Fitness Centre

IMPLEMENTATION

After the UAT testing done, implementation phase is initiated. This phase is very crucial in the
SDLC. So now developed system will be implemented into operations. So, it is now coming out
from Testing and now actual users are going to use. During implementation, if any issue occurs
then it needs to resolve on the priority with SLA. During the implementation, User manual and
training to the actual users are mandatory.
After implementation, needs to keep the eye on the data, whether data is inserted/updated correct
or there are any discrepancies in data. If found any issue the needs to correct data. But before that
we must insert all master data with pre-requisite of the project.
User should know the very process of changing the master data as well as. We can divide
Implementation in multiple phases as below,
1. Fresh Implementation – Client did not use any system till now and getting the new
system to get rid of Manual system.
2. Project replacement Implementation – Client is using the same system from other vendor
and getting the new system in place of the previous system.
3. New Release of same Project Implementation – Client is using the same system with
same vendor and getting the newly updated exe based on his/her new requirement for
business related. In this case needs to copy only the deliverables.

Page 30 of 30