BSc Project

CS Department
Project ID: UQU-CS-2017-55
December 2017

Online Sporting Club

Authors:

Supervisor:

Dr. Serine Al-Hadi

Dept. of computer science

College of Computer Science at Al-Qunfudah
Umm Al-Qura University, KSA
This project report is submitted to the Department of computer science at Umm Al-Qura
University in partial fulfillment of the requirements for the degree of Bachelor in
Computer Science.

Author(s):
First name last name Address E-mail

University supervisor(s):
Name
Mail
Department of computer science

Dept. of computer science

Faculty of Computer science at Al-Gunfudah
Umm Al Qura University

2
 Intellectual Property Right Declaration

This is to declare that the work under the supervision of ……………….. having title "
…………………………………. " carried out in partial fulfillment of the requirements of
Bachelor of Science in computer science, is the sole property of the Umm Al Qura
University and the respective supervisor and is protected under the intellectual property
right laws and conventions. It can only be considered/ used for purposes like extension
for further enhancement, product development, adoption for commercial/organizational
usage, etc., with the permission of the University and respective supervisor.

This above statement applies to all students and faculty members.

Date: ../…/2017

Author(s):
…………………………………. Signature:
……………….. Signature:
Signature:
Signature:
Signature:

Supervisor:
……………………………………… Signature:

3
 Anti-Plagiarism Declaration

This is to declare that the above publication produced under the supervision of
……………………………….. having title " ………………………………………." is
the sole contribution of the author(s) and no part hereof has been reproduced illegally (cut
and paste) which can be considered as Plagiarism. All referenced parts have been used to
argue the idea and have been cited properly. I/We will be responsible and liable for any
consequence if violation of this declaration is proven.

Date: …/…/2017

Author(s):
Signature:
Signature:
Signature:
Signature:
Signature:

4
 Acknowledgements

After a journey of research and effort and diligence

culminated in the completion of this research, thank God for his
blessing. We are pleased to express our sincere gratitude and
appreciation to Dr. Serene El Hadi for her efforts in guiding us to
this research. We also extend our sincere thanks to all those who
have helped us, especially Dr. Amina Al-Twi and Dr. Amal Al-
Kassibi. Without their presence, we would not have felt the
pleasure of work and the sweetness of research.

Table of Contents

Acknowledgements ……………………………………………………………………………..…ii
iii
Table of Contents ……………………………………………………………………………………………
iv
List of Figures ……………………………………………………………………………………………
5
Introduction ……………………………………………………………………………………………1
Chapter I: - Project Presentation …………………………………………….………………… 2
1.1 Introduction ……………………………….………………………………....…………………… 3
1.2 Existing System Description ....…….……………………………………. ………………….3
1.3 Proposed System Description …………………………………………………………………. 5
1.4 Project Management Approach ……………………………………………….…………………. 5
1.5 Schedule Planning …………………………………………………………….……………….. 8
1.6 Conclusion…………………………………………………………………………………………9
10
Chapter 2:- Analysis & Requirement Specification ……………………………………
2.1 Introduction …………………………………………………………………………………………… 11
2.2 System Analysis …………………………………………………………………………………………… 11
12
2.2.1 Actors Description ……………………………………………………………………………………………
2.2.2 Functional Requirements ………………………………………………………………………… 13
2.3 Use Case diagram …………………………………………………………………………………………… 14
3.4.2 Sequence diagrams ………………………………………………………………………… 16
2.5 Non-Functional Requirements ……………………………………………………… 33
2.6 Conclusion …………………………………………………………………………………………… 34
Chapter 3:- Design Considerations ……………………………………………………………… 35
3.1 Introduction ……………………………………………………………………………………………… 36
3.2 Hardware environment ………………………………………………………………………………………… 36
3.3 Software environment …………………………………………………………………………………………… 37
3.4 Conclusion ……………………………………………………………………………………………… 38
Chapter 4:- System Design ………………………………………………………………………………………… 39
4.1 Introduction ……………………………………………………………………………………………… 40
4.2 Class Description ……………………………………………………………………………………………… 40
4.3 Class Diagram ……………………………………………………………………………………………… 44
4.4 Conclusion ……………………………………………………………………………………………… 46
Conclusion and Perspective …………………………………………………………………………………………47

List of Figures

4
Figure (1) “www.fitnessarab.com” Website …………………………………………………………..…
4
Figure (2) “www.rashiqa.com” Website ……………….……………………………………………………
6
Figure (3) Waterfall Model …………………………………………..………………………………………………
8
Figure (4) Schedule of Project ……………………………………………………………………………………
6
 Figure (5) System actors ……………………………………………………….………………… 13
15
Figure (6) Use Case Diagram ……………………………….………………………………....……………………
Figure (7) “Login” Sequence Diagram ....…….…………………………………………. 16………………….
17
Figure (8) “Register” Sequence Diagram ………………………………………………………………….
18
Figure (9) “Search product” Sequence Diagram ………………………………………………………….
19
Figure (10) “View product” Sequence Diagram ………………………………………….………………..
20
Figure (11) “Add product” Sequence Diagram …………………………………………………………
Figure (12) “Update product” Sequence Diagram …………………………………… 21
22
Figure (13) “Buy product” Sequence Diagram …………………………………………………
23
Figure (14) “Payment” Sequence Diagram ……………………………………………………………………
Figure (15) “Add Coach” Sequence Diagram 24
…………………………………………………………………
25
Figure (16) “Choose Coach” Sequence Diagram …………………………………………………………
26
Figure (17) “change Coach” Sequence Diagram …………………………………………………………
Figure (18) “Delete Coach” Sequence Diagram ………………………………………… 27
28
Figure (19) “Update Coach/ customer” Sequence Diagram …………………………………
29
Figure (20) “Answer question” Sequence Diagram ……………………………………………………
Figure (21) “Send Reminder” Sequence Diagram ………………………………. 30
Figure (22) “Show Coach Details” Sequence Diagram …………………………..31
Figure (23) “Show Customer” Sequence Diagram ……………………………………..32
Figure (24) Server components …………………………………………………………………. 36
Figure (25) Class Diagram …………………………………………………………………………. 45

Introduction

Nowadays communication technology made a revolution in human’s life; there are

many studies that seek to make peoples ordinary tasks easier as possible. The ordinary

7
life of people now became much easier than previous decades that all depends on
ordinary methods to do usual life activities. The internet is now awesome method to
achieve many activities; one of those activities is serving people do their sporting
exercises without the need to go the sporting centers. This study research paves a way
to make a simple system to achieve that activity as a modern technique and make our
society, on the same side with urban countries. The methodology used is “System
Development Life Cycle” approach to develop the system.

8
 (Chapter 1)
Project Presentation

1.1 Introduction
Recently, with the spread of obesity and unhealthy diets and the people need of
sporting clubs people became aware how big the importance of sports and its relevance
to human health. It is not easy for all to fulfil their desires. There are some obstacles

9
 that may face people going to sporting clubs especially women as the society is not
allowing for women to go in such places. Besides, the expensive subscription of these
clubs make most people unable to pay for it. That leads many of society members to
miss practicing such an important activity.

1.2 Existing System Description

The current system is the traditional usual method of going to sporting clubs and
gyms to make practices using their own appliances and following of Coaches advices
using a big subscription fees. We can list the disadvantages of these methods as
follows:-

1- High subscription fees of sporting clubs.

2- It is sometimes hard for women to go out and communicate with others.
3- Hard day works sometimes take all the time that leads to not be able to go for
sporting clubs.
4- Difficulty in having an integrated and equipped place for this activity
5- Besides, if someone needs an appliance, he is obliged to go to sporting stores
himself to buy it.

The similar currently existed sites that made by the techniques will be used in our
system are offering limited resources of learning or following of Coaches advices.
Besides, it has no store for shopping. The currently similar systems contain just one of
the via-discussed activities. Some example of existed sites:

10
 Figure (1) “www.fitnessarab.com” Website

In this web application targets only a specific category and is a category of men and
a specific exercise system (bodybuilding), the subjects are limited, repetitive, and used
tools are expensive.

Figure (2) “www.rashiqa.com” Website

11
 It does not depend on certified trainers guidance, and not all the diet recipes
healthy, but all of it are part of the participants’ experiences' recipes and methods of
rapid slimming and popular mixes such as Chinese tea and slimming creams...etc. that
may be harmful.

1.3 Proposed System Description

After this study we found that making a web application will be the proper solution
for building the system needed, so we are going to make a web application using the
tools needed to coding and making user friendly interfaces. The solution is chosen after
making a study of current information technology techniques and differentiate between
the best in many aspects like lower errors that need debugging in periodic maintenance
and lower cost when designing and maintaining and easy user interfaces that can any
user act with it and meet all their needs. The proposed system overcame some of the
current system disadvantages:-

1- Interactive and easy to use.

2- No need for transportation to go and return.
3- Save people’s privacy.
4- Choosing the right time for the subscribing.
5- Nominal subscription fees.

1.4 Project Management Approach

One of the main approaches of SDLC is the Waterfall approach, which is first SDLC
(System Development Life Cycle) Model to be widely used in Software Engineering to
ensure success of the project. It is very simple to understand and use.  In a waterfall
model, each phase must be completed fully before the next phase can begin. At the end
of each phase, a review takes place to determine if the project is on the right path and
whether or not to continue or discard the project. In this model, the testing starts only

12
after the development is complete. The next figure shows the diagrammatic
representation of different phases of waterfall model. It contains (5) main steps.

Figure (3) Waterfall Model

13
o Stage 1: Planning and Requirement Analysis

Requirement analysis is the most important and fundamental stage in SDLC. It is

performed by the senior members of the team with inputs from the customer, the sales
department, market surveys and domain experts in the industry. This information is then
used to plan the basic project approach and to conduct product feasibility study in the
economical, operational and technical areas. Planning for the quality assurance
requirements and identification of the risks associated with the project is also done in the
planning stage. The outcome of the technical feasibility study is to define the various
technical approaches that can be followed to implement the project successfully with
minimum risks.

o Stage 2: Designing the Product Architecture

SRS is the reference for product architects to come out with the best architecture for
the product to be developed. Based on the requirements specified in SRS, usually more
than one design approach for the product architecture is proposed and documented in a
DDS – Design Document Specification. This DDS is reviewed by all the important
stakeholders and based on various parameters as risk assessment, product robustness,
design modularity, budget and time constraints, the best design approach is selected for
the product. A design approach clearly defines all the architectural modules of the product
along with its communication and data flow representation with the external and third
party modules (if any). The internal design of all the modules of the proposed architecture
should be clearly defined with the minutest of the details in DDS.

o Stage 4: Building or Developing the Product

In this stage of SDLC the actual development starts and the product is built. The
programming code is generated as per DDS during this stage. If the design is performed in

14
 a detailed and organized manner, code generation can be accomplished without much
hassle. Developers must follow the coding guidelines defined by their organization and
programming tools like compilers, interpreters, debuggers, etc. are used to generate the
code. Different high level programming languages such as C, C++, Pascal, Java and PHP are
used for coding. The programming language is chosen with respect to the type of software
being developed.

o Stage 5: Testing the Product

This stage is usually a subset of all the stages as in the modern SDLC models, the
testing activities are mostly involved in all the stages of SDLC. However, this stage refers to
the testing only stage of the product where product defects are reported, tracked, fixed
and retested, until the product reaches the quality standards defined in the SRS.

o Stage 6: Maintenance

Once the product is tested and ready to be deployed it is released formally in the
appropriate market. Sometimes product deployment happens in stages as per the
business strategy of that organization. The product may be released as it is or with
suggested enhancements in the targeting market segment. After the product is released in
the market, its maintenance is done for the existing customer base.

1.5 Schedule Planning

A Gantt chart, commonly used in project management, is one of the most popular
and useful ways of showing activities (tasks or events) displayed against time. On the
left of the chart is a list of the activities and along the top is a suitable time scale. Each
activity is represented by a bar; the position and length of the bar reflects the start date,
duration and end date of the activity. The followed plan tasks to achieve the project is
discussed as follows:-

15
16
 Figure (4) Schedule of Project

1.6 Conclusion
In this chapter, we introduced the general idea of our project mentioning the
current system and its disadvantages and the proposed solution with its advantages. In
addition, there is a project management approach to discuss the methodology used in
the project with a working plan schedule.

(Chapter 2)
17
 Analysis & Requirement
Specification

2.1 Introduction
The current research part paves a way to make a simple system as an online sporting
club web application for being used by all users. The system and user full requirements
are discussed in details through the current chapter. The following subjects also
contains system analysis using proper tools and diagrams. There are also some other
subjects that help in general system evolution.

2.2 System Analysis

18
 Systems analysis is defined as the process of observing systems for troubleshooting
or development purposes. It is applied to information technology, where computer-
based systems require defined analysis according to their makeup and design. It is also
described as the act or process of studying an activity (such as a procedure, a business,
or a physiological function) typically by certain means in order to define its goals or
purposes and to discover operations and procedures for accomplishing them most
efficiently. Though the following subject on of the most important tools in system
analysis is used “UML”.

Unified Modeling Language (UML)

UML (Unified Modeling Language) is a standard notation for the modeling of real-
world objects as a first step in developing an object-oriented design methodology. It
uses graphic notation to create visual models of software systems. UML diagrams can be
divided into two categories:-

- The first type includes six diagram types representing structural

information.
- The second includes the remaining seven diagrams representing general
types of behavior.

Structure diagrams are used in documenting the architecture of software systems

and are involved in the system being modeled. Different structure diagrams are: 

- Class Diagram
- Component Diagram
- Deployment Diagram
- Composite Structure Diagram
- Object Diagram
- Package Diagram

Behavior diagrams represent functionality of software system and emphasize on

what must happen in the system being modeled. The different behavior diagrams are: 

19
 - Activity Diagram
- Use Case Diagram
- UML State Machine Diagram
- Communication Diagram
- Timing Diagram
- Interaction Overview Diagram
- Sequence Diagram

To determine the features, structures and relationships of the elements involved in

the proposed system, and clarify the chronology of messages between them, the object-
oriented approach is chosen. That means using the following diagrams:-

1. Use case diagram: to describe functionality of a system in terms of actors, goals as

use cases and dependencies among the use cases.
2. Sequence diagram: to represent communication between objects in terms of a
sequence of messages.
3. Class diagram: to represent system class, attributes and relationships among the
classes.

2.2.1 Actors Description

It is used to describe functionality of a system in terms of actors, goals as sub use

cases and dependencies among them. The following table shows the actors:-

Sn. Actor Description

Subscribed This actor contains all registered customers, the roles conclude in
1 choosing, changing and asking a coach.
Customer

This actor contains any unregistered visitor that can only register,
2 Customer
view, buy or search product or payment.

This actor is the coach that works on the system to show and answer
3 Coach
customers (answer advice or answer exercise).

20
 This actor is the system manager that has the privileges to
manipulate the database records and mange users’ accounts. He can
4 Administrator
add, edit or delete coach. Also, can add, edit or delete products and
send reminder and show coach details.

Figure (5) System actors

2.2.2 Functional Requirements

Functional requirement defines a function of a system or its component. A function
is described as a set of inputs, the behavior, and outputs. Functional requirements may
be calculations, technical details, data manipulation and processing and other specific
functionality that define what a system is supposed to accomplish. The following are the
requirements with some details: -

Administrator Requirements: -

- The Admin should be able to login.

- The Admin should be able to add coach.
- The Admin should be able to edit coach.
- The Admin should be able to delete coach.
- The Admin should be able to show coach details.
- The Admin should be able to add product.
- The Admin should be able to edit product.
- The Admin should be able to delete product.
- The Admin should be able to add send reminders

Customer Requirements: -

- The Customer should be able to register.

- The Customer should be able to login.
- The Customer should be able to view product.
- The Customer should be able to buy product.

21
 - The Customer should be able to make payment.
- The Customer should be able to search product.

Subscribed Customer Requirements: -

- The Subscribed Customer should be able to login.

- The Subscribed Customer should be able to choose Coach.
- The Subscribed Customer should be able to change coach.
- The Subscribed Customer should be able to ask coach.
- The Subscribed Customer should be able to ask for advice.
- The Subscribed Customer should be able to ask for exercise.

Coach Requirements: -

- The Coach should be able to login.

- The Coach should be able to show customer.
- The Coach should be able to answer customer.
- The Coach should be able to answer advice.
- The Coach should be able to answer exercise.

2.3 Use Case diagram

A use case represents how a system interacts with its environment by illustrating
the activities that are performed by the users and the system’s responses. Use cases are
a means of expressing user requirements. Use cases are used extensively in the analysis
phase. Use cases are very useful tools to us to understand user requirements. However,
use cases only convey the user’s point of view. Transforming the user’s view into the
developer’s view by creating functional requirements is one of the important
contributions of system analyst.

22
23
 Figure (6) Use Case Diagram

3.4.2 Sequence diagrams

24
 It is the most common kind of interaction diagram, which focuses on the message
interchange between a number of lifelines. Sequence diagram describes an interaction
by focusing on the sequence of messages that are exchanged, along with their
corresponding occurrence specifications on the lifelines. The following are some of the
systems’ sequence diagrams:-

A. Login

Figure (7)
“Login” Sequence Diagram

25
B. Register

Figure (8) “Register” Sequence Diagram

26
C. Search product

Figure (9) “Search product” Sequence Diagram

27
D. View product

Figure (10) “View product” Sequence Diagram

28
E. Add product

Figure (11) “Add product” Sequence Diagram

29
F. Update product

Figure (12) “Update product” Sequence Diagram

30
G. Buy product

Figure (13) “Buy product” Sequence Diagram

31
H. Payment

Figure (14) “Payment” Sequence Diagram

32
I. Add Coach

Figure (15) “Add Coach” Sequence Diagram

33
J. Choose Coach

Figure (16) “Choose Coach” Sequence Diagram

34
K. Change Coach

Figure (17) “change Coach” Sequence Diagram

35
L. Delete Coach

Figure (18) “Delete Coach” Sequence Diagram

36
M. Update Coach / customer

Figure (19) “Update Coach/ customer” Sequence Diagram

37
N. Answer question

38
 Figure (20) “Answer question” Sequence Diagram

O. Send Reminder

39
 Figure (21) “Send Reminder” Sequence Diagram

P. Show Coach Details

40
 Figure (22) “Show Coach Details” Sequence Diagram

Q. Show Customer

41
 Figure (23) “Show Customer” Sequence Diagram

2.5 Non-Functional Requirements

A non-functional requirement is a requirement that specifies criteria that can be

used to judge the operation of a system, rather than specific behaviors. This should be

42
contrasted with functional requirements that define specific behavior or functions. It
includes several criteria some of it shortly discussed below:-

a. Performance: - The system should be with high performance in achieving

tasks and operations in the whole systems. Also response time should be
fast in responding to the user usage and supports multiple users at a time.

b. Accessibility: - System should be accessed through the internet so any user

can use it by Smart phone.

c. Accuracy: - System should give accurate details and information about the
contained products and other subjects.

d. Reliability: - The system should be available to all users all the time. Also
should provide a backup plan for the database so the data will be in safe
and can be retrieved easily when needed.

e. Usability The system should be interactive and easy to use and requires
least effort to operate (user friendly). It also should support the Arabic
language if available.

f. Availability: - The system should accept as many users' requests with no

break down or failures

g. Portability: - The application is made using HTML, CSS and PHP programing
languages which are platform independent and can be transported to
other servers with minimum effort.

h. Security: - The system users must have complicated usernames and

passwords to access the system services. Only the administrator is
responsible for the safety of system structures and database records.

i. Recoverability: - The system can be easily recovered in case of failures, in

favor of the scheduled "Backups" that been stored on an external Hard
43
 Disk Drive.

j. Manageability: - The system can be managed by the administrator through

his control panel page. The database can be managed easily through the
"PHPMyadmin" control panel.

2.6 Conclusion

Systems analysis is a problem-solving method that involves looking at the wider

system, breaking apart the parts, and figuring out how it works in order to achieve a
particular goal. Through the via discussed subjects we made an analysis for the
proposed system with the proper tools that help us to make a step forward to design
phase.

44
 (Chapter 3)
Design Considerations

45
 3.1 Introduction

Before designing any system, there should be some considerations and

prerequisites that are important to give a proper system design without complications.
Through the current chapter, some of them are discussed with details.

3.2 Hardware environment

Depending on the next table of the system server, best performance requirements
there are some needs to make the system works properly. These needs pave the way to
make a good working system. In our case, the main part of the system is to keep the
“server” computer in a safe environment that no one can reach it easily. Only prevailed
persons are the responsible for that. The server room environment should be cold and
dry to absorb as much as temperature come out from the speed of executing processes.
We are here talking about the “CPU”. In addition, the "Backup" operation should be
done on every system files and database in case of critical malfunctions. The automatic
backup operation is scheduled in certain periods and been retrieved if needed. The
administrator should be sure of keeping these situations available all time. There is no
limitation for the hardware used as the system can run easily when providing the next
server good performance requirements in the following table:-

Sn Item Qty Description

1 CPU (i7) Cash (8) MB
2 RAM 4 GB
3 HDD 1 TB
4 VGA 2 GB
5 Key Board
6 Mouse
7 Power Cables
8 Monitor 24 inch
1 Used in the main CPU to manipulate processes
3 As Random Access Memory to Applications
1 As a storage media to database & system files
1 Used to easy display contents fast
1 To write texts and commands and codes
1 Used in easy handle interfaces and icons
2 To supply the devices with AC power
1 To view the contents manipulated by CPU

Figure (24) Server components

46
 3.3 Software environment

We also covered some general needs to keep on the proper environment for good
system performance. There are certain operating systems that been made especially for
our situation for best performance we should put the “Windows server” operating
system any version that available on Microsoft official web site. In addition, there are
some programs needed essentially for supporting the server performance. Like the
following:-

➢ The operating system “Windows Server 2008” should have:-

- “Apache” or any equivalent application that do the same task.
- “MYSQL” database management system software.
- “PHP” package to enable the PHP codes runs well.
- “PHPMyadmin” package works as admin database control panel.
- .Net Framework software to enable the programs runs sufficiently.

➢ Used programing languages and programs

- HTML: (Hypertext Markup Language) is the main markup language for creating
web pages structures and other information that can be displayed in a web
browser. HTML is the "hidden" code that helps us communicate with others on
the World Wide Web (WWW). All Web pages all over the world contains HTML.

- PHP: (Hypertext Preprocessor language) is a server scripting language, and is a

powerful tool for making dynamic and interactive Web pages quickly. PHP is a
widely used, free, and efficient alternative to competitors such as Microsoft's
ASP. It is especially suited for web development and can be embedded into
HTML.

47
 - CSS: (Cascading Style Sheets) is a style sheet language used for describing the
look and formatting of a document written in a markup language. In other
words, it defines layout of HTML documents. For example, CSS covers fonts,
colors, margins, lines, height, width, background images, advanced positions and
many other things. It saves a lot of work and time.

- APPSERV: is a web server application notable for playing a key role in the initial
growth of the World Wide Web. It is the world's most popular Web server (HTTP
server). It can make you do all your work on your personal PC without the need
of a server to program and test your codes on it. It contains needed applications
like (Apache, MySQL, PHP and PHPMyadmin).

- MYSQL: MySQL is the world's most popular open source database used on the
web. Basically, a MySQL database allows you to create a relational database
structure on a web-server somewhere in order to store data or automate
procedures. If you think of it in comparison to Microsoft Access, MySQL is what
holds all of your tables, PHP acts as your queries (among other things), and your
forms are basically web pages with fields in them.

- PHOTOSHOP: it is a sophisticated image manipulating program has been

developed and manufactured by Adobe Systems. It is one of the most famous
and widely used tools of the trade. It has features include the ability to crop,
balance colors and tones, and format pictures.

- DREAMWEAVER: Adobe Dreamweaver is a site building and publishing tool

appropriate for intermediate to advanced users that allows developers to create
and edit web pages and applications using a graphical interface and built-in
advanced design and coding features. This software was originally created by
Macromedia but rights to produce it were later sold to Adobe Systems.

3.4 Conclusion

48
 The via-discussed subjects contains the main requirements and considerations
before designing the proposed system. It is simply the programs needed and tools to
make best environment for system well working without any malfunctions. It is a
pavement to plan for the design phase and execute it.

(Chapter 4)
System Design

49
 4.1 Introduction

The design phase is a fundamental step for the realization of any project. It
facilitates the information system and achieves the implementation of the base and
given treatment. Thereafter, we should seek the means and tools as possible to develop
the application.

4.2 Class Description

1. “Advice” table

It contains (4) attributes:-

2. “Message” table

It contains (4) attributes:-

50
3. “Category” table

It contains (4) attributes:-

4. “Coach” table

It contains (8) attributes:-

It also contains some functions:-

5. “Exercise” table

It contains (4) attributes:-

6. “Product” table

It contains (6) attributes:-

51
7. “Administrator” table

It contains (4) attributes:-

It also contains some functions:-

8. “Subscribed Customer” table

It contains (9) attributes:-

52
 It also contains some functions:-

9. “Order” table

It contains (8) attributes:-

10. “Customer” table

It contains (9) attributes:-

53
 It also contains some functions

4.3 Class Diagram

A class diagram is an illustration of the relationships and source code dependencies

among classes in the Unified Modeling Language (UML). In this context, a class defines
the methods and variables in an object, which is a specific entity in a program or the
unit of code representing that entity. Class diagrams are useful in all forms of object-
oriented programming (OOP).

54
55
56
 Figure (25) Class
Diagram

4.4 Conclusion

57
 Systems design is the process of defining the architecture, modules, interfaces, and
data for a system to satisfy specified requirements. Systems design could be seen as the
application of systems theory to product development. The following is the system
design phase that is show the product structure and interfaces prototyped.

58
 Conclusion and Perspective

The online sporting club system is an awesome method to let people so their
everyday exercises without the need to go to sporting clubs or centers that may be with
a big benefit on reducing the big subscription fees of current sporting clubs besides
giving the users the chance to practice their exercises anytime in their homes with less
efforts as possible. The system is a great edition to make a smart life for people and
paves a way to be in a more civilized society.

59