Event management Webseite in short...
Users of this service (website) must register themselves [url removed, login to view] must provide the following information:
1. A Username of their choice.
2. Valid Email address
3. Password (2x )
4. Optional phone number (eventually to be used for sending SMS)
--- Validation procedure of registration by Email is required
--- Validation checking must be included
20 different events must be shown (e.g. in a table) on the events page as below:
Events are specified by the Day (Mo. Tu., Wed. etc), Month, numeric Day and starting time of the event.
Up to 16 participants can register for an event and their names (=usernames) are listed accordingly.
For each event there shall be two buttons to confirm participation or cancel participation.
The booking for an event shall be made by clicking a button (Click to join the event).
If someone wants to cancel his participation at the event, he may click on another button (cancel participation).
Mo. Oct.5; 19:00 Magat, Seeler, Maier, Peter,
Henry, Ballack, Mueller, Heini,
Toppi, Hans K.,Bommel, Mausi,
Wed. Oct 8; 18:00 ......
Fr. Oct 10; 10:00 ......
And so on (in total the next 20 events are to be shown)
Functionality more in detail:
1. Initial Registration Process
A new visitor of the page needs to register first in order to use this service.
After providing his username, Email address, 2x password and (optionally) SMS number, a check has to be done with the database, whether this username exists already. If yes a respective message must come up and the process shall start again. The same check must be made for the Email address, password and sms number. Once all these validation procedures lead to negative results, an Email shall be send to the new user for validation purpose. If validation is confirmed, the username, Email, password and SMS must be considered as valid data in the database.
2. Log in procedure and booking procedure
A registered user logs into the webpage by entering username and password. The username is also the participant name as it appears in the events table.
If username and password is validated, a new page will come up showing the next 20 upcoming events with the respective registered players.
If the user wants to join an event, he can now click on the JOIN EVENT button. If this button is clicked, the system must first check for the number of participants on the particular selected event. If it is fully booked (16 people are booked) a respective message must come up. If less than 16 players are registered, a check must be done whether the current user is registered for the event already. If yes, a respective message must come up. If he is not registered yet, the username shall be added to the database and also shown in the list of players and a message should come up “You are registered for this event on …(Date).. starting at …(Time).”
Automatically an Email shall be send to all other participants informing them that the respective user has confirmed his participation for the particular event.
3. Cancellation procedure
If a participant wants to cancel his participation, he has to log in, go to the respective event where he is listed with his username and then he must click the CANCEL PARTICIPATION button. Now the system must first check with the database whether the user is registered already. If not, a respective message must come up. If yes, the name should be deleted from the database and the following player names in the database shall move one step up in order to make sure there is no empty space left in the listing of participants.
A message must appear such as ”Your cancellation for the event …(Date) with starting (Time) has been confirmed”.
Furthermore an Email must be send to all the other remaining participants, informing them that the user…(Name) . has cancelled his participation for the event on …(Day)….(Date) and (start time)….
4. Passed events - Automatic update of events
Once the date and starting time of the event is passed, the respective data for that event shall not be used anymore for display on the site. Means: The user should always see the next upcoming event on top of the event list and the following events further below.
5. Admin input for new events
There should be an admin page which allows to fill in further events with Day (Mo. Tu. We etc. ) Date and Start time.
The admin should also be able to see all data referring to passed events.
NOTE: This is the first phase of this project. Means: It is planned to extend the above functionality further later on.