Squash ladder ranking system

**STIGESPILLET** **Ladder for Nidaros Squash Club** # Introduction The target is to make a "ladder" based ranking system for squash players. A number of squash players meet once a week and play. Based on the result the ranking (ladder) for next week will be made/updated. Players should also be able to login and register for play for the next week. *Note: this is not a system where players can challenge other players on the ladder. We play weekly and the all the matches will be finished within approx. 2 hours.* The ranking system should be preferably made in .php with an open source Sql database. Tools must be approved prior to starting. Result and examples from our former 10 year old Access based system (manually uploaded database) can be found here: <[login to view URL]> Access to the [[login to view URL]][1] servers for testing can be given according to agreement. The Access database system is attached for reference. The two files MUST be stored in C:\_Stigespillet\. The image files must be stored in C:\_Stigespillet\bilder\. Note that the ranking routine is not correct. See the attachment for proposal of tables (some copied from the Access system). * SpecStigespillet [login to view URL] # The organizing of the play The play will be organized in as many 4 player groups as possible. In a 4 player group there will be 4 matches in a 2 hour period. First player 1/A and 4/D in the group will play in Match (K1). Then the player 2/B and 3/B will play in Match (K2). Then the winner of match 1 will meet the winner of match 2 in the Match (K3). Last the loser will play the looser in Match (K4). The new rank (for this group) will be: 1) Winner of Match (K3) 2) Loser of Match (K3) 3) Winner of Match (K4) 4) Loser of Match (K4) (opp = Up , ned = Down - V = winner / T = Looser) ## Deliverables **STIGESPILLET** **Ladder for Nidaros Squash Club** # Introduction The target is to make a "ladder" based ranking system for squash players. A number of squash players meet once a week and play. Based on the result the ranking (ladder) for next week will be made/updated. Players should also be able to login and register for play for the next week. *Note: this is not a system where players can challenge other players on the ladder. We play weekly and the all the matches will be finished within approx. 2 hours.* The ranking system should be preferably made in .php with an open source Sql database. Tools must be approved prior to starting. Result and examples from our former 10 year old Access based system (manually uploaded database) can be found here: <[login to view URL]> Access to the [[login to view URL]][1] servers for testing can be given according to agreement. The Access database system is attached for reference. The two files MUST be stored in C:\_Stigespillet\. The image files must be stored in C:\_Stigespillet\bilder\. Note that the ranking routine is not correct. See the attachment for proposal of tables (some copied from the Access system). * SpecStigespillet [login to view URL] # The organizing of the play The play will be organized in as many 4 player groups as possible. In a 4 player group there will be 4 matches in a 2 hour period. First player 1/A and 4/D in the group will play in Match (K1). Then the player 2/B and 3/B will play in Match (K2). Then the winner of match 1 will meet the winner of match 2 in the Match (K3). Last the loser will play the looser in Match (K4). The new rank (for this group) will be: 1) Winner of Match (K3) 2) Loser of Match (K3) 3) Winner of Match (K4) 4) Loser of Match (K4) (opp = Up , ned = Down - V = winner / T = Looser) Similar maps can be found for 3 and 5 groups - witch could be needed depending on how many players joining. The number of players per group can be found in table TBL_PlayersOnCourts in the file "SpecStigespillet [login to view URL]". # User stories USER - the general user of the system. ADMIN - several people with the ADMIN role registered in the TBL_Players. Anything the USER can do the ADMIN can do. ANYONE - Open page for anyone. All user stories are according to rights after login to the pages. 1. **User login** The USER or ADMIN can log into the system. There is a contact e-mail address for new players who must be registered by an admin (after paying the register fee). 1. **User information** The USER and ADMIN can view, change and update his/her personal information and password. Only an admin can set admin rights for an user. 1. **Forgot password** The USER can request an e-mail with his password. 1. **New player** The ADMIN can register new players with e-mail and a proposed dummy password. The user must fill in personal information and can change his password if he or she likes. 1. **User registration for play (done weekly)** The User can register or unregister for play in the period from VAR_EnlistTime to VAR_LastUnlistTime. Before or after these two periods the register or unregister is locked and this is stated. 1. **User registration (fast)** The User can register directly through a http\\... address including the e-mail and password. 1. **Arrange play** The play is organized according to rank and who is registered for play. A proposal for the new groups/courts should be given according to TBL_PlayersOnCourts. Admin can change this manually. In order to change order for the player the rank value must be changed. 1. **Show play** The play is shown organized according to rank, who is coming to play and court number for the player. There should be included graphics according to the following 4,5 or 3 man groups. See also the section "The organizing of the play". 1. **Enter result** The ADMIN can register result as letters in the new order where A = player 1, B = player 2 and so on. Player E, D, C, B, A means that player number 5 is now the new number 1, player number 1 is the new number 5 and so on. 1. **Create the new ranking** After all the results from the last play have been entered the ranking for next play can be made. The philosophy of the ranking is that all players not meeting will lose at least one rank. All the players registered for play moves out of the ranking. All players not registered for play moves automatically at least one place down. The players "playing" then competes for the "free" places in between the players not playing. The players will be ranked according to how they win in their groups. All players that are not playing will move one place down on the ladder (+1). If the user is registered for play and does not show up he will lose all his matches and will get a +4 rank penalty in addition. The players will be ranked according to how they win in their groups. The winner of group 1 will have the rank = 1 (overall winner) The winner of group 2 will swap place with the loser of group 1 The winner of group 3 will swap place with the loser of group 2 And so on? All results will be stored in the Log The new ranking list will be ready for play next week. Note that players can register for next weeks play prior to the creating of the new ranking list. Maybe the ADMIN have no time to register the results before 3 days after the games. The next morning the players can register for play next week. See also example of ranking in the "Example of ranking routine" worksheet of the file "SpecStigespillet [login to view URL]". 1. **Admin edit** The ADMIN can change all values in all tables 1. **Show information** The ADMIN can list out all players with all information. 1. **See the log** Anyone can look at the log and result similar to this. <[login to view URL]>