Club Management System 1

8/2/2019 Club Management System 1

1/71

CLUB MANAGEMENT SYSTEM

BUZY (Baroda United Zoroastrian Youth) is one of the primeorganizations (Club) in the Heart of Vadodara City. They areoffering various Club Activity in the city to their esteemed clubmembers

Todays world is moving towards intense competition, wherein the Hospitality Industry is not an exception. The Managersare entailed to work towards new innovation and attract morebusiness and to provide excellent customer services. Theshifting of such market transformation and the growth in the

IT sector had aspired bringing in such a services as to fulfillthe optimum customer satisfaction.


2/71

It include below mentioned levels :-

The CLUB MANAGEMENT SYSTEM for BUZY issuch an effort to understand the functioning of the

Club Management in its best possible manner.Membership Details

The Hall Description

The Facility Description

Sports Details

Event Details

Sub Event Details

Member Event DetailsThe Club Management System is a utility of theManagement Club to facilitate the basic services &facilities by the management.


3/71

Objectives

The primary objective of the Club Management System is to make more user-friendly system. Apart from this, the system entails more objectives with a viewof following perspective.

Functionality Objective: The system works best in its user-friendly environmentat a level entailed to the user requirement.

Organizational Objective: To organize the role of Club Management Systemthrough Systems in brings about association of the service thus offered.

Time Management Objective: To give utmost importance to the duration ofwork to be done within a specified time limit.

Personal objective: To assist employees in achieving their personal goals atleast insofar as these goals enhance the individuals contribution to theorganization.

Objective of Accuracy: To deliver accurate and precise data with due care

taken at the data level.Objective of Security: With the help of password and user rights facility one canbe sure to protect the data or abstract the data.


4/71

DATA FLOW DIAGRAM


5/71

1.1 Membership Type Process

1.3 Membership Details Process

1.5 Members Sports Process

1.9 Event Master Process

1.2 Personal Details Process

1.4 Sports Master Process

1.6 Hall Master Process

1.7 Facility Master Process

1.8 Facility Transaction Process

1.10 Sub-Event Master Process

User/Member

User/Member

User/Employee

User/Employee

User/Member

1.11 Master Event Process

2nd Lavel DFD


6/71

USER

Event Master

Event Master

AddRecord/Process

Request to Add

Get DataFrom User

ValidateData

Validate Name

Is ValidData

SaveProcess

Save All DetailsExcept Event

Type ID

Conformationto User

Add Event Master


7/71

USER

Hall TypeMaster

Hall TypeMaster

AddRecord/Process

Get DataFrom User

ValidateData

Validate Name

Is ValidData

SaveProcess

Save All DetailsExcept Hall

Type ID

Conformationto User

ADD HALL PROCESS

Request to Add


8/71

USER

MembershipType MasterMembership

Type Master

FindRecord

/Process

Request to Modifyby Passing a Valid

Membership Type ID

Pass the Membership

Type ID

SaveData

Conformationto User

MODIFY MEMBERSHIP PROCESS

Get DataProcess

RequestedData Found

ModifyDataValidate

Data

Get Data andPresent it to

Presentation Layer

Validate theModified Name

Requestto Save


9/71

USER

Personal

Master

PersonalMaster

FindRecord

/Process


Membership ID

Pass the Membership

ID

SaveData

Conformationto User

MODIFY PERSONAL PROCESS

Get Data

Process

RequestedData Found

ModifyDataValidate

Data


Presentation Layer

Validate theModify Name

Request toSave


10/71

USER

MembershipType Master

MembershipType Master

AddRecord/

Process Get DataFrom User

Validate

Data

Validate Name

Is ValidData

SaveProcess

Save All DetailsExcept Membership

Type ID

Conformationto User

CREATE MEMBERSHIP PROCESS

Request to Add


11/71

USER

Facility

TypeMaster

FacilityType

Master

AddRecord/

Process

Request to Add

Get DataFrom User

ValidateData

Validate Name

Is Valid

DataSave

Process

Save All Details

Except FacilityType ID

Conformationto User

CREATE FACILITY PROCESS


12/71

USER

FacilityMasterFacility

Master

FindRecord

/Process


Facility ID

Pass theFacility

ID

SaveData

Conformationto User

MODIFY FACILITY PROCESS

Get DataProcess

RequestedData Found

ModifyDataValidate

Data


Presentation Layer


Requestto Save


13/71

USER

EventMaster

Event Type

Master

Find

Record/Process


Event Type ID

Pass the Event

ID

SaveData

Conformationto User

MODIFY EVENT PROCESS

Get DataProcess

RequestedData Found

ModifyDataValidate

Data


Presentation layer

Validate theModify Name

Requestto Save


14/71

USER

HallMasterHall

Master

FindRecord

/Process

Pass the HallID

SaveData

Conformationto User

MODIFY HALL PROCESS

Get DataProcess

RequestedData Found

ModifyDataValidate

Data

Get data andPresent it to

Presentation Layer


Requestto Save


Facility ID


15/71

USER

SportsMasterSports

Master

Find

Record/Process Pass the Sports

ID

SaveData

Conformationto User

MODIFY SPORTS PROCESS

Get DataProcess

RequestedData Found

ModifyData

ValidateData


Presentation Layer


Requestto Save


Sports ID


16/71

E R Diagram


17/71


18/71

Data Model


19/71


20/71

A Complete Structure of the Program

Number of Modules

MODULES / FORMS

Personal details: it will allow adding /modifying personal details like first, middle and last name,address, phone number etc.

Membership type: it will allow adding /modifying member type id, membership name the priceincurred, number of years of membership, special price and discounts if any.

Membership details: this would allow entering sub-membership id, member type id, final amountand remarks

Sport master: this would allow add/modify assenting sport id. Name of the sport, type of thesport i.e. it is indoor or out door, any equipments available.

Hall master: it will allow add/modify hall id., name of the hall and the type of hall, its chargesand discount.

Facility master: it would allow add/modify the details of facility id, name of the facility, the priceavailed for that facility and discount.

Event master: it would add/modify the detail of event id, name of the event, the starting and theending date of the event.

Sub-event master: it would allow add/modify the detail of the sub-event id, would call the eventid, the date of the event, the price insert of the event, the time of the event and description.

Member event: it would allow add/modify the details of the event id, would called the event id,the date of the event, the price inserted of the event, the time of the event and the description.

Member sports detail: it would allow inputting the sub-membership and sport details and relation

them.


21/71

1.Data Structure

MEMBERSHIP TYPE MASTER

FIELD

NAMEDATA TYPE WIDTH

CONSTRAIN

TSREMARKS

Member

type idVarchar 8 Primary key

Display the

member id

Membership

nameVarchar 15 Not-null

Display the

member name

Price Numeric 8 >=0Display the

membership price

No. of years Numeric 2 >=0

Mention the no. of

years of

membershipMembership

typeVarchar 10 >=0 Life long years

Special

priceNumeric 8 >=0 Special offer if any

Discount Numeric 2 >=0 Mention discount

PERSONAL DETAILS


22/71

PERSONAL DETAILSFIELD NAME DATA TYPE WIDTH CONSTRAINTS REMARK

Membership id Varchar 8 Primary key Display the membership id

First name Varchar 15 Not-nullMention the first name of the

member

Middle name Varchar 15 Not-nullMention the middle the

member

Last name Varchar 15 Not-nullMention the last name of the

member

Membership date Date Time 9 Not-nullDisplay membership issued

date

Address 1 Varchar 100 Display the first address

Address 2 Varchar 100 Display the second address

City Varchar 20 Not-null Display the city name

State Varchar 20 Not-null Display the state name

Pin code Numeric 08 Not-nullDisplay the code name of the

city

Phone(m) Numeric 15Display the mobile no. the

member

Phone (r) Numeric 15Display the residence no. of

memberE-mail id Varchar 20 Dis la the e-mail id


23/71

Membership Detail

FIELD NAME DATA TYPE WIDTH CONSTRAINTS REMARK

Sub

membership

id

Varchar 8 Primary keyDisplay the sub

member id

Membership

idVarchar 8 Foreign key

Display the member

id

Member type


Display member type

id

Final amount Numeric 10 >=0Display the final

amount

Remark Varchar 100 Display remark


24/71

Sports master


Sport id Varchar 8 Primary key Display the sport id

Sport name Varchar 20 Not NullDisplay the sport

name

Sport type Varchar 10 Not Null Display type of sport

Equipment

availableLogical 1 Y/N

Display equipment

available

Charges Numeric 6 >=0Display charges for

sport


25/71


Sub membership


Display the sub member

id

Sport id Varchar 8 Foreign key Display the sport id

Annual amount Numeric 8 >=0Display the annual

amount

Guest charges Numeric 5 >=0 Display the guest charges

Member sport


26/71

Hall master


Hall id Varchar 8 Primary key Display the hall id

Hall name Varchar 15 Not-null Display the hall name

Hall type Varchar 15 Not-null Display type of hall

Hall charges Numeric 8 >=0Display the hall

charges

Discount Numeric 2 >=0Display the discountof the hall


27/71

Facility master


Facility id Varchar 8 Primary key Display the Facility id

Facility name Varchar 20 Not-nullDisplay the Facility

name

Facility price Numeric 10 >=0Display the facility

price

Discount Numeric 10 >=0Display the discount

on facility


28/71

Hall facility transaction


Hall id Varchar 8 foreign key Display the hall id

Facility id Varchar 8 foreign key Display the Facility id

Here Hall_Id & Facility_Id concatenated Primary Key


29/71

Event master


Event id Varchar 8 Primary key Display the event id

Event name Varchar 20 Not-null Display the event name

From date Date time 9 Not NullDisplay the starting

date of the event

To date Date time 9 Not Null


30/71

Sub-event master


Sub-event id Varchar 20 Primary key Display the sub event id

Event id Varchar 20 Foreign key Display the event id

Event date Date time 9 Not Null Display the event date

Event price Numeric 10 Not-null Display the event price

Event time Date time 9 Not Null Display the event time

Description Varchar 100 Remarks if any


31/71

Member event


Master-event id Varchar 8 Primary keyDisplay the master

event id

Sub Eventmaster id

Varchar 8 Foreign key Display the subevent master id

Sub master id Varchar 8 Foreign keyDisplay the sub

member date

Price Numeric 8 >=0Display the price of

the event

Total guest Numeric 4 >=0Display the total no

of guest

Total guest

priceNumeric 10 >=0

Display the total

guest price


32/71

Process Logic


33/71

EVENT MASTER

Start

Stop

Is Add

Input EventID

Open EventMaster File and

Search for ID

Is EOF=False?

Read AllRelevant Details

IncrementEvent ID &Generate

New BlankRecord

InputEvent ID,

EventDetails

Store EventDetails

Yes

No

Yes

No

Yes

Checks forValidation


34/71

HALL FACILITY TRANSACTION- MODIFY

Start

Stop

Input HallID

Open Hall FacilityTransaction and

Check fro ID

Yes

No

Store theData

Is EOF=False?

Input All the Data

Validate the Data


35/71

MEMBER EVENT

Start

Stop

Is Add

Input MasterEvent ID

Open MasterEvent File and

Search for ID

Is EOF=False?


IncrementMaster Event ID& Generate New

Blank Record

InputMaster

Event ID,Member

Event Details

Store MasterEvent Details

Yes

No

Yes

No

Yes

Checks for

Validation


36/71

MEMBER SPORTS - ADD

Start

Stop

Input Sub

Membership ID

Open SubMembershipMaster and

Search for ID

Yes

No

Is EOF=False

InputSports ID

Open Sports IDAnd Check for

Record

Is EOF=False

Store TheResult into

DataTransaction

MEMBERSHIPDETAILS


37/71

MEMBERSHIP DETAILS

Start

Stop

Is Add

Input Sub-Membership

ID

Open MembershipDetails File andSearch for ID

Is EOF=False?


IncrementCounterProcess

Is BOF= False ?

InputSub-

Member ID,Membership

Details

StoreMembership

Details

Yes

No

Yes

No

Yes No

ChecksValidation


38/71

PERSONAL DETAILS

Start

Stop

Is Add

InputMembership

ID

Open PersonalDetails File and

Search for ID

Is EOF=False?


IncrementMembership ID& GenerateNew Blank

Record

InputMember ID,

PersonalDetails

Store Personal

Details

Yes

No

Yes

No


39/71


40/71

FACILITY MASTER

Start

Stop

Is Add

Input FacilityID

Open FacilityMaster File andSearch for ID

Is EOF=False?


IncrementFacility ID

and Generate

Blank Record

InputFacility ID,

FacilityDetails

Store FacilityDetails

Yes

No

Yes

No

Checks for

Validation


41/71

HALL FACILITYTRANSACTION - MODIFY

Start

Stop

Input Hall

ID

Open Hall FacilityTransaction and

Check fro ID

Yes

No

Store theData

Is EOF=False?

Input All the Data

Validate the Data


42/71

HALL MASTER

Start

Stop

Is Add

Input Hall ID

Open Hall MasterFile and Search for

ID

Is EOF=False?


IncrementHall ID &

GenerateNew Blank

Record

InputHall ID, Hall

Details

Store HallDetails

Yes

No

Yes

No


MEMBER SPORTS


43/71

Start

Stop

Is Add

Input SubEvent ID

Open Sub EventMaster File andSearch for ID

Is EOF=False?


IncrementCounterProcess

Is BOF= False ?

InputSub EventID, EventDetails

Store SubEvent Details

Yes

No

Yes

No

Yes No

ChecksValidation


44/71

MEMBER SPORTS - MODIFY

Start

Stop

Input Sub

MembershipID

Open SubMembership

Transaction andCheck for Record

Yes

No

Store theData

Is EOF=False?

Input All the Data

Validate the Data

MEMBERSHIP TYPE


45/71

MASTER PROCESS

Start

Stop

Is Add

InputMemberType ID

Open MembershipType Master File

and Search for ID

Is EOF=False?


IncrementMembership

Type ID &Generate NewBlank Record

InputMemberType ID,MemberName

StoreMembership

Details

Yes

No

Yes

No


SPORTS MASTER


46/71

Start

Stop

Is Add

Input SportsID

Open SportsMaster File and

Search for ID

Is EOF=False?


IncrementSports ID &Generate

New Blank

Record

InputSports ID,

SportsDetails

Store SportsDetails

Yes

No

Yes

No


T f O t t / R t


47/71

Types of Output / Report

GenerationAs the output of this project, following types of report will begenerated.

Membership Type Report

Members Details Report

Members General ReportSports Type Report

Facility Report

Event Report

Sub Event Report

Members Event ReportMembers Sports Report

And More Reports can add if Customer Required


48/71

Validation Check

Case: Upper case/Lower case auto checking in application itself contained.

Not Null: All fields that are mapped to Primary key / Foreign Key / NOT NULL ,will be validate so that the data is not stores as NULL in the required fields withabove mentioned constraints.

Primary Keys: Primary keys are the KEY column, which makes then Auto-Incremented field value if its Numeric or partially numeric.

Alphabetic: All text fields that take inputs as Alphabetic will be validated, so thatonly alphabets are taken as input values.

Numeric: All text fields that take Integers, as inputs will be validated so, that theonly numerals are allowed.

Decimal Places: More than two decimal place is not allowed.

Date Time:All Date field values and Time field values are stores as dd-mm-yyyy format and hh: mm respectively and will be consistent through out thesystem.

Field Length: All text fields max length, are set according to the defined in to

Databases fields, so that the characters does not exceed themax. Length.

Duplication: Duplication checks for key field for the entire Database as well asDuplication of Employee in accessing record must not be allowed.

Data Stores in the reference table / column is validated through a Visual BasicComponent like Combo Box, List Views etc., which makes the Foreign Key Valueconsistent and sure to be present in the Parent table.


49/71

Tools Language / Platform to be used

Front End : VB.Net

Back End : SQL-Server 2000 Report Tool : Crystal Reports

Other Tools : Microsoft VISIO (UML

modeling) MS - Word.


50/71

Future scope of the project

Future Scope of Club Management System ManagementSystem:In future we can recruit the Club Management System Member throughInternet. This means we can get the members from any place. Theseworlds facilitate reluctant members to enroll through net in asophisticated & user-friendly way. We could put together the AccountingSystem and HRMS with Club Management System so this will be a

complete system. More over Inventory management could beaccommodated along with existing one to connect with the inventorylevels of the, this would allow smooth communication between thePurchase Department and the Inventory Department. The masses canalso avail the On-Line registration facility and enroll themselves through

easy access facility. We could add the modules of different socialresponsibility initiatives of the club. Sustainable energy projects can beintegrated to our future scope for this project. Culture, arts andrecreation as well as environment and conservation can be includingenhancing this project. Flexibility can be provided to enhance the scopeof the Club Management System.


51/71

Screen Shot

LOGIN FORM


52/71

MEMBERSHIP TYPE MASTER


53/71

PERSONAL DETAIL


54/71

MEMBERSHIP DETAIL


55/71

SPORTS MASTER


56/71

MEMBER SPORT


57/71

HALL MASTER


58/71

FACILITY MASTER


59/71

EVENT MASTER


60/71

SUB EVENT MASTER


61/71

MEMBER EVENT


62/71

HALL FACILITY TRANSACTION

REPORT GENERATION


63/71

REPORT GENERATION1.EVENT REPORT


64/71

2.FACILITY REPORT


65/71

3.SPORT REPORT


66/71

4.HALL REPORT


67/71

5.MEMBERSHIP REPORT

SECURITY FORMS


68/71

SECURITY FORMSLogin Form


69/71

ADD USER


70/71

DELETE USER


71/71

CHANGE PASSWORD

Club Management System 1

Documents

Transcript of Club Management System 1