CRICKET CLUB MANAGEMENT SYSTEM

PROJECT REPORT

Submitted by

LUTHFAN PP

KMC20MCA2014

GUIDE

RESMI SR

to

the APJ Abdul Kalam Technological University in partial fulfillment of the

requirements for the award of the Degree

of

Master of Computer Applications

Department Of Management Studies & Computer Applications

KMCT College of Engineering

Kallanthode, NITC P.O, Kozhikode-673601

”Terrific Hitters Cricket Club” located at Kakkodi, Kozhikode is a website system is

completely automated. The proposed system allows the members to book ground for var-

ious days, request for club membership and register for the various training batches. Less

effort is required for maintaining the database of club using this software. Margin of error

will be reduced and regulating members will be a breeze by using this software. The main

aim to reduce the human effort at the club and over come the limitations. The end users

can register for membership, book ground, register for different training batches, receive

notices and view images related to the cricket from the management.

i
 Contents

Chapter 1 INTRODUCTION 2

1.1 General Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.2 Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2 SYSTEM ANALYSIS 4

2.1 Existing system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.2 Proposed system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.3 Module Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.3.1 Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.3.2 User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.4 Feasibility study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.4.1 Operational Feasibility . . . . . . . . . . . . . . . . . . . . . . . . 13

2.4.2 Technical Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.4.3 Economic Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.5 System Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.5.1 Developer Requirement . . . . . . . . . . . . . . . . . . . . . . . 15

2.5.2 User Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . 15

ii
 2.6 Actors and Their Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.6.1 Club Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.6.2 User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 3 METHODOLOGY 18

3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.2 Uml Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.2.1 Use case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.2.2 Activity Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.3 User Story . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.4 Product Backlog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.5 Project plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3.6 Database Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.6.1 Registration of member . . . . . . . . . . . . . . . . . . . . . . . . 29

3.6.2 Batch Registration . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.6.3 Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.6.4 Ground Booking . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.6.5 Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.6.6 Upcoming fixture . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

3.6.7 Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.7 UI Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

3.7.1 Admin Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

3.7.2 Member Registration . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.7.3 Member Login Page . . . . . . . . . . . . . . . . . . . . . . . . . 39

iii
3.7.4 Admin Homepage . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.7.5 Batch Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.7.6 Ground Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3.7.7 Post Notification Page . . . . . . . . . . . . . . . . . . . . . . . . 43

3.7.8 Post Fixture Page . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.7.9 Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3.7.10 Post Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3.7.11 Member Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.7.12 Member Home Page . . . . . . . . . . . . . . . . . . . . . . . . . 49

3.7.13 Batch Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

3.7.14 Ground Booking Page . . . . . . . . . . . . . . . . . . . . . . . . 51

3.7.15 Notification Page . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3.7.16 Upcoming Fixture Page . . . . . . . . . . . . . . . . . . . . . . . 53

3.7.17 Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

3.7.18 Post Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

3.7.19 View Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

1
 Chapter 1

INTRODUCTION

The Terrific Hitters Cricket club management project is designed with the motive of

managing a cricket club. This software system consists of various online booking and

management functionaries needed by a cricket club. It provides various options like ground

bookings, member registrations, notice posting, member registration, batch registration and

more. This software system assures efficient management and maintains the functioning

on a cricket club.

1.1 General Background

The Terrific Hitters Cricket Club Management is to manage the details of Cricket, train-

ing, players, batches, Schedules. The project is totally built at administrative end and thus

only the administrator is guaranteed the access. The purpose of the project is to build an

application program to reduce the manual work for managing the Cricket, batches, players.

It tracks all the details about the Players, Batches, Schedules.

2
1.2 Objective

Players are the backbone of every game. Training players well is something necessary

for the improvement of the playing skill. The Terrific Hitters Cricket Club gives complete

freedom to the players to make any shot with full confident , and gives an effective more

experience in the ground. The achievements done by the register and get the Terrific Hit-

ters club information through website in the proposed system no need to meet the club

member all the information are published in online. The players can register or login into

the website. Furthermore, online bookings decrease the standing time thanks to wait list

management features. And many members can book the slot at the same time.

3
 Chapter 2

SYSTEM ANALYSIS

2.1 Existing system

The existing system for a cricket club management system is done manually by a group

of members.If any of the members need to take membership in the club then they have to

visit the club by themselves and they have to fill a white paper form by giving their details.

And the the club manager will verify the details that the member have wrote in the form.

If the member got the admission in the club then he or she should also have to fill another

form which coloured pink for the batch registration. There are two type of batches, that

are regular and vacation batches. If there is anything that is any news notifications that

the club manager need inform the club members then he post all the news notifications in

the physical board in the front of the club office. club managers should check the member

registration book to know the member details and their roles in the ground. It takes lot of

time consuming.

4
 If anyone need to book the ground then they need to go the club by themselves and

first they have to see the club manager and ask for him that they had come to book the

ground, and the club manager will inform them about the available slots for the ground.

Members does not know about the booking slots in advance, they only know when they

reach at the club by the club managers. Also members can book the ground by calling to

the club but in the case if the club manager are in the ground with the club members then

he cannot pickup the call. By reaching in the club and if there is no any slots vacant for

ground then the members should return without booking the ground and it become very

disappointment to the members. So there is only 50 percentage of chance for the getting

the slot because the members does not know about the available slots for the ground. They

only known by taking the effort by getting to the club.

Members does not know about the upcoming the fixtures of the club team, they have

to ask for the club manager or to the club team captain to know about the next match and

venue of the club team. And they will tell to the members whom all are ask to them about

the next fixtures.

5
2.2 Proposed system

The proposed system is computerize which helps in maintaining the record easily. The

System is cost effective. The achievements done by the register and get the club infor-

mation through website in the proposed system no need to meet the club member all the

information are published in online. The players can register or login into the website .

The members can register to the club through the website by providing name, username as

email, password, member type, date of birth, gender, place, pin code, contact number.After

the member registration, the members should do the batch registration by providing name,

email id, contact number, batch type, member type, batch timing, for various batches, that

is regular or vacation batches.

The next is the ground booking for the members, members can book the ground by

looking the available slots present at that time through the website. The member should

provide name, email id, contact number and select the available slots at that time. After

the ground booking completed by the members, they can see the amount to pay to club for

the booking of the ground and they should give these amount to the club manager after the

usage of ground at club. If one member select a slot then that slot be coloured to red and no

other member can book the same slot, they can go for another slot that coloured in green,

which means that the green coloured one are the available slots for the current date.

The next As the proposed system is portable it can be accessed anywhere irrespective of

time. All of this information will be stored in the database. Next is the entry of the players.

All the news and notifications are posted in the website. And members can view the the

6
news or notifications. so the members can know the updated news in the club. The ground

date and time is saved in the database for further information. Members can also view the

upcoming fixtures of the club team. Members can also the view the images in the gallery

posted by the club manager.

Club manager can login into the website using username and password. Club manager

have the overall control over the website. Club manager can post notifications and news for

the club members. The club manager can able to see the club members list and can able to

see various training batches. Club manager can post the images related to the cricket in the

website.

Main activities of admin are:

Login:

Admin need to login to the application by the already given username and pass-

word.

Post notifications:

After login to this application admin is redirected to the home page.And admin can

post notifications and news.

Check the member details:

Admin can check the member details, who are registered to the club.

7
Create batch and view batches:

Club manager need to create the batches, i.e regular batch or vacation batches

and After the admin login, club manager can view and check the various training

batches.

Add/view slots for ground booking:

Club manager can add the slots for ground bookings and Club manager can view

the ground booking details done by the members.

Post images and upcoming fixtures:

Club manager can add various images related to the cricket and can add upcoming

fixtures of the club team.

View/Respond feedback:

Admin can view the feedback by the club members and respond to the feedback.

8
 View report:

Admin can view the report of the various batches that members are registered,

ground booking amount.

Main activities of club members are:

Registration:

Club members can register to the website. The members can register to the club

through the website by providing name, username as email, password, member

type, date of birth, gender, place, pin code, contact number.

Login:

After the club member registration, the club member should login into the website

by the username and password. After the login the members can access available

facilities in the website.

Batch Registration:

After the member registration, the members should do the batch registration by

providing name, email id, contact number, batch type, member type, batch timing,

for various batches, that is regular or vacation batches. And members can see the

fees of various batches at the time of batch registration.

9
Ground booking:

After the member login, members can book the ground by looking the available

slots present at that time through the website. The member should provide name,

email id, contact number and select the available slots at that time. After the ground

booking completed by the members, they can see the amount to pay to club for the

booking of the ground and they should give these amount to the club manager after

the usage of ground at club. If one member select a slot then that slot be coloured

to red and no other member can book the same slot, they can go for another slot

that coloured in green, which means that the green coloured one are the available

slots for the current date. At the time of slot booking, the members can see the

price of slots per hour in the batch registration page.

View notifications or news:

Club members can view updated news or notifications posted by the club manager.

View upcoming fixtures:

Club members can view the upcoming fixtures of the club team.

View images:

Members can view the images in the gallery that are posted by the club managers.

Give the feedback:

Members can give any feedback about anything related to the club or trainers

10
2.3 Module Description

2.3.1 Admin

The managerial functions are carried out by the Admin. Admin can approve the book-

ings done by end users, send notices to the online notice board, check different members

of the club and the users registered for various training batches.

• Check member details

• Post notifications

• Batch create

• Add ground booking slot

• View ground booking details

• Post upcoming fixtures

• Check the various batch

• Post images

• View/Respond to the feedback

• view report

2.3.2 User

The end users can register for membership, book ground, register for different training

batches and receive notices from the management.

• View notifications

11
• Book for the ground slot

• Register for vacation or regular batch

• View the upcoming fixtures of the club team

• View images in the gallery

• Give the feedback

12
2.4 Feasibility study

A feasibility study is a high-level capsule version of the entire System analysis and

Design Process. The study begins by classifying the problem definition. Feasibility is to

determine if it’s worth doing. Once an acceptance problem definition has been generated,

the analyst develops a logical model of the system. A search for alternatives is analyzed

carefully. There are 3 parts in feasibility study. They are operational,technical and eco-

nomic.

2.4.1 Operational Feasibility

operations are mainly concerned and are completely depended on he users. The system

is developed by giving prime importance to the ease with which the end users can operate

on the system. Any person or user who can access the system through any web browsers

such as chrome, Mozilla, etc from anywhere which already present in our computer system

or mobile devices. The web application is able to use conveniently without the help of

another person and becomes able to use the services of the web application with more ease.

The project has been developed in such a way that that it becomes very easy even for a

person with little computer knowledge to operate it. This is very user friendly and does not

require any technical person to operate. Thus the project is even operational feasible.

2.4.2 Technical Feasibility

Technical feasibility if it is possible to complete the project with the current technology.

The web application is going to use many programming languages in order to ensure a

good user experience for the end user, as well as adopting good coding practices for the

13
developer. The structure of the web application will consist of a back end and front end.

The back-end will be implemented using MySQL , PHP. The front-end should be completed

using HTML, CSS . The proposed system is support with the existing computer system for

admin side and members can access the system via a computer system. Thus cricket club

management system is technically feasible.

2.4.3 Economic Feasibility

The proposed system is economically feasible. Economic feasibility is the measure of

the cost-effectiveness of a project, which is often called cost-benefit analysis. The tech-

nique of cost benefit analysis is often used a basis for assessing economic feasibility. Eco-

nomic feasibility determines whether the proposed system is capable of generating for the

club. It includes quantification and identification of all the benefits expected. This assess-

ment typically involves a cost/benefits analysis. This web application is free and available

on internet.

14
2.5 System Environment

2.5.1 Developer Requirement

3.5.1.1 Hardware Requirement

•Processor : Intel Core i3

•RAM : 4GB

•Storage : 500GB Hard disk

3.5.1.2 Software Requirement

• Operating system : Windows 10

• Front end : HTML, CSS

• Back end : PHP, MySQL

• IDE : Visual Studio Code

• Web browser : Internet Explorer/Google chrome/Firefox

2.5.2 User Requirement

• Computer/Laptop

• Any OS with updated browser

• Stable internet access

15
2.6 Actors and Their Roles

2.6.1 Club Manager

Club manager in this project is responsible for managing this web application. For club

manager,web application is designed. various features and services are:

• Login

• Post news and notification

• Create batch

• View and manage members

• View the various batches

• Add slots for ground booking

• View the ground booking details

• Add upcoming fixtures

• Post images

• View/Respond to feedback

• View report

2.6.2 User

To continue as users,they must register to the website with their valid name,phone num-

ber etc. Main features to users involves:

• View notifications or news

16
• Book the ground slot

• Register for vacation or regular batch

• View upcoming fixtures

• View images in the gallery

• Give feedback

17
 Chapter 3

METHODOLOGY

3.1 Introduction

This project follows Agile methodology. Agile software development comprises vari-

ous approaches to software development under which requirements and solutions evolve

through the collaborative effort of self organizing and cross-sectional teams and their cus-

tomers/end users. It advocates adaptive planning, evolutionary development, early delivery

and continuous improvement and it encourage rapid and flexible response to change. It’s

a process for managing a project that involves constant collaboration and working in itera-

tions. Today, the word Agile can refer to these values and the frameworks for implement-

ing them, including Scrum, Kanban, Extreme Programming (XP), and Adaptive Project

Framework (APF). One thing that separates Agile from other approaches to software de-

velopment is the focus on the people doing the work and how they work together. Solutions

evolve through collaboration between self-organizing cross-functional teams utilizing the

appropriate practices for their context.

18
3.2 Uml Diagrams

3.2.1 Use case Diagram

Figure 3.1: Use case Diagram

19
3.2.2 Activity Diagrams

Figure 3.2: Admin activity

20
Figure 3.3: User activity

21
3.3 User Story

User story As a (Type of I want to (Per- So that I can (Achieve

ID Users) form some task) some goal)

1 Admin Homepage Can navigate entire

pages of system

2 Admin Login Access the system

3 Admin Create/view Create and view various

batches batches

4 Admin Create/view/update Can create, view and

slots for ground update slots for ground

booking

5 Member Homepage Can navigate entire

pages of system

6 Member Registration Access the system

7 Member Login Access the system

8 Member View and batch Can register for various

registration batches

22
User story As a (Type of I want to (Per- So that I can (Achieve

ID Users) form some task) some goal)

9 Member View and book Can view and book

available slots for available ground slot

ground

10 Admin Check member Can check various

details members

11 Admin Post notifications Can post notifications

for members

12 Member View notifica- View notifications

tions posted by admin

13 Admin Create/update up- Can create and update

coming fixtures upcoming team fixtures

14 Member View upcoming Can view upcoming

fixtures team fixtures posted by

admin

15 Admin Add and update Add and update images

images related to cricket

16 Member View images Can view images

posted by admin

17 Member Post feedback Give feedback to admin

18 Admin View and respond Can view and respond

feedback to the feedback given

by members

19 Admin View23
report Type of batch mem-

bers, ground booking

amount
3.4 Product Backlog

USER PRIORITY SIZE SPRINT STATUS RELEASE RELEASE

STORY (LOW,HIGH, (PLANNED, DATE GOAL

ID MEDIUM) PROGRESSED,

COMPLETED)

1 MEDIUM 10 1 planned 15/12/2021 Homepage of Ad-

min

2 MEDIUM 9 planned 16/12/2021 Login into system

3 MEDIUM 8 planned 19/12/2021 Create/view

batches

4 MEDIUM 10 planned 23/12/2021 create/view/update

ground slots

5 MEDIUM 10 planned 25/12/2021 Homepage of

member

24
USER PRIORITY SIZE SPRINT STATUS RELEASE RELEASE

STORY (LOW,HIGH, (PLANNED, DATE GOAL

ID MEDIUM) PROGRESSED,

COMPLETED)

6 MEDIUM 10 planned 27/12/2021 Member registra-

tion

7 MEDIUM 9 2 planned 30/12/2021 Member login

8 MEDIUM 9 planned 03/01/2022 view and batch

registration

9 HIGH 11 planned 06/01/2022 view and book

ground slot

10 HIGH 10 planned 09/01/2022 check member

details

25
USER PRIORITY SIZE SPRINT STATUS RELEASE RELEASE

STORY (LOW,HIGH, (PLANNED, DATE GOAL

ID MEDIUM) PROGRESSED,

COMPLETED)

11 MEDIUM 10 3 planned 10/01/2022 post notifications

12 MEDIUM 10 planned 16/01/2022 view notifications

13 MEDIUM 9 planned 19/01/2022 create/update fix-

tures

14 HIGH 9 planned 20/01/2022 view fixtures

15 MEDIUM 11 planned 22/01/2022 add/update im-

ages

26
USER PRIORITY SIZE SPRINT STATUS RELEASE RELEASE

STORY (LOW,HIGH, (PLANNED, DATE GOAL

ID MEDIUM) PROGRESSED,

COMPLETED)

16 HIGH 10 4 planned 24/01/2022 view images

17 MEDIUM 10 planned 26/01/2022 give feedback

18 MEDIUM 9 planned 29/01/2022 view/respond

feedback

19 HIGH 9 planned 04/02/2022 view report

27
3.5 Project plan

User Task name Start date End date Days Status Goal

story

ID

1 Sprint1 15/12/21 16/12/21 1 planned

2 Sprint1 16/12/21 19/12/21 2 planned

3 Sprint1 19/12/21 22/12/21 3 planned

4 Sprint1 22/10/21 23/10/21 1 planned

5 Sprint1 23/10/21 25/10/21 2 planned

6 Sprint2 25/12/21 27/12/21 2 planned

7 Sprint2 27/12/21 30/12/21 3 planned

8 Sprint2 30/12/21 03/01/22 4 planned

9 Sprint2 03/12/21 06/01/22 3 planned

10 Sprint2 06/12/21 09/01/22 2 planned

11 Sprint3 09/01/22 10/01/22 1 planned

12 Sprint3 11/01/22 16/01/22 5 planned

13 Sprint3 16/01/22 19/01/22 2 planned

14 Sprint3 19/01/22 20/01/22 1 planned

15 Sprint3 20/01/22 22/01/22 2 planned

16 Sprint4 22/01/22 24/01/22 2 planned

17 Sprint4 24/01/22 26/01/22 2 planned

18 Sprint4 26/01/22 29/01/22 3 planned

19 Sprint4 29/01/22 04/02/22 5 planned

28
3.6 Database Design

3.6.1 Registration of member

This is member registration table. This table includes details of user like name, email,

password, address, gender, phone no, dob and member type. Member can register by them-

selves.

29
No. Name Type Constraints Description

1 member id INT PRIMARY KEY Registration id of

member

2 member name VARCHAR(15) NOT NULL Full name of

member

3 email VARCHAR(10) NOT NULL Email id of mem-

ber

4 password VARCHAR(25) NOT NULL password of

member

5 address VARCHAR(50) NOT NULL address of mem-

ber

6 gender VARCHAR(25) NOT NULL Gender of mem-

ber

7 phone no VARCHAR(10) NOT NULL Phone number of

member

8 dob DATE NOT NULL DOB of member

9 member type VARCHAR(15) NOT NULL Type of member

Table 3.4.2 Registration of member

30
3.6.2 Batch Registration

This is batch registration table. Batch registration is done by member. It includes

batch id, member id, name and batch type.

No. Name Type Constraints Description

1 batch id INT PRIMARY KEY Batch id

2 member id INT FOREIGN KEY Id of member

3 member name VARCHAR(15) NOT NULL Full name of

member

4 batch type VARCHAR(10) NOT NULL Type of Batch

Table 3.4.2 Registration of batch table

31
3.6.3 Login

This is login table. This include user name, user type and password for login to this

application. Hotel owner, user and delivery boy can access his/her account by entering

username and password.

No. Name Type Constraints Description

1 login id INT PRIMARY KEY Login id of User

2 username VARCHAR(15) NOT NULL Name of User

3 password VARCHAR(8) NOT NULL Password of user

of User

4 usertype VARCHAR(13) NOT NULL Type of user

Table 3.4.1 Login table

3.6.4 Ground Booking

This is ground booking table. Ground booking are done by member. It contains

booking id, member id,member name, date and time.

32
No. Name Type Constraints Description

1 Booking id INT PRIMARY KEY Id of booking

2 Member id INT FOREIGN KEY Id of member

3 Member name VARCHAR(10) NOT NULL name of member

4 Date DATE NOT NULL Date of booking

8 Time DATETIME NOT NULL Time of booking

Table 3.4.2 Ground booking table

33
3.6.5 Notifications

This is notification table. It includes notification id and content.

No. Name Type Constraints Description

1 notification id INT PRIMARY KEY Id of notifications

2 content VARCHAR(50) NOT NULL Content of notifi-

cations

Table 3.4.2 Notification table

34
3.6.6 Upcoming fixture

This is upcoming fixture table. It includes match and date and time.

No. Name Type Constraints Description

1 Match VARCHAR(50) NOT NULL Match fixture

2 Date DATE NOT NULL Date of match

3 time DATETIME NOT NULL Time of match

Table 3.4.2 Upcoming fixture table

35
3.6.7 Feedback

This is feedback table. It includes feedback id, member id and content.

No. Name Type Constraints Description

1 Feedback id INT PRIMARY KEY Id of feedback

2 member id INT FOREIGN KEY id of member

3 content VARCHAR(100) NOT NULL Content of feed-

back

Table 3.4.2 Feedback table

36
3.7 UI Diagram

3.7.1 Admin Login

Through login page, Admin login to his web page. By entering username and pass-

word admin can enter into the web page.

Figure 3.4: Admin login page

37
3.7.2 Member Registration

Member registering to the system using basic details.

Figure 3.5: Member Registration page

38
3.7.3 Member Login Page

Member can login into his webpage by entering his username and password.

Figure 3.6: Member login page

39
3.7.4 Admin Homepage

Admin can manage the homepage by adding ground slots, send notifications, add

fixtures, post images, respond to feedback.

Figure 3.7: Admin Homepage

40
3.7.5 Batch Page

Admin can view the batch members and their batch type.

Figure 3.8: Batch page

41
3.7.6 Ground Slot

Admin can add and slots for ground booking, and also admin can view the the book-

ing details. It includes booking id, member id,member name, date and time.

Figure 3.9: Ground s lot

42
3.7.7 Post Notification Page

Admin can post notifications to members.

Figure 3.10: Post notification page

43
3.7.8 Post Fixture Page

Admin can post upcoming fixtures. It includes match team, date and time.

Figure 3.11: Post Fixture

44
3.7.9 Image

Admin can post and view images to members .

Figure 3.12: Image Page

45
3.7.10 Post Feedback

Admin can view and respond to the feedback given by members It includes feedback

id, member id and content.

46
 47

Figure 3.13: Feedback pages

Admin can check the member details that who are registered to the club. It includes

member id, member name, member type, dob, gender, address, pno.

Figure 3.14: Member details page

48
3.7.12 Member Home Page

Member can manage the home page. It includes create batch, ground booking, noti-

fication, fixtures, images and feedback.

Figure 3.15: Member Home Page

49
3.7.13 Batch Page

Member can register the batch. It includes batch id, member id, member name and

member type.

Figure 3.16: Batch page

50
3.7.14 Ground Booking Page

Member can view and book the available ground slot. It includes date and the number

slots.

Figure 3.17: Ground Booking Page

51
3.7.15 Notification Page

Member can view the notifications posted by the admin.

Figure 3.18: Notification page

52
3.7.16 Upcoming Fixture Page

Member can view the upcoming fixtures played between various teams.

Figure 3.19: Fixture page

53
3.7.17 Image

Member can view the images related to cricket posted by the admin.

Figure 3.20: Image page

54
3.7.18 Post Feedback

.Member can post feedback to admin. It includes feedback content.

Figure 3.21: Post Feedback page

55
3.7.19 View Report

Admin can view the report about the ground booking amount and count of member

in different types of batches.

Figure 3.22: Report page

56