Golf Management System

Golf Club Membership System Software Engineering DavidO' Connor t00130990
Page 1 of 42
Golf Club Membership System
Software Engineering: Catherine Woods
Submitted By: David O’ Connor (KCOMP_G_Y6)
Submitted on: 19th
December 2014

Page 2 of 42
Table of Contents
1. Introduction...............................................................................................................................4
2. Functional Requirements............................................................................................................5
3. User Requirements.....................................................................................................................6
3.1. The system performs rate management...............................................................................6
3.2. The system performs member administration......................................................................6
3.3. The system performs finance management..........................................................................6
3.4. The system will perform Golf Club administration................................................................6
4. System Requirements.................................................................................................................7
4.1. System Level Use Case.........................................................................................................7
4.2. Rates Management.............................................................................................................7
4.2.1. Create Member Type ....................................................................................................8
4.2.2. Change Member Type.................................................................................................10
4.3. Member Management......................................................................................................12
4.3.1. Register Member........................................................................................................12
4.3.2. Amend Member .........................................................................................................15
4.3.3. De-Register Member...................................................................................................17
4.3.4. List Members .............................................................................................................19
4.4. Finance Management........................................................................................................21
4.4.1. Issue Member Invoice.................................................................................................21
4.4.2. Issue Renewal Notice..................................................................................................23
4.4.3. Record Payment.........................................................................................................25
4.5. Admin...............................................................................................................................27
4.5.1. Income Analysis .........................................................................................................27
4.5.2. Member Analysis .......................................................................................................29
4.5.3. List Late Fees.............................................................................................................31
5. System Model...........................................................................................................................33
5.1. Data Flow Diagrams – Elements.........................................................................................33
5.2. Level-0 DFD.......................................................................................................................34
5.3. Level-1 DFD.......................................................................................................................35
5.4. Level-2 DFD – Process P1 ...................................................................................................36

Page 3 of 42
6. Data Model ..............................................................................................................................40
7. Database Schema .....................................................................................................................41
8. Program Specifications....................................................................Error! Bookmark not defined.
9. Conclusion................................................................................................................................42
10. References:.................................................................................Error! Bookmark not defined.

Page 4 of 42
1. Introduction
Thissystemwill allow agolf course tomanage theirday to dayactivitieswithregardto the management
of theirbusinesswithrespecttomembershipmanagementanddayto dayactivitiesof runninga
successful golf course.Thissystemwill allow the usertoregisternew memberswithinthe golf course
and manage theirmembershipsinaneffective manner.The systemshall store all informationrelatedto
each memberof the golf course theirmembershiptype,theirnextrenewaldate,etc.
The user will be able toaccessall informationaboutgolf course members

Page 5 of 42
2. FunctionalRequirements
Golf Club
Membership
System
Rates
Create Member
Type
Change
Member Type
Members
Register
Member
Amend Member
De-Register
Member
List Members
Finance
IssueMember
Invoice
IssueRenewal
Notice
Record Payment
Admin
IncomeAnalysis
Member
Analysis
List Late Fees

Page 6 of 42
3. User Requirements
The following user requirements have been identified for the system (Golf365):
3.1. Thesystemperforms ratemanagement
3.1.1. Golf365 will allow to create membership type
3.1.2. Golf365 will allow to change membership type
3.2. Thesystemperformsmemberadministration
3.2.1. Golf365 will allow the details of each new member to be recorded
3.2.2. Golf365 will allow a member’s details to be amended
3.2.3. Golf365 will allow the de-registration of a member
3.2.4. Golf365 will generate a member listing
3.3. Thesystemperforms financemanagement
3.3.1. Golf365 will issue invoices to members
3.3.2. Golf365 will allow to issue renewal notices to members
3.3.3. Golf365 will record membership payment transaction
3.4. Thesystemwill performGolfClubadministration
3.4.1. Golf365 will perform income analysis
3.4.2. Golf365 will perform member analysis
3.4.3. Golf365 will list late membership fees

Page 7 of 42
4. SystemRequirements
4.1. SystemLevelUseCase
4.2. Rates Management
The system has two essential requirements in relation to the management of rates data. The
creation of member types and the changing of member types.
Process Rates
Administrator
Manage
Members
Manage
Finance
Process Admin
Member

Page 8 of 42
4.2.1. Create Member Type
Details of all membership types are held in the system.
Use Case Name Create Member Type
Use Case Id 1
Priority 1
Source Management
Primary BusinessActor Administrator
Other ParticipatingActors
Description Thisfunctioncreatesa new membertype.
Preconditions
Trigger Administratorwishestocreate anew membertype.
Typical Scenario Actor Action System Response
Step 1: The Administratorinvokes
the create membertype function.
Step 3: The Staff memberenters
the requireddata:
 Title of membertype
 Description
 Fee
Step 4: The Staff memberconfirms
the membertype isto be created
Step 2: The systemdisplaysthe UI.
Step 5: The systemvalidatesthe
inputdata:
 All fieldare required
 Fee mustbe greaterthan
zero
Step 6: The systemstoresthe new
membertype inthe Memberfile.
Step 7: The systemdisplaysa
confirmationmessage.
Step 8: The systemresetsthe UI.
Create
Member Type
Administrator Validate
Member Type
<<includes>>

Page 9 of 42
Alternate Scenarios Actor Action System Response
A requiredfieldisnot
entered
Step 5: A required fieldisnot
entered
Step 6: The systemdisplaysan
appropriate errormessage
Conclusions Newmembertype iscreated
Post conditions
BusinessRules
Implementation
Constraints

Page 10 of 42
4.2.2. Change Member Type
Membertypescan be changedat any time (new age category,etc). Existingmemberscan
Use Case Name Change Member Type
Use Case Id 2
Priority 2
Source Management
Description The staff memberwishestochange membertype.
Preconditions
Trigger Administratorwishestochange amembertype.
Step 1: The staff memberinvokes
the change membertype function.
Step 3: The staff memberselects
the required membertype tobe
changed.
Step 5: The staff membermakes
the requiredamendments.
Step 2: The systemretrieves
membershiptype detailsfrom the
Ratesand displaysonthe UI.
Step 4: The systemdisplaysthe
detailsforthe selectedmember
type on the UI.
inputdata:
 All fieldare required
 Fee mustbe greaterthan
zero
Step 7: The systemsavesthe
amendedmembertype detailsin
the Memberfile.
Change
Member Type
Administrator
Validate
Member Type
<<includes>>

Page 11 of 42
Step 9: The systemresetsthe UI.
entered
Step 6: A requiredfieldisnot
entered.
appropriate errormessage.
Conclusions Membertype ischanged
Post conditions
BusinessRules
Implementation
Constraints

Page 12 of 42
4.3. MemberManagement
The system has five essential requirements in relation to the management of member data. The
registering of members, amending members, de-registering members, the listing of members and
also the issuing of member invoice.
4.3.1. Register Member
Details of all golf course members must be held within the system. Each new member is
assigned a unique member identification number (Mem_ID) which is assigned by the system.
Use Case Name RegisterNewMember
Use Case Id 3
Priority 1
Source Management
Description Thisfunctionregistersanew memberof the golf clubonthe system.
Preconditions Firstfee paymentmusthave beenreceivedfromthe member.
Trigger Memberrequests togainmembershiptoGolf course.
the registermemberfunction.
Step 2: The systemdeterminesthe
nextMem_Id.
membership type detailsfromthe
Ratesfile.
Register
Member
Administrator
Validate
Member Type
<<includes>>
Member

Page 13 of 42
Step 5: The staff memberenters
the requiredmemberdetails:
 Surname
 Forename
 Address
 Email
 Phone
 DOB
 MembershipType
Step 6: The staff memberconfirms
that the registrationistoproceed
inputdata:
 All fieldsare required
 DOB mustnot be in the
future
 DOB mustbe compatible
withmembershiptype
Step 8: Registrationdate is
assignedthe systemdate
Step 9: Memberstatusis assigned
the defaultstatus‘active’
Step 10: Nextrenewal date issetto
systemdate plusone year.
Step 11: The systemstoresthe
memberdetailsinthe Memberfile
Step 12: The systemdeterminesthe
nextPay_Idand storespayment
detailsinthe Paymentsfile:
 Pay_Id
 PaymentDate
 Amount
 Mem_Id
confirmationmessage
entered
entered

Page 14 of 42
Conclusions The newmemberisregistered
Post conditions Membermusthave validIdentificationtobecome anew member.
BusinessRules Juniormembermustbe under18.
Implementation
Constraints

Page 15 of 42
4.3.2. Amend Member
Use Case Name AmendMember
Use Case Id 4
Priority 1
Source Members
Other ParticipatingActors Member
Description Memberof Staff wishestoamenddetailsof member.
Preconditions Membermustbe an active member.
Trigger Administratorrequests toamendmember’sdetails.
the Mem_Id.
the details tobe amended:
 Surname
 Forename
 Address
 Email
 Phone
 DOB
 MembershipType
Step 6: The staff memberconfirms
that the registrationistoproceed
Mem_Id fromthe Members file
inputdata:
 All fieldsare required
 DOB mustnot be in the
future
 DOB mustbe compatible
withmembershiptype
Step 7: The systemstoresthe
amended memberdetailsinthe
Memberfile
confirmationmessage
Amend
Member
Administrator
Validate
Member Type
<<includes>>
Member

Page 16 of 42
entered
entered
Conclusions The amendeddetailsare updated
Post conditions Membermusthave validIdentificationto amendtheirdetailsonthe
system.
BusinessRules
Implementation
Constraints

Page 17 of 42
4.3.3. De-Register Member
Use Case Name De-RegisterMember
Use Case Id 5
Priority 2
Source Members
Other ParticipatingActors Member
Description Memberwishesto de-registerasa memberof golf course.
Preconditions Must holdfull membershipinordertode-registerfromgolf course
membership.
Trigger Memberrequests tode-registermembershipwithGolf course.
the de-registermemberfunction.
the Mem_Id.
Step 6: Staff memberenters‘yes’.
Step 2: The systemrequests
Mem_Id.
Step 4: The systemretrieves the
information associated withthe
Mem_Id.
Step 5: The systemasksuser‘Are
You Sure You Want To De-Register
Member’.
Step 7: Memberstatusis assigned
the defaultstatus‘de-active’
De-Register
Member
Administrator Member

Page 18 of 42
Conclusions The memberis de-registered
Post conditions Memberisno longera memberof the golf club.
BusinessRules Onlyan active membercanbe de-registered.
Implementation
Constraints

Page 19 of 42
4.3.4. List Members
Use Case Name List Members
Use Case Id 6
Priority 1
Source Admin
Description Thisfunction requiresthe systemtoproduce alistof all clubmember
whichcan be presentedinorderof name,membershipdetailsor
membershiptype.
Preconditions Membersmustbe registeredonthe golf membershipsystembeforethey
can be listed
Trigger Administratorrequiresalistof all currentmembers.
Step 1: The administratorrequests
a listof all currentgolf course
members.
Step 3: The administratorspecifies
a sort orderfor the listing
 Surname
 Forename
 MembershipType
Step 6: The administratorenter
“Yes” or “No”.
Step 2: The systemretrievesdetails
of all currentmembersanddisplays
theminorder of name.
Step 4: The systemretrievesthe
detailsof all currentmembersand
displaystheminthe order
specified.
Step 5: The systemissuesa
message “Doyou wishtoprint
data?”
List Members
Administrator
Validate
Member Type
<<includes>>

Page 20 of 42
No Memberdetailsfound Step 3: The systemalertsthe
administratortothe fact that there
isno data available forthe listing(A
message isdisplayedonthe User
Interface)
Conclusions A listingof all currentmemberswithinthe golf course isgenerated.
Post conditions
BusinessRules Members’detailsmayonlybe viewed,notchangedordeleted,when
displayedinthisway.
The listshouldonlyinclude currentmembers.
Implementation
Constraints

Page 21 of 42
4.4. FinanceManagement
The system has two essential requirements in relation to the management of finance data. The
issuing of renewal notices to members and also the recording of payment received from
members.
4.4.1. Issue Member Invoice
Use Case Name Issue MemberInvoice
Use Case Id 7
Priority 1
Source Finance
Description Thisfunctionissuesmemberinvoices.
Preconditions Membersmustbe registeredonthe golf membershipsystembeforean
invoice canbe issued.
Trigger Administratorrequestsinvoice toissue tomember.
issue memberinvoice.
Step 3: The administratorenters
requiredMem_Id.
Step 5: The userconfirmsthatthe
invoice istobe issuedtothe
member.
of the memberfromthe Member
file anddisplaysonthe UI.
Step 6: The systemgeneratesthe
invoice and issuesittomembervia
email orpost (if email isn’tonfile).
Issue Member
Invoice
Administrator
Member

Page 22 of 42
Conclusions An invoice isissuedtomember.
Post conditions Can onlybe issuedtoexistingmembers.
BusinessRules
Implementation
Constraints

Page 23 of 42
4.4.2. Issue Renewal Notice
Use Case Name Issue Renewal Notice
Use Case Id 8
Priority 1
Source Finance
Description Adminwishestoissue renewal notice tomember
Preconditions Members membership mustbe due toexpirywithinamonthtobe issued
a renewal notice.
Trigger Administratorrequiresarenewal noticetobe issuedtomember.
issue renewal notice.
memberswhose renewal date is
withinamonth.
Step 4: The userconfirmsthatthe
invoice istobe issuedtothe
member.
of all members frommemberfile
whose renewal date is withina
monthand displaysonthe UI.
Step 5: The systemgeneratesthe
invoice and issuesittomembervia
email orpost (if email isn’tonfile).
Conclusions A renewal notice isissuedtomember.
Post conditions Can onlybe issuedto existingmembers.
BusinessRules
Issue Renewal
Notice
Administrator
Member

Page 24 of 42
Implementation
Constraints

Page 25 of 42
4.4.3. Record Payment
Use Case Name Record Payment
Use Case Id 9
Priority 1
Source Finance
Description Adminwishestorecordpaymentfrommember
Preconditions Must of receivedpaymentfrommember
Trigger Memberpaysmembershipfee.
Step 1: The administratorinvokes
the record paymentfunction.
requiredMem_Id.
the amountreceivedfrommember.
Step 7: Nextrenewal date issetby
user.
Step 2: The systemrequests
Mem_Id.
frommemberfile anddisplayedon
UI for User to enterpaymentdetails
(amount).
Step 6: Systemchecksthat input
data isvalidand thatthe amount
matchesthe fee due forthe
membershiptype.
Step 8: Systemstoresdetailsinthe
Paymentfile andnextrenewal date
isupdatedinthe memberfile.
Step 9: Receiptemailedtomember
Confirmationmessage displayed
Record
Payment
Administrator Member

Page 26 of 42
Conclusions A paymentisrecorded asreceivedfrommember
Post conditions Membermusthave paid membershipfee torecordpayment.
BusinessRules
Implementation
Constraints

Page 27 of 42
4.5. Admin
The system has three essential requirements in relation to the management of admin data. The
income analysis, member analysis and also the listing of any late fees outstanding.
4.5.1. Income Analysis
Use Case Name Income Analysis
Use Case Id 10
Priority 1
Source Admin
Description Adminwishesto performanincome analysis.
Preconditions
Trigger Adminrequiresanincome analysis.
the income analysis function.
a sort orderfor the listing(payment
details,monthlyincome,etc.)
‘yes’or‘no’.
of income analysisfromfinance and
displaysthe dataindefaultorder.
data of income analysisand
specified.
data?”
Income
Analysis
Administrator

Page 28 of 42
Conclusions An income analysisisperformed.
Post conditions
BusinessRules
Implementation
Constraints

Page 29 of 42
4.5.2. Member Analysis
Use Case Name MemberAnalysis
Use Case Id 11
Priority 1
Source Admin
Description Adminwishesto performanincome analysis.
Preconditions
Trigger Adminrequiresamemberanalysis.
the memberanalysisfunction.
a sort orderfor the listing
(membershipId,membership
details, surname,forename, etc.)
of memberanalysisfrommembers
file anddisplaysthe dataindefault
order.
data of memberanalysisand
specified.
data?”
Conclusions A memberanalysisisperformed.
Member
Analysis
Administrator

Page 30 of 42
Post conditions
BusinessRules
Implementation
Constraints

Page 31 of 42
4.5.3. List Late Fees
Use Case Name List Late Fees
Use Case Id 12
Priority 1
Source Admin
Description Adminwishes compile alistof memberswithlate feesoutstanding.
Preconditions Membersmustbe registeredonthe golf membershipsystem andhave
late feesoutstanding.
Trigger Adminrequestsalistof all late fees.
the listlate feesfunction.
a sort orderfor the listing;
(membershiptype,membership
details,surname,forename)
of late feesoutstanding and
displaysthemindefaultorder.
detailsof all late fees anddisplays
theminthe orderspecified.
data?”
No Memberdetailsfound Step 3: The systemalertsthe
administratortothe fact that there
isno data available forthe listing(A
message isdisplayedonthe User
Interface)
List Late Fees
Administrator
Validate
Member Type
<<includes>>

Page 32 of 42
Conclusions A listingof all late feesof members withinthe golf course isgenerated.
Post conditions
BusinessRules The listshouldonlyinclude member withlate feesoutstanding.
Implementation
Constraints

Page 33 of 42
5. SystemModel
5.1. DataFlowDiagrams – Elements
External Entities:
Member
Data Stores:
D1 Members File
D2 Rates File
D3 Payments File
Processes:
P1 Process Rates
P1.1 Create Member Type
P1.2 Change Member Type
P2 Manage Members
P2.1 Register Member
P2.2 Amend Member
P2.3 De-Register Member
P2.4 List Members
P3 Manage Finance
P3.1 Issue Member Notice
P3.2 Issue Renewal Notice
P3.3 Record Payment
P4 Process Admin
P4.1 Income Analysis
P4.2 Member Analysis
P4.3 List Late Fees

Page 34 of 42
5.2. Level-0DFD
Member
Golf 365
Member details
MembershipCard

Page 35 of 42
Rate
Details
5.3. Level-1DFD
Member
P1
Process
Rates
D1 Members File
P2
Manage
Members
P3
Manage
Finance
P4
Process
Admin
D2 Rates File
D3 Payments File

Page 36 of 42
5.4. Level-2DFD– ProcessP1
P1.1
Create
Member
Type
P1.2
Change
Member
Type
D2 Rates File

Page 37 of 42
P2.1
Register
Member
P2.3
De-
Register
Member
P2.4
List
Member
P2.2
Amend
Member
D1 Members File
D2 Rates File
D3 Payments File
Member
Member
Member

Page 38 of 42
P3.1
Issue
Member
Invoice
P3.2
Issue
Renewal
Notice
P3.3
Record
Payment
D1 Members File
D3 Payments File
Member

Page 39 of 42
P4.1
Income
Analysis
P4.2
Member
Analysis
P4.3
List Late
Fee
D1 Members File
D3 Payments File
D3 Payments File

Page 40 of 42
1 …*
1
1
1 …*
1 …*
1
6. DataModel
Rates
Create MemberType {pk}
Change MemberType
Finance
Issue MemberInvoice
Issue Renewal Notice
RecordPayment{pk}
Members
RegisterMember{pk}
AmendMember
De-RegisterMember
List Members
Admin
Income Analysis
MemberAnalysis{pk}
List Late Fees

Page 41 of 42
7. DatabaseSchema
Schema: Golf365
Relation:Rate
Attributes:
Create MemberType char (10) NOT NULL,
Change MemberType char (10) NOT NULL,
PRIMARY KEY: Create MemberType
FOREIGN KEY:
Relation:Members
Attributes:
RegisterMemberchar(10) NOT NULL,
AmendMemberchar (10) NOTNULL,
De-RegisterMemberint(5),
List Members char (10)
PRIMARY KEY: RegisterMember
Relation:Finance
Attributes:
Issue MemberInvoice int(5),
Issue Renewal Notice int(5),
RecordPaymentint(5),
PRIMARY KEY: RecordPayment
FOREIGN KEY:
Relation:Admin
Attributes:
Income Analysis
MemberAnalysis
List Late Fees
PRIMARY KEY: MemberAnalysis
FOREIGN KEY:

Page 42 of 42
8. Conclusion

Golf Management System

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (7)

Similar to Golf Management System

Similar to Golf Management System (20)

Recently uploaded

Recently uploaded (20)

Golf Management System