Fitnes Center

F
F
i
i
t
t
n
n
e
e
s
s
s
s
C
C
e
e
n
n
t
t
e
e
r
r
S
S
y
y
s
s
t
t
e
e
m
m

By

Saw Shu Lin

SCHOOL OF ARTS AND SCIENCE
TUNKU ABDUL RAHMAN COLLEGE
KUALA LUMPUR

ACADEMIC YEAR
2010/2011

Fitness Center System

Project
ii
F Fi i t t n ne es ss s C Ce en nt t e er r S Sy ys st t e em m

By

Saw Shu Lin

Supervisor: Mr Ku Cheng Fui

A project report submitted to the School of Arts and Science
in partial fulfillment of the requirement for the
Bachelor of Science, Campbell University, U.S.A,
And
Advanced Diploma in Science.

Division of Computer Science
School of Arts and Science
Tunku Abdul Rahman College
Kuala Lumpur

2010/2011

Copyright 2008 by Tunku Abdul Rahman College.
All rights served. No part of this project documentation may be reproduced,
stored in retrieval system, or transmitted in any form or by any means without
prior permission of Tunku Abdul Rahman College.

Fitness Center System Declaration

Project
iii
D De ec cl l a ar ra at t i i o on n
The project submitted herewith is a result of my own efforts in totality and in every
aspect of the project works. All information that has been obtained from other
sources had been fully acknowledged. I understand that any plagiarism, cheating or
collusion or any sorts constitutes a breach of College rules and regulations and would
be subjected to disciplinary actions.

__________________________
Students Name: Saw Shu Lin
Course: AIB

Fitness Center System Abstract

Project
iv
A Ab bs st t r ra ac ct t
There are several mandatory components of an abstract as follows:

Purpose:
The main purpose to develop this project is in partial fulfilment of the requirement for
Bachelor of Science. Besides that, is to help the Fitness Center to reduce their
overload paperwork.

Scope:
Fitness Center System consists of 8 Main modules and 3 sub modules. The Main
module which are Customer Module, Member Module, Booking Module, Payment
Module, Reward Point Module, Report Module, Staff Module and Login Module. For
the Gift Module, Payment Item Module and Activity Module are sub modules in the
system.

Methodology:
We were using the Object Oriented Approach to design our system. We was draw out
some the diagram such as class diagram, collaboration diagram, activity diagram and
sequence diagram in order to help us have the better idea when develop the system.
The tools we are using to develop our system are Microsoft Visual Studio 2008 and
Microsoft SQL Server 2005.

Assessment criteria used:
During the system development, Mr Ku had give us some suggestion in the designing
the system. The day before final testing, we have undergone the partial testing to test
whether any dissatisfy area need us to make changes or improvement.

Fitness Center System Abstract

Project
v
Development phases:
First of all, we come out a proposal with the propose system that we want to develop.
Then we find the supervisor that who accepts our proposal and guide us for the final
year project. After that, we come out the project specification. Which include the
company background, business rules, organization structure, project objective, project
scopes and project schedules. After we done all the documentation, then we start to
design the UML diagram such as class diagram, collaboration diagram, activity
diagram and sequence diagram. Next we start to design our database. Based on the
class diagram that we draw, we come out the database with few records. The last
phase is coding and testing.

Results:
The project overall is consider fulfil the requirement and can deliver the system on
time. The strength of the system is the interface is standardise, minimizes the user
input and validation checking for the user input. For the weaknesses of the system is
the interface is bored interface.

Conclusions and Recommendations:
Through the project, we have learned that time management is important. If do not
have the good time management, it will affect the quality of the project. Besides that,
teamwork and communication also consider as important. Two person works is better
than one person work.

Fitness Center System Acknowledgement

Project
vi
A Ac ck kn no ow wl l e ed dg ge em me en nt t
I wish to express my sincere gratitude to project supervisor, Mr. Ku Cheng Fui, for his
guidance, constant support and encouragement throughout the completion of this final
year project. I would also like to convey my heartfelt appreciation to Mr. Ku Cheng
Fui for contributing his ideas and in-depth knowledge in the field.

A warm thank is extended to my team mate Ong Li Lean for sharing their resources,
opinions, knowledge, experience and skills in programming and development
methodology, so generously. I would also like to personally thank my family, friends
in TAR College and my fellow course-mates who have one way or another extended
their assistance in completing this project.

Last, but not least, I wishes to acknowledge the unwavering support shown by all
lectures who teach me before.

Fitness Center System Table of Contents

Project
vii
T Ta ab bl l e e o of f C Co on nt t e en nt t s s
Fitness Center System .............................................................................................................. ii
Declaration.............................................................................................................................. iii
Abstract .................................................................................................................................... iv
Acknowledgement ................................................................................................................... vi
1. System Planning ................................................................................................................ 2
1.1 Project Aims and Objectives ................................................................................................. 3
1.2 Company Background .......................................................................................................... 4
1.3 Project Scope ........................................................................................................................ 6
1.3.1 Module Handle ......................................................................................................................... 7
1.4 Project Schedule ................................................................................................................... 8
1.5 Outline of approach/Methodology Used ............................................................................... 9
2. Requirements Analysis ................................................................................................... 11
2.1 Fact Gathering..................................................................................................................... 12
2.2 Fact Recording .................................................................................................................... 12
2.2.1 Functional Requirement ......................................................................................................... 12
2.2.2 Non-Functional Requirement ................................................................................................. 15
2.3 Overview Use Case Diagram .............................................................................................. 17
2.4 Detailed Use Case Diagram ................................................................................................ 18
2.5 Use Case Description .......................................................................................................... 24
2.6 Class Diagram ..................................................................................................................... 41
3. System Design .................................................................................................................. 43
3.1 ERD Diagram ..................................................................................................................... 44
3.2 Activity Diagram ................................................................................................................ 45
3.3 Sequence Diagram .............................................................................................................. 65
3.4 Data Dictionary ................................................................................................................... 77
3.5 System Design .................................................................................................................... 84
4. Programming ................................................................................................................... 94
4.1 Programming Tool .............................................................................................................. 95
4.2 Programming Approach ...................................................................................................... 95
5. Software Testing .............................................................................................................. 98
5.1 Type of Testing ................................................................................................................... 99
5.2 Test Plan ........................................................................................................................... 100
6. Conclusion ...................................................................................................................... 106
6.1 Linkage to seminar ............................................................................................................ 107
6.2 Evaluation of project strengths and weaknesses ............................................................... 107
6.3 Suggestion for the future improvement ............................................................................ 108
6.4 Conclusion ........................................................................................................................ 109
7. References ...................................................................................................................... 110
Fitness Center System Table of Contents

Project
viii
8. Appendices ..................................................................................................................... 111
8.1 Business Rule .................................................................................................................... 112
8.2 Development Environment ............................................................................................... 113
8.3 Operation Environment ..................................................................................................... 113
9. User Guide ..................................................................................................................... 114

Fitness Center System Chapter 1 : System Planning

Project 1

Chapter 1

System Planning


Project 2
1 1. . S Sy ys st t e em m P Pl l a an nn ni i n ng g
This chapter is to provide the planning for the system that is going to develop. In the
system planning, it consists of project objectives, company background, project scope,
project schedule and outline of approach or methodology used.


Project 3
1.1 Project Aims and Objectives
Below are the objectives that we want to achieve when developing the Fitness Center
System:
To help the organization to reduce the overload paperwork
To reduce the storage space problem of keeping the member records.
To update record quick and easily because all the system are computerized
Minimize the human mistake and error because do not need the manual record
Speed out the checkout and check in process for member
Reduce the administrative costs because we no need to hire more staffs.
Can maintain the member history easily.
Can save the printing and distributing paper based manuals because all the document
can easily maintained.


Project 4
1.2 Company Background

1.2.1 Nature of business
Celebrity Fitness is a fitness equipment and leisure chain store that especially support
to the development of healthy lifestyle of every Malaysian. Our business is no longer
just about helping people lose weight. Its about changing peoples lives. As the
fastest growing fitness chain club, we will continue to deliver on our promise of
guaranteed value and our aim to help every Malaysian to achieve them fitness goals.
We have experienced and professional Personal Trainers to help and motivate them to
lose weight and changing peoples lives style.

1.2.2 Product and service
We carry the widest range of health and fitness equipment. Bright fluorescent lights
combined with pumping music and club ambience, makes Celebrity Fitness the most
unique fitness center. Offering the best quality service and equipment, Celebrity
Fitness also provides the most complete selection of aerobic, yoga, indoor cycling
class, and dance classes. Members will also enjoy the added amenities of a healthy
Caf & Lounge, Sauna and Steam Rooms, Pilates facilities, and trainers and
instructors.

1.2.3 Current system uses
The current system that the Celebrity Fitness uses is mostly manual system. But for
the member part, they use computer to keep track the member record. They staff was
feeling stress by the constantly growing workload. Furthermore, the manual system
waste a lot of paperwork cost and it also waste the storage space problem because
they need to have a space to store all the record.


Project 5
1.2.5 Organization structure

Chief Executive Operator
Mr Choi Kwang Ho
Director of Operation
Ms Lillian Bong
Administration
Department
Yoga
Trainer
Lilica Vargas
Indoor
Cycling
Kenny Lim
Aerobic
Chin Lai
Dance
Leonardo Luis
Staff
Ezura
Staff
Khor Wai Yee
Staff
Renee Lim

Project 6
1.3 Project Scope


Project 7
1.3.1 Module Handle
We are developing Fitness Center System in window based system. Below are the module
handle by us:
Module Handle Person In Charge
Staff Login Module Saw Shu Lin
Customer Maintenance Module Saw Shu Lin
Staff Maintenance Module Saw Shu Lin
Booking Maintenance Module Saw Shu Lin
Activity Maintenance Module Saw Shu Lin
Customer Attendance Module Saw Shu Lin
Member Login Saw Shu Lin
3 Report Saw Shu Lin
Gift Maintenance Module Ong Li Lean
Payment Item Maintenance Module Ong Li Lean
Member Maintenance Module Ong Li Lean
Reward Point Maintenance Module Ong Li Lean
Payment Maintenance Module Ong Li Lean
3 Report Ong Li Lean


Project 8
1.4 Project Schedule

Project Start Date End Date Complete
Proposal & Project Plan

1 Mar 2010 20 Mar 2010 5%
Analysis

21 Mar 2010 30 Mar 2010 10%
Interface Design

31 Mar 2010 30 Apr 2010 20%
Database Design

1 May 2010 3 J un 2010 30%
Coding

4 J un 2010 4 J an 2011 80%
Testing

5 J an 2011 24 Feb 2011 85%
Summit Draft Report

25 Feb 2011 07 Mar 2011 95%
Summit Final Report

08 Feb 2011 16 Mar 2011 100%


Project 9
1.5 Outline of approach/Methodology Used
Fitness Center System is developing by using the Microsoft Studio 2008 and
Microsoft Server 2005. For the approach used in this system are Object Oriented
Approach and Unified Modeling Language (UML) for the data modeling. Object
oriented programming (OOP) applications are easier to maintain, have more reusable
components, and are more scalable.
Object Modelling is based on identifying the objects in a system and their
interrelationships. Once this is done, the coding of the system is done. Object
Modelling is somewhat similar to the traditional approach of system designing, in that
it also follows a sequential process of system designing but with a different approach.
The basic steps of system designing using Object Modelling are system analysis,
system design, object design and implementation.
The computer language that I use to develop Fitness Center System is VB.NET.
Object Oriented Analysis and design (OOAD) acquire the UML diagram in order to
have the better understanding on the system requirement, and design. I use Visual
Paradigm to help me to draw out the diagrams. For example, sequence diagram,
activity diagram and use case diagram. For the class diagram, I use the Microsoft
Visio. OOAD method is good for the system requirement and design.

Chapter 2

Requirements Analysis

Fitness Center System Chapter 2 : Requirement Analysis

Project 11
2 2. . R Re eq qu ui i r r e em me en nt ts s A An na al l y ys si i s s
This chapter will gather the information and provide the analysis of the system that
going to develop. Requirements Analysis is the process of understanding the user
needs and expectations from a proposed system.


Project 12
2.1 Fact Gathering
After go through the system planning, the next step that we going to do is the gather
the information and get close to user in order to understand their daily operation and
how they work. Hence my teammate and I have consult the staff who work in the
fitness center in order can gather more information and easy for us to develop the
system.
2.2 Fact Recording
After I go through the fact gathering, the next step we going to do is fact recording.
Below are the requirements for the user needs.
2.2.1 Functional Requirement
i) Login Module
Login Module consists of several functions such as login and change password.
- After login in the system, the system will pop up relevant data to user based on
their user name and password.
- The login module also allows the user to change to password for the security
purpose.

ii) Customer Maintenance Module
The customer maintenance module will keeps track all the customer details.
- Staff can View the customer details by using the search criteria that are provided
which are customer ID, customer name or customer IC No in the customer detail
form.
- Staff also can choose to View All the customer details.
- The Add function is to add the customer detail during their registration.
- The Edit function is to edit the customer record when any typing error or changes
have been made in the customer information.
- The Delete function is to delete the particular customer detail.


Project 13
iii) Customer Attendance Module
The customer Attendance module will keeps track all the customer attendance
details.
- Staff can View the customer attendancedetails by using the search criteria that are
provided which are customer ID in the customer attendancedetail form.
- Staff also can choose to View All the customer attendancedetails.
- The Add function is to add the customer attendancedetail when they start join the
activity.

iv) Staff Maintenance Module
The staff maintenance module will keeps track all the staff details.
- Manager can View the staff detail by using the search criteria that are provided
which are staff ID, staff name or staff IC No in the staff detail form.
- Manager also can choose to View All the staff details.
- The manager will add staff detail when the person as staff of the company.
- The Edit function is to edit the staff information.
- The Delete function is to cancel staff information when the staff resign or retired.

v) Booking Maintenance Module
The booking maintenance module is to help the member to book the time and
activity that they want to join the class.
- Staff can View the booking detail by using the search criteria that are provided
which are booking ID or member ID in the booking detail form.
- Staff also can choose to View All the booking details.
- In the booking form the staff can view the activity whether the activity is still
available.
- Staff can Add the booking detail when the activity is available.
- The Delete function is to delete the booking record.
- In the booking detail form, staff can export the daily booking detail to the
Microsoft Excel in order to let them to take the attendance.

vi) Activity Maintenance Module
The activity maintenance module is allowing the admin people to keep track all the
activity detail.

Project 14
- Activity can View the activity details by using the search criteria that are provided
which are activity ID or activity name in the activity detail form.
- Activity also can choose to View All the activity details.
- The Add function is to add the activity details.
- The Edit function is to edit the activity record when any typing error or changes
have been made in the activity information.
- The Delete function is to delete the particular activity detail.

vii) Report Module
The report module is allowing the manager to view the monthly report.
- Manager need to select the month that he or she wants to view in staff report or
booking report. For member report, manager needs to select the month and
member type when he or she wants to view the report.

viii) Member Login Module
The member login module is allowing the member keeps track all the member
attendancedetails.
- After login in the system, the system will pop up relevant data to member based
on their IC No.


Project 15
2.2.2 Non-Functional Requirement
i) Cost and time saving
Staff can enjoy savings in term of times and costs with regard to save the
administrative cost because the entire document can easily maintain and the
organization not need to hire more people to keep track the data and filing the all data
manually. All the data will keep into the system database. For the time, the staff can
save the time to find out the history data. This is because the system can help staff to
find out the old data more easily and quickly. Besides that it can reduce the storage
space problem of keeping the member records.

ii) Reduced redundancy
Data used across several different purposes can lead to repetition of information and
leading to inconsistency and duplicated data. After develop the system, each data is
only be stored once. And it can minimize the human mistake and error because do not
need the manual record. So it will reduce the data redundancy.

iii) Up-to-date data
After develop this system, it can update record quick and easily because all the system
are computerized. The staffs no need to find out the data manually and correct it with
pen. Staff can directly go to the search button in the system to find out the particular
data and correct it quick.

iv) Security
In this system, all the data can only be accessible to those authorized to see it. Only
the authorized people have the capability to make changes on the data under
controlled conditions. For example, only the manager has the authorized to make
changes of the staff information. And the staff cannot have the authorized to view or
make changes on other staff information.

v) Improve customer service
The system saves times and help organization to provide the best way to serve the
customer. Through the system, it can speed out the checkout and check in process for

Project 16
member. Member can save their time to check in and checkout when they enter to
fitness club or leaving fitness club.


Project 17
2.3 Overview Use Case Diagram
Overview Use Case Diagram show what the system functions are performed.


Project 18
2.4 Detailed Use Case Diagram
The detail use case diagram show the detail of the each use case in the overview use
case diagram.

i) Maintain Customer Details


Project 19
ii) Maintain Customer Attendance

iii) Staff Login


Project 20
iv) Maintain Staff Detail


Project 21
v) Maintain Booking Detail


Project 22
vi) Maintain Activity Detail

vii) Report


Project 23
viii) Member Login


Project 24
2.5 Use Case Description
i. Use Case Name: Maintains Customer Detail
Brief Description: This use case describes how we add a customer as well as
changing, deleting or viewing a customer details.
Primary Actor: Staff, manager
Pre-Condition: Add Customer, View Customer, Delete Customer and Edit Customer
Main Flows:
Actor Action System Response
1. Display Main Menu
2. Select the Maintains Customer Details
3. Display the Sub Menu: Add
Customer Detail, Edit Customer
Detail, View Customer Detail and
Delete Customer Detail
4. Select Sub Menu to perform.

- If the staff selects Add Customer Details, the S1: Add New Customer subflow is
performed.
- If the staff selects Edit Customer Details, the S2: Edit Customer subflow is
performed.
- If the staff selects View Customer Details, the S3: View Customer subflow is
performed.
- If the staff selects Delete Customer Details, the S4: Delete Customer subflow is
performed.

Sub Flows:
S1: Add New Customer
1. Display Add New Customer
Form for staff enters the customer

Project 25
details.
2. Staff enters the details of customer.
3. System will verify the data that the
staff enters.
4. System will ask for confirmation
from the staff.
5. Staff will click on confirmation to add the
new customer record.

6. System updates the database.

S2: Edit Customer Details
1. Display Customer Form with
particular customer detail
2. Staff will edit some field.
staff enters.
from the staff.
5. Staff will click on confirmation for edit
the customer record.


S3: View Customer Details
1. Display View Customer Form to
staff for viewing particular customer
details or all the customer details.

Project 26
2. Staff enters the customer ID, IC No, or
Name or select view all.

3. System will verify the ID, IC No or
Name that the staff enters.
4. System displays the customer
details.

S4: Delete Customer Details
1. Display Customer Form with a
particular customer detail
2. Staff click Delete button in the
Customer Detail form.

3. System will ask for confirmation from the
staff.
4. Staff will click on confirmation for
delete the customer details.


Alternate Flows:
- A1 step S1-3: If one of the data entered by staff is invalid data, system will display
invalid data message.
- A4 step S3-3: If the Customer ID IC No, or Customer Name incorrect, prompt out the
message box for incorrect Customer ID, IC No or Customer Name.
- A4 step S3-4: If the Staff Click On Add as Member, then the system will get all the
customer information to member form.


Project 27
ii. Use Case Name: Maintains Customer Attendance Detail
Brief Description: This use case describes how we add a customer attendance as well
as view a customer attendance details.
Primary Actor: Staff, manager
Pre-Condition: Add Customer Attendance and View Customer Attendance
Main Flows:
2. Select the Maintains Customer Details
3. Display Maintains Customer Main
Menu
4. Select the Maintains Customer
Attendance Details

Customer Attendance Detail,
View Customer Attendance
Detail

- If the staff selects Add Customer Attendance Details, the S1: Add New Customer
Attendancesubflow is performed.
- If the staff selects View Customer Attendance Details, the S2: View Customer
Attendancesubflow is performed.
Sub Flows:
S1: Add New Attendance Customer
1. Display Add New Customer
Attendance Form for staff enters the
customer details.
2. Staff enters the details of customer.

Project 28
staff enters.
from the staff.
5. Staff will click on confirmation to add the
new customer attendance record.


S2: View Customer Attendance Details
1. Display View Customer
Attendance Form for staff to view
particular customer details or all the
customer details.
2. Staff enters the customer ID or select
view all.

3. System will verify the ID that the
staff enters.
4. System displays the customer
attendance details.

Alternate Flows:
- A2 step S2-3: If the Customer ID incorrect, prompt out the message box for incorrect
Customer ID.


Project 29
iii. Use Case Name: Login
Brief Description: User need to login to the system in order to perform the functions.
Primary Actor: Staff, Manager, Administrator
Main Flows:
1. Display Login Screen.
2. Enter Username and Password.
3. Verify the username and password.
4. Display Main Menu.

Alternate Flows:
- A1 step S3: If the Username and Password that entered by user are not match with
the database, system will display invalid username and password message and
require the user to key in again.
iv. Use Case Name: Change Password
Brief Description: This use case is to allow the staff, administrator and the manager
to change the password.
Primary Actor: Staff, Manager, Administrator
Main Flows:
1. Display Login Screen.
2. Click the Change Password Form.
3. Display Change Password Form.
4. Enter Username and existing Password.
5. Enter new Password.
6. Verify the username and existing
Password and new Password.

Project 30
from user.
8. User will click on confirmation on change
Password.


Alternate Flows:
- A1 step S6: If the Username and Password that entered by user are not match with the
database, system will display invalid username and password message and require the
user to key in again.
- A1 step S6(a): If the Username and Password that entered by user are match with the
database, but the new password is invalid, ask user re-enter the new password.

v. Use Case Name: Maintains Staff Detail
Brief Description: This use case describes how we adding a staff as well as
changing, deleting or viewing a staff details.
Primary Actor: Manager
Pre-Condition: Add Staff, View Staff, Delete Staff and Edit Staff Detail
Main Flows:
2. Select the Maintains Staff Details
3. Display the Sub Menu: Add Staff
Detail, Edit Staff Detail, View Staff
Detail and Delete Staff Detail

- If the staff selects Add Staff Details, the S1: Add New Staff subflow is performed.
- If the staff selects Edit Staff Details, the S2: Edit Staff subflow is performed.
- If the staff selects View Staff Details, the S3: View Staff subflow is performed.
- If the staff selects Delete Staff Details, the S4: Delete Staff subflow is performed.

Project 31
Sub Flows:
S1: Add New Staff
1. Display Add New Staff Form for
manager enters the staff details.
2. Manager enters the details of staff.
manager enters.
4. System will ask for confirmation from
the manager.
5. Manager will click on confirmation
to add the new staff record.


S2: Edit Staff Details
1. Display Staff Form with the particular
staff detail
2. Manager will edit some field.
manager enters.
the manager.
for edit the staff record.



Project 32
S3: View Staff Details
1. Display View Staff Form with
particular staff details or all the staff
details.
2. Manager enters the staff ID, IC No,

3. System will verify the ID, IC No or
Name that the manager enters.
4. System displays the staff details.

S4: Delete Staff Details
1. Display Staff Form with a particular
staff detail
2. Manager click Delete button in the
Staff Detail form.

manager.
for delete the staff details.


Alternate Flows:
- A1 step S1-3: If one of the data entered by manager is invalid data, system will
display invalid data message.
- A3 step S2-5: If one of the data entered by manager is invalid data, system will
- A4 step S3-3: If the Staff ID, IC No, or Staff Name incorrect, prompt out the message
box for incorrect Staff ID or Staff Name.

Project 33
vi. Use Case Name: Maintains Booking Detail
Brief Description: This use case describes how we adding a booking as well as
viewing or cancelling a booking.
Primary Actor: Staff
Pre-Condition: Add Booking, View Booking and Cancel Booking
Main Flows:
1. Display Main Menu.
2. Select the Maintains Booking Details.
3. Display the Sub Menu: Add Booking
Detail, View Booking Detail and Cancel
Booking.

- If the staff selects Add Booking Details, the S1: Add New Booking subflow is
performed.
- If the staff selects View Booking Details, the S2: View Booking subflow is performed.
- If the staff selects View Booking Details, the S3: Cancel Booking subflow is
performed.
Sub Flows:
S1: Add New Booking
1. Display Add New Booking Form for
staff enters the booking details.
2. Staff enters the details of booking.
3. System will verify the data that the staff
enters.
staff.

Project 34
5. Staff will click on confirmation to
add the new booking record.


S2: View Booking Details
1. Display View Booking Form for staff
to view particular booking details or all the
booking details.
2. Staff enters the booking ID, member
ID, booking Date or select view all.

3. System will verify the booking ID,
member ID or Booking Date that the staff
enters.
4. System displays the booking details.

S3: Cancel Booking Details
1. Display Booking Form with the
particular booking details
2. Staff clicks the Delete button in the
Booking Details.

staff.
4. Staff will click on confirmation for
delete the booking details.



Project 35
Alternate Flows:
- A2 step S2-3: If the Booking ID, member ID, booking Date incorrect, prompt out the
message box for incorrect Booking ID.

vii. Use Case Name: Maintains Activity Detail
Brief Description: This use case describes how we adding an Activity as well as
changing, deleting or viewing a Activity details.
Primary Actor: Administrator
Pre-Condition: Add Activity, View Activity, Delete Activity and Edit Activity
Detail
Main Flows:
2. Select the Maintains Activity Details
Activity Detail, Edit Activity Detail,
View Activity Detail and Delete
Activity Detail

- If the administrator selects Add Activity Details, the S1: Add New Activity subflow is
performed.
- If the administrator selects Edit Activity Details, the S2: Edit Activity subflow is
performed.
- If the administrator selects View Activity Details, the S3: View Activity subflow is
performed.
- If the administrator selects Delete Activity Details, the S4: Delete Activity subflow is
performed.


Project 36
Sub Flows:
S1: Add New Activity
1. Display Add New Activity Form for
administrator enters the Activity details.
2. Administrator enters the details of
Activity.

administrator enters.
the administrator.
5. Administrator will click on
confirmation to add the new Activity
record.


S2: Edit Activity Details
1. Display Activity Form with the
particular Activity detail
2. Administrator will edit some field.
administrator enters.
the administrator.
confirmation for edit the Activity
record.


Project 37
S3: View Activity Details
1. Display View Activity Form with
particular Activity details or all the
Activity details.
2. Administrator enters the Activity ID,

3. System will verify the ID or Name that
the administrator enters.
4. System displays the Activity details.

S4: Delete Activity Details
1. Display Activity Form with a particular
Activity detail
2. Administrator click Delete button in
the Activity Detail form.

administrator.
confirmation for delete the Activity
details.


Alternate Flows:
- A1 step S1-3: If one of the data entered by administrator is invalid data, system will
- A3 step S2-5: If one of the data entered by administrator is invalid data, system will

Project 38
- A4 step S3-3: If the Activity ID or Activity Name incorrect, prompt out the message
box for incorrect Activity ID or Activity Name.

viii.aUse Case Name: Generate Report
Brief Description: This use case describes how we view the monthly report
Primary Actor: Manager
Pre-Condition: View Report
Main Flows:
2. Select the Report
3. Display the Sub Menu: View
Booking Report, View Staff Report,
View Member Report.

- If the manager selects View Booking Report, the S1: View Booking Report subflow is
performed.
- If the manager selects View Staff Report, the S2: View Staff Report is performed.
- If the manager selects View Member Report, the S3: View Member Report subflow is
performed.

Sub Flow:
S1: View BookingReport
1. Display View Booking Report for
manager to view booking report.
2. Manager select the month that he or
she want to view.

3. System will verify the month that

Project 39
manager select.
4. System displays the booking report.

S2: View Staff Report
1. Display View Staff Report for manager
to view staff report.
2. Manager select the month that he or
she want to view.

3. System will verify the month that
manager select.
4. System displays the staff report.

S3: View Member Report
1. Display View Member Report for
manager to view member report.
2. Manager selects the month and
member type that he or she want to
view.

3. System will verify the month and
member type that manager select.
4. System displays the member report.


Project 40
ix. Use Case Name: Member Login
Brief Description: Member need to login to the system in order to perform the
functions.
Primary Actor: Member
Main Flows:
1. Display Member Login Screen.
2. Enter Member IC No.
3. Verify member IC No.
4. Display Member Details.
Alternative Flow:
- A1 step 3: If member IC No entered by member is invalid data, system will display


Project 41
2.6 Class Diagram

Chapter 3

System Design

Fitness Center System Chapter 3 : System Design

Project 43
3 3. . S Sy ys st t e em m D De es si i g gn n
This chapter will show the designing of the proposal system which are including ERD
Diagram, Activity Diagram and Sequence Diagram. Data Dictionary and system
design of the proposal diagram also will be showed.


Project 44
3.1 ERD Diagram


Project 45
3.2 Activity Diagram

i) Login Activity Diagram

ii) Change Password Activity Diagram


Project 46
iii) Maintain Customer Overview Activity Diagram


Project 47
a) Add Customer Activity Diagram


Project 48
b) Edit Customer Activity Diagram

c) View Customer Activity Diagram


Project 49
d) Delete Customer Activity Diagram

e) Check Customer Attendance Activity Diagram


Project 50
f) Add Customer Attendance Activity Diagram


Project 51
iv) Maintain Staff Overview Activity Diagram


Project 52
a) Add Staff Activity Diagram


Project 53
b) Edit Staff Activity Diagram


Project 54
c) View Staff Activity Diagram

d) Delete Staff Activity Diagram


Project 55
v) Maintain Booking Overview Activity Diagram


Project 56
a) Add Booking Activity Diagram


Project 57
b) View Booking Activity Diagram

c) Delete Booking Activity Diagram


Project 58
vi) Maintain Activity Overview Activity Diagram


Project 59
a) Add Activity / Class Activity Diagram


Project 60
b) Edit Activity / Class Activity Diagram


Project 61
c) View Activity / Class Activity Diagram

d) Delete Activity / Class Activity Diagram


Project 62
vii) Generate Report Overview Activity Diagram


Project 63
a) Generate Booking Report

b) Generate Member Report


Project 64
c) Generate Staff Report

viii) Member Login Activity Diagram


Project 65
3.3 Sequence Diagram

i) Login Sequence Diagram

ii) Change Password Sequence Diagram


Project 66
iii) Maintain Customer Module Sequence Diagram
a) Add Customer Detail

b) Edit Customer Detail


Project 67
c) View Customer Detail

d) Delete Customer Detail


Project 68
e) Check Customer Attendance

f) Add Customer Attendance


Project 69
iv) Maintain Staff Module Sequence Diagram
a) Add Staff Detail

b) Edit Staff Detail


Project 70
c) View Staff Detail

d) Delete Staff Detail


Project 71
v) Maintain Booking Module Sequence Diagram
a) Add Booking Detail

b) View Booking Detail


Project 72
c) Delete Booking Detail


Project 73
vi) Maintain Activity Module Sequence Diagram
a) Add Activity Detail

b) Edit Activity Detail


Project 74
c) View Activity Detail

d) Delete Activity Detail


Project 75
vii) Report Sequence Diagram
a) Generate Booking Report

b) Generate Member Report


Project 76
c) Generate Staff Report

viii) Member Login Sequence Diagram


Project 77
3.4 Data Dictionary
Customer Table

Field Name Data Type Length Description PK / FK
CustID int - A Unique ID to identify the each
Customer
PK
CustName nvarchar MAX A field that indicate the Customers
Name
-
CustAddress nvarchar MAX A field that indicate the Customers
Address
-
CustAge int - A field that indicate the Customers
Age
-
CustGender nvarchar 50 A field that indicate the Customers
Gender
-
CustICNo nvarchar 50 A field that indicate the Customers
IC.No
-
CustPhone nvarchar 50 A field that indicate the Customers
Phone
-
CreateDateTime datetime - A field that indicate the Customers
Register Date
-
Active bit - A field that indicate the Customers
record is Active or Inactive
-
MemberID decimal 18,0 A field that indicate the Members ID FK

Customer Attendance Table

AttendID int - A Unique ID to identify the each
Customer Attendance
PK
CustomerID int - A field that indicate the Customer
Information
FK
ActivityID int - A field that indicate the Activity that
Customer join
FK
Active bit - A field that indicate the Customer
Attendance record is Active or
Inactive
-

Project 78
Member Table

MemberID decimal 18,0 A Unique ID to identify the each
Member
PK
MemberName nvarchar 50 A field that indicate Members
Name
-
MemberAddress nvarchar MAX A field that indicate Members
Address
-
MemberAge int - A field that indicate Members Age -
MemberGender nvarchar 50 A field that indicate Members
Gender
-
MemberICNo nvarchar 50 A field that indicate Members IC
No.
-
MemberPhone nvarchar 50 A field that indicate Members
Phone
-
CreateDateTime datetime - A field that indicate new Member
Entered Date and Time
-
Active bit - A field that indicate the Members
-
MemberType nvarchar 50 A field that indicate the Type of
Members
-
Weight int - A field that indicate Members
Weight
-
Height int - A field that indicate Members
Height
-
BodyCondition nvarchar MAX A field that indicate Members Body
Condition
-
ActivityID int - A field that indicate Members
Activity
FK
StaffID int - A field that indicate the Staffs ID FK


Project 79
Staff Table

StaffID int - A Unique ID to identify the each
Staff
PK
StaffName nvarchar MAX A field that indicate the Staffs
Name
-
StaffAddress nvarchar MAX A field that indicate the Staffs
Address
-
StaffAge int - A field that indicate the Staffs
Age
-
StaffGender nvarchar 50 A field that indicate the Staffs
Gender
-
StaffICNo nvarchar 50 A field that indicate the Staffs
IC.No
-
StaffPhone nvarchar 50 A field that indicate the Staffs
Phone
-
Position nvarchar 50 A field that indicate the Staffs
Position
-
StaffPassword nvarchar 50 A field that indicate the Staffs
Password
-
CreateDateTime datetime - A field that indicate the Create
Staffs Date
-
Active bit - A field that indicate the Staffs
-


Project 80
Reward Point Table

Gift Table

RewardID int - A Unique ID to identify the each
reward.
PK
TotalRewardPoint int - A field that indicate Total
Reward Point for particular
Member.
-
TotalPointRedeem int - A field that indicate Total Point
that Redeem by each Member.
-
CreateDateTime datetime - A field that indicate the Date
and Time for new Reward Point
-
Active bit - A field that indicate the Reward
Points record is Active or
Inactive
-
MemberID decimal - A field that indicate Members
ID
FK
StaffID int - A field that indicate the Staffs
ID
FK
PaymentID int - A field that indicate the
Payments ID
FK
GiftID int - A Unique ID to identify the each Gift PK
GiftName nvarchar 50 A field that indicate Name of the Gift -
Qty int - A field that indicate the Quantity for
the particular Gift
-
TotalPoint int - A field that indicate the Total Point
for the particular Gift
-
CreateDateTime datetime - A field that indicate the Date and
Time for new Gift
-
Active bit - A field that indicate the Gifts record
is Active or Inactive
-
RewardID int - A field that indicate Rewards ID FK

Project 81
Activity Table

ActivityID int - A Unique ID to identify the each
Activity
PK
ActivityName nvarchar MAX A field that indicate the Activitys
Name
-
Quantity int - A field that indicate the Activitys
Quantity
-
ActivityStartTime nvarchar 50 A field that indicate the Activitys
StartTime
-
ActivityEndTime nvarchar 50 A field that indicate the Activitys
End Time
-
ActivityGroup nvarchar 50 A field that indicate the Activitys
Group
-
Activitys Date
-
Active bit - A field that indicate the Activitys
-

Reserve Table

Field Name Data Type Length Description PK /
FK
ReserveID int - A Unique ID to identify the each
Reserve ID
PK
BookingDate datetime - A field that indicate Booking Date -
ReserveQty int - A field that indicate the total quantity
of the activity have been book
-
Active bit - A field that indicate the status of
reserve
-
ActivityID int - A field that indicate the Activitys ID FK

Project 82
Booking Table

BookingID int - A Unique ID to identify the each
Booking
PK
Booking Date
-
BookingDate datetime - A field that indicate Booking Date -
BookingQty int - A field that indicate the Booking
Quantity
-
Active bit - A field that indicate the booking
-
StaffID int - A field that indicate the Staffs ID FK
MemberID decimal 18,0 A field that indicate the Members
ID
FK
ActivityID int - A field that indicate the Activitys
ID
FK

Payment Item Table

PaymentItemID int - A Unique ID to identify the each
payment items
PK
ItemName nvarchar 50 A field that indicate item of the
payment
-
Price decimal - A field that indicate price for the
particular item
-
CreateDateTime datetime - A field that indicate the date and
time for new payment item
-
RewardPoint int - A field that indicate the point will
gain for the payment item
-
Active bit - A field that indicate the status of
item
-

Project 83
Payment Table

PaymentID int - A Unique ID to identify the
each Payment
PK
PaymentType nvarchar 50 A field that indicate Payment
Type
-
TotalPayment decimal - A field that indicate Total for
each Payment
-
CreateDateTime datetime - A field that indicate the Date
and Time for create Payment
-
NewPaymentDateTime datetime - A field that indicate the Date
and Time for new Payment
-
Balance decimal - A field that indicate Balance
for each Payment
-
MemberID decimal 18,0 A field that indicate the
Members ID
FK
StaffID int - A field that indicate the staffs
ID
FK
PaymentItemID int - A field that indicate the
Payment Items ID
FK

Project 84
3.5 System Design
Login

Change Password


Project 85
Main Menu

Admin Main Menu


Project 86
Search Customer Detail

Customer Detail


Project 87
Search Customer Attendance

Add Customer Attendance


Project 88
Search Booking Detail

Booking Detail


Project 89
View Daily Booking

Search Staff Detail


Project 90
Add Staff Detail

Member Login


Project 91
Search Activity Detail

Activity Detail


Project 92
Report Form

Chapter 4

Programming

Fitness Center System Chapter 4 : Programming

Project 94
4 4. . P Pr ro og gr ra am mm mi i n ng g
This chapter will discuss about the programming that used to develop the system
which will include the programming approach and tool.


Project 95
4.1 Programming Tool
The programming language that I used to develop my system is VB.Net. It is used
because the system is window based system. VB.Net has the toolbox that allows the
developer to drag and drop the object that they want. With the feature, it is easy for us
to design the user interface.
4.2 Programming Approach
The programming approach that I used to develop my system is three tier design
architecture. Three-tier architecture which the user interface, business logic and data
access are developed and maintained as independent modules, some time on separate
platforms.By using this approach, all code is separate clearly and can be reuse by
other classes.


Project 96
This is the parts of the example to show the three tier design architecture that I had use in my
system:

User Interface

Try
aStaff =New StaffBAL(StaffID, StaffPassword)
astaff.UpdatePassword()
MessageBox.Show("Password Updated")

Catch ex As DuplicateException
MessageBox.Show(ex.Message)
End Try

Business Logic (BAL)

Public Sub UpdatePassword()
StaffDAL.UpdatePassword(Me)
End Sub

Data Access (DAL)

Public Shared Sub UpdatePassword(ByVal aStaff As StaffBAL)

staffPassword =aStaff.aStaffPassword
staffID =aStaff.aStaffID

Dim sqlUpdate As String ="Update STAFF" & _
" SET StaffPassword ='" & staffPassword & "' WHERE STAFFID ='" & staffID & "'"

Try
Initialize()

Dim adpstaff As New SqlDataAdapter()
adpstaff.UpdateCommand =New SqlCommand(sqlUpdate)

adpstaff.UpdateCommand.Connection =conStaff
adpstaff.UpdateCommand.ExecuteNonQuery()

Catch e As Exception
MessageBox.Show(e.Message)

Finally
Terminate()
End Try

End Sub

User Interface will invoke Business
Logics Update Password Function
Business Logic will invoke Data Accesss Update
Password Function to update the password in database

Chapter 5

Software Testing

Fitness Center System Chapter 5 : Software Testing

Project 98
5 5. . S So of ft t w wa ar re e T Te es st t i i n ng g
This chapter will discuss the software testing with different methods that have been
gone through.


Project 99
5.1 Type of Testing
i) Unit Testing
Unit testing is a software development process in which the smallest testable parts of
an application. Unit Testing also can be called as module Testing. Unit testing also
can define as the self-testing module by module before it combines with other
module. I will perform the unit testing when I finished one module to ensure the
module can run smoothly before I proceed to another module.

ii) Integration Testing
Integration testing is a logical extension of unit testing. Integration testing, also
known as integration and testing (I&T), is a software development process which two
units that have already been tested are combined into a component and tested as
groups in multiple ways. I will perform the integration testing when I finished some
of the module. For Example, Booking and Staff module are link. Each booking are
arrange by one staff. After member add the booking, I need to make sure the staff
information will record in the booking table. When the staff view back the record, all
information need to ensure are correct.

iii) Acceptance Testing
Acceptance testing is a final stage of testing that is performed on a system before
delivered to a live environment. The acceptance testing are continue test until the user
agree that the deliverable system is acceptance. Acceptance tests are generally
performed as "black box" tests. Black box testing means that the tester uses specified
inputs into the system and verifies that the resulting outputs are correct, without
knowledge of the system's internal workings. The acceptance testing will perform by
Mr Ku Cheng Fui and Ms Tan Lay Aik before the system is submitted.


Project 100
5.2 Test Plan
i) Login
No. Test Data Result Expected Action
1 User does not enter the UserName
and Password.
Message show user request to
enter information.
Reenter
2 User enters incorrect UserName
and Password.
Message show wrong UserName
and Password.
Reenter
3 User enters correct UserName and
Password.
Redirect to main menu. Ok

ii) Change Password
1 User enters incorrect UserName
and Password.
Message show wrong UserName
and Password.
Reenter
2 User enters new Password do not
match with confirm password.
Message show new password
does not match.
Reenter
3 User correct enters the required
field and click confirm button.
Message show Password
Updated and redirect to login
menu.
Ok


Project 101
iii) Maintain Customer Module
1 User does not enter any data. Message shows please fill in all
information.
Ok
2 User does not enter customer ID
for searching customer record.
Message show please enter the
Customer ID to proceed
Ok
3 User does not enter customer IC
No for searching customer record.
Customer IC No to proceed
Ok
4 User does not enter customer
name for searching customer
record.
Customer name to proceed.
Ok
5 User click add new customer
button.
Redirect to add customer detail
form.
Ok
6 User click check customer
attendance button.
Redirect to search customer
attendance detail form.
Ok
7 User click reset button. All field will free of data. Ok
8 User click add customer as
member button.
Redirect to add member detail
form.
Ok
9 User click update customer button
after click edit.
The edited field will show the
updated data.
Ok
10 User click Delete customer
button.
Customer record will be
removing.
Ok
11 User click save customer button
after click new.
The new record will added in
database.
Ok
12 User does not enter customer ID
for searching customer attendance
record.
Message Show please enter the
Customer ID to proceed.
Ok
13 User click add new customer Redirect to add customer Ok

Project 102
attendance button. attendance detail form.
14 User click save customer
attendance button after click new.
database.
Ok
15 User click back button. Redirect to search customer
attendance detail form.
Ok

iv) Maintain Staff Module
1 User does not enter any data. Message show please fills in all
information.
Ok
2 User does not enter staff ID for
searching staff record.
Staff ID to proceed
Ok
3 User does not enter staff IC No
for searching staff record.
Staff IC No to proceed
Ok
4 User does not enter staff name for
searching staff record.
Message Show please enter the
Staff name to proceed.
Ok
5 User click add new staff button. Redirect to add staff details
form.
Ok
7 User click update staff button
after click edit.
updated data.
Ok
8 User click Delete staff button. Staff record will be removing. Ok
9 User click save staff button after
click new.
database.
Ok


Project 103
v) Maintain Activity Module
information.
Ok
2 User does not enter activity ID for
searching activity record.
Activity ID to proceed
Ok
3 User does not enter activity name
for searching activity record.
Activity name to proceed.
Ok
4 User click add new activity
button.
Redirect to add activity details
form.
Ok
7 User click update activity button
after click edit.
updated data.
Ok
8 User click Delete activity button. Activity record will be
removing.
Ok
9 User click save activity button
after click new.
database.
Ok

vi) Maintain Booking Module
information.
Ok
2 User does not enter booking ID
for searching booking record.
Booking ID to proceed.
Ok
3 User does not enter member ID
for searching booking record.
member ID to proceed.
Ok
4 User click add new booking
button.
Redirect to add booking details
form.
Ok

Project 104
7 User does not enter booking date
for searching daily booking
record.
bookig date to proceed.
Ok
8 User click Delete booking button. Booking record will be
removing.
Ok
9 User click save booking button
after click new.
database.
Ok
10 User clicks export booking to
excel button.
Booking record will export to
Microsoft Excel.
Ok

vii) Member Login
1 User does not enter member IC
No.
Message show please enter
Member IC No.
Reenter
3 User enters incorrect data. Message show record not found. Reenter
4 User enters correct member IC
No.
Member is allowing enter to
fitness center.
Ok

viii) Report
1 User does not enter any data. Message show please select data. Reenter
2 User enters incorrect data. Message show record not found. Reenter
3 User enters correct data. Redirect to report form. Ok

Chapter 6

Conclusion

Fitness Center System Chapter 6 : Conclusion

Project 106
6 6. . C Co on nc cl l u us si i o on n
This chapter is to conclude the system that have been done, conclusion and
recommendation. Besides, this chapter will discuss the strengths and weaknesses of
the system.


Project 107
6.1 Linkage to seminar
As conclusion, barcode system which related to my seminar has been applied in the
fitness center system. Barcode system can be use in when the member come to the
fitness center, member can scan the IC No at the member card. So member will know
the next payment date. I had done a form for the member self check-in for them.
Though members who not paying for their monthly fee are not allowed entering into
fitness center. The purpose is to ensure financial transaction between the member and
fitness center.
6.2 Evaluation of project strengths and weaknesses
Strengths
- User interface of the system is user friendly and easy to use.
- System provides may view for user to search the record.
- Error message, warning message and information message are given for user when
they target the function.
- Authorization control also include in the login form in order to eliminate the
unauthorized access to the system.
- System provides the validation to validate the invalid data.
- System can reduce the paper work and save human resources for example time and
effort.
- System is allowing member to do self check-in to the fitness center.

Weaknesses
- System is offline, unable to let member to do booking online.
- System provides less animation, it may be less attractive to user.
- Due to want to achieve standardise of the system, so system interface is bored
interface.


Project 108
6.3 Suggestion for the future improvement

The suggestion for the future improvement is after the member makes booking,
Fitness Center System need to send notification to them to ensure member is
attending for the activity class. For example, if the member make booking or
reservation at 10 March 2011, that mean that the system need to automatically send
the sms, phone call or email to member to double confirm with member whether they
will attend the for the tomorrow activity.

Filtering for the report is another improvement in the future. In the report, additional
filtering can be done in order can get more clear and precise data. Crystal report is the
good tool for design the report. Unfortunately, crystal report is not used in our Fitness
Center System. Due to lack of time, we use the window form to show out the data
instead of using crystal report.

Besides that, the system can be further improved in the design interface. We will try
to add in more animation in our system to increase the attractive of the interface.
Another future improvement is tried to make our system online. So member can check
their booking detail and make booking online.


Project 109
6.4 Conclusion
As a conclusion, we had learned a lot of knowledge while doing this project. After
done the entire project, we have the experienced difficulties to developing a complete
software application.
During this few months develop; we faced some of the problem. We very appreciated
our friends that help us and give us some opinion about the system. The most
difficulties problem that we faced is when we are developing the booking module.
Fortunately, our friend who are willing to share out their experience and opinion
while we faced problem. But still have some problem we needed to find out ourselves
through internet. But at last, we had learned how to develop a system phase by phase.
Time management is most important during develop a system. If system has the
proper or good time management, the systems that produce will more quality.
Furthermore a well planning will save effort and time as it eliminate the extra work
after planning. All the project objective has been successfully reach by us.
Lastly, this project brings a lot of benefit to us because through this project we had
learned that have a proper time management is essential and helping us improve our
programming skill.

Fitness Center System References

Project 110
7 7. . R Re ef f e er re en nc ce es s

i) Donald Bell, 2004, UML Basics: The Sequence Diagram, Viewed 18 May
2010, http://www.ibm.com/developerworks/rational/library/3101.html
ii) Indranil Chatterjee, 2010, VBExcel Sheet, Viewed 11 J uly 2010,
http://www.a1vbcode.com/app-4933.asp
iii) Nirosh, 2011, Introduction to object Oriented Programming concept and more,
viewed 28 J anuary 2011,
http://www.codeproject.com/KB/architecture/OOP_Concepts_and_manymore.
aspx#Architecture
iv) Peter, 2010, Sorting DataGridView for Collection Generic Data, Viewed 4
December 2010, http://www.a1vbcode.com/app-5083.asp

Fitness Center System Appendices

Project 111
8 8. . A Ap pp pe en nd di i c ce es s
The entire content are include in the document except the business rule, operation
environment and development environment.


Project 112
8.1 Business Rule
Each payment can only make one payment for the membership and each membership
payment can only be making by one member.
One staff can serve many members; each member can serve by many staff.
One member can make one or many bookings in different time; each booking was
making by zero or many members.
Each staff handled one or more bookings in a day, each booking can only handled by
one staff.
One staff only can have one staff record.
One member only can have one record.
Staff needs to log in before to make the transaction
Each member has their own locker. One locker is belong to one member
Each member who loss the member card only can renew the card twice each year
The customer needs to register before join our fitness club.
Each customer can serve by only one consultant
Each member allows joining many fitness classes.
Each fitness class only has one trainer.


Project 113
8.2 Development Environment
Programming Language: Microsoft Visual Basic 2008
Database: SQL Server 2005
Hardware: Personal Computer, Canon printer, Pendrive, scanner
Software: Microsoft office 2007, Rational Software Architect, Microsoft window XP
Professional, Microsoft Window Vista, Visual Basic Studio, Visual Paradigm for
UML 7.0 Enterprise Edition, Paint

8.3 Operation Environment

Application
Server
Data
Warehouse
Firewall PC
Operational
Database
Barcode Reader
Fitness Center System User Guide

Project 114
9 9. . U Us se er r G Gu ui i d de e
9.1 Splash Screen

9.2 Login

1. Allow user to key in the Username and Password.
2. Click link to Change Password form.
3. Click to Login.
1
2
3
4

Project 115
4. Exit the system.

After click Login, system will verify which user login and show the message.

9.3 Change Password

1. Allow user to key in the change password detail.
2. Click to confirm the change password detail.
3. Click back to login form.

Message will show when user click confirm button.
1
3
2

Project 116
9.4 Main Menu

1. Click to Activity Form.
2. Click to Booking Form.
3. Click to Customer Form.
4. Click to Member Form.
5. Click to Reward Form.
6. Click to Staff Form.
7. Click to Report Form.
8. Click to Exit Login Form.
1
4
5 6
3 2
7
8

Project 117
9.5 Admin Main Menu

1. Click to Activity Form.
2. Click to Gift Form.
3. Click to Payment Item Form.
4. Click to Exit Login Form.

1
3 2
4

Project 118
9.6 Search Activity Detail Form

1. Allow user to select the Activity ID radio button and key in the Activity ID to
search activity detail.

This message will show when there are no records for the Activity ID.

2. Allow user to select the Activity Name radio button and key in the Activity
Name to search activity detail.

This message will show when there are no records for the Activity Name.
1
2
3
4
5
6

Project 119
3. Click to search activity details.
4. Click to reset the entire field.
5. Display the Activity Detail and can double click the activity record for further
view the particular activity detail.
6. Click back to main menu.

9.7 Search Customer Detail Form

1. Allow user to select the Customer ID radio button and key in the Customer ID
to search customer detail.

This message will show when there are no records for the Customer ID.

1
2
4
5
6
3
7
8
9

Project 120
2. Allow user to select the Customer Name radio button and key in the Customer
Name to search customer detail.

This message will show when there are no records for the Customer Name.

3. Allow user to select the Customer IC No radio button and key in the Customer
IC No to search customer detail.

This message will show when there are no records for the Customer IC No.

4. Click to search customer details.
6. Display the Customer Detail and can double click the customer record for
further view the particular customer detail.
7. Click to add new customer detail.
8. Click to check the customer attendance.


Project 121
9.8 Customer Detail Form

1. Allow user to key in the member details.
2. Click to add customer as member.
3. Click to create new customer record.
4. Click to edit customer record.
2
3
4
5
1
6
7
8 9

Project 122

This message will show when records has been successful edited.

5. Click to delete customer record.

This message will show when records has been successful deleted.

7. Error Icon will display when user miss to key in the customer detail.
8. Click to save the customer record.

This message will show when records is added into database.

9. Click to cancel the add customer process.


Project 123
9.9 Check Customer Attendance Detail

1. Allow user to select the Customer ID radio button and key in the Customer ID
to search customer attendance detail.

This message will show when there are no record for the Customer ID.

2. Display the Customer attendance Detail and can double click the customer
attendance record for further view the particular customer attendance detail.
3. Click to search customer attendance details.
5. Click to add new customer attendance detail.

1
6
2
3
4
5

Project 124
9.10 Add Customer Attendance Detail

1. Click to search customer detail

This message will show when user do not click the search button to search
customer detail.

2. Select the activity that customer want to join.

This message will show when user do not select the activity name drop down
list.

1
2
3 4

Project 125
3. Click to add the customer attendance record.

This message will show when user successful add the customer attendance
record.

4. Click back to search customer attendance detail.

9.11 Search Staff Detail

1. Allow user to select the Staff ID radio button and key in the Staff ID to search
staff detail.

1
4
2
8
7
6
5
3

Project 126
This message will show when there are no record for the Staff ID.

2. Allow user to select the Staff Name radio button and key in the Staff Name to
search staff detail.

This message will show when there are no record for the Staff Name.

3. Allow user to select the Staff IC No radio button and key in the Staff IC No to
search staff detail.

This message will show when there are no record for the Staff IC No.

4. Display the Staff Detail and can double click the staff record for further view the
particular staff detail.
5. Click to search staff details.
7. Click to add new staff detail.


Project 127
9.12 Staff Detail Form

1. Allow user to key in the staff details.
2. Click to create new staff record.
3. Click to edit staff record.
2
1
7
6
5
3
4
8

Project 128


4. Click to delete staff record.


6. Error Icon will display when user miss to key in the staff detail.
7. Click to save the staff record.

This message will show when user successful add the staff record.

8. Click to cancel the add staff process.


Project 129
9.13 Search Booking Detail

1. Allow user to select the Booking ID radio button and key in the Booking ID to
search booking detail.

This message will show when there are no record for the Booking ID.

2. Allow user to select the Member ID radio button and key in the Member ID to
search Booking detail.

This message will show when there are no record for the Member ID.
1
3
2
4
5
6
7
8

Project 130
3. Display the Booking Detail and can double click the booking record for further
view the particular booking detail.
4. Click to search booking details.
6. Click to view daily booking detail.
7. Click to add new booking detail.

9.14 View Daily Booking Detail

1. Click Booking Date drop down list to select the booking date.

This message will show when there are no record for the Booking Date.

2. Click to search the booking detail.
3. Display the booking detail.
4. Click to export the data grid view data to Microsoft excel.
2
1
4
3

Project 131
9.15 Booking Detail Form

1. Allow user to key in the booking details.
2. Click to create new booking.
2
1
3
5
6
7
8
4

Project 132
3. Click to delete booking record.


5. Error Icon will display when user miss to key in the booking detail.
6. Booking record will be show when user selects the activity.
7. Click to save the booking record.

This message will show when records has been successful added.

8. Click to cancel add booking process.


Project 133
9.16 Activity Detail Form

1. Allow user to key in the activity details.
2. Click to create new activity.
3. Click to edit activity record.
1
2
4
5
3
6
7
8

Project 134


4. Click to delete activity record.


5. Click back to admin main menu.
6. Error Icon will display when user miss to key in the activity detail.
7. Click to save the activity record.

This message will show when records has been successful added.

8. Click to cancel add activity process.


Project 135
9.17 Monthly Booking Report

1. Click Month drop down list to select the Month.

This message will show when user do not select the month.

2. Click to search monthly booking data.

This message will show when no record in database.

1
2

Project 136
Monthly Booking Report


Project 137
9.18 Monthly Member Report



2. Click Member Type drop down list to select the member type.


2
3
1

Project 138
3. Click to search monthly member data.


Monthly Member Report


Project 139
9.18 Monthly Staff Report



2. Click to search monthly Staff data.


1
2

Project 140
Monthly Member Report


Project 141
9.19 Member Login

1. Allow User key in the Member IC No.

This message will show when member do not pay month member fee.

2. Click to check the member detail.
3. Click to clear the entire field.
4. Display member detail.
1
2
3
4

Fitnes Center

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Fitnes Center

Загружено:

Авторское право:

Доступные форматы

F

Вам также может понравиться