Cheltenham Club Information System

Use case diagram
1.1 Functional requirements
The main functional requirements of the system are:
 The system should be able to record the details of the members of the club.
 The system should be able to record the details which includes the name, contact
details, role, date of joining the club.
 The system should provide the club members with the option to view their profile
on the system and also add, modify their details on the portal.
 The system should also be able to maintain a record keeping option for the
accounts of the club. The system would be able to fine the players in case they are
not paying the fees on time. The system should be able to dismiss the players
would be dismissed from the club if they do not pay the fees for a long period of
time.
 In addition to this, the system should be able to store the details of the game. In
case the game is cancelled or postponed the system would store the details as null
in the tables created in the system.
 The system should be able to record the training session of the players who are
members for the club.
 The members should be able to view and update their profile.
 The system should be able to provide the user with the option of searching for the
possible options in the system. The system should also be able to provide the
reports for the requested by the users in the system.
1.2 use case diagram
1

2

2) use case diagram documentation
Primary use case 1
Use Case
Title: Record Details
Actors: Players, Admin
Description: The admin would be storing the details of the players in the system.
Each and every detail of the player would be stored in to the
information system implemented for the club.
Precondition The pre-condition is that the player should be eligible for registration
into the system.
Flow 1.Record details
2.Add Details
3.Modify Details
Alternative
Flow
1. Log In
2. Add Details
3. Record Details
4. Delete Details
Primary use case 2
Use Case Title: Update Account
Actors: Player
Description: The Player or the member who is attached to the system
would be able to update their details on the portal
Precondition The player would be able to view their profile on the system.
Flow 1. Record Details
2. View Account
3. Update Account
Primary use case 3
Use Case Title: Record Match Details
Actors: System
3

Description: The system would be able to store the details of the matches
that take place.
Precondition The admin should be logged in to the system.
Flow 1. Log in
2. Record Match Details
Primary use case 4
Use Case Title: Suspend Players
Actors: Players, System
Description: The system would be checking the fess payments made by
the players. If the player does not make the payment, then the
system would be suspending the player.
Precondition Check Payment
Flow 1. Check Payment
2. Suspend Player
Primary use case 5
Use Case Title: Modify details
Actors: Admin, Players
Description: The admin would be modifying the details stored in the
system for the players.
Precondition Record Details
Flow 1. Log In
2. Add Details
3. Record Details
4. Modify Details
10 use cases - brief description
Use case 1: Log in: The Admin would be logging into the system
Use case 2: Add Details: The Admin would be adding the details of the players in the
system.
Use case 3: Record Details: The details of the players would be recorded in to the system.
Use case 4: Modify Details: the admin would be modifying the details of the players into
the system.
4