Starting from:
$29.99
Final Project: Rock, Paper, Scissors
UNIX System Programming
Final Programming Project
As stated in the syllabus, the final programming project is worth 20% of the final grade. This final project has two parts. The first part is a TCP network client/server. The second part is the same client with a GTK+ GUI. Part 1: Rock, Paper, Scissors (65% points) We would like two programs (a referee and a player - there will be two players running at the same time) that interact over the Internet to play the "Rock, Paper, Scissors" game. In this game, two players secretly choose one item out of the set of rock, paper, and scissors. They then reveal their choice. A referee decides who wins as follows: • Paper beats rock (by covering it). • Rock beats scissors (by smashing it). • Scissors beats paper (by cutting it). • Matching choices are a draw. The winning player gets a point. In a draw, no points are awarded. The referee program (the "server") should create and bind a network socket with a random port chosen. The port number should be displayed. Then the referee should wait for two players to connect and then send data to the players indicating that the game may begin. The player program (the "client") should take a server machine name and a port number as commandline arguments. It should create a network socket and connect to the referee process . (If there is no referee process to connect to, the program should exit with an error message.) A player then should prompt the local user to enter a choice. The choice is sent to the referee. After the referee receives two choices, it should decide which player has won the round and send information about the round back to both players so that they may display the results to the local user. The system must implement the following network protocol. The player programs must send the string "READY" to the referee when they are ready to make a choice. The referee should then respond to each player with the string "GO". Thereafter, the players alternate sending an item choice and receiving the results of the round. (The format of this information is your choice.) When a user wishes to exit, the player program should send the "STOP" string to the referee. The referee should respond with the string "STOP" to both players followed by summary game information (number of rounds won by each player, etc., again the format of this information is your choice). The players should display this information to the local user and then exit. The referee should return to waiting for the next pair of player connections. (I.e., the referee process is intended to run indefinitely.) Assignment Write programs named referee and player that implement the referee and player programs. Here is an example of possible referee and player sessions running on (fictitious) machines named newton, galileo, and einstein. (User input is shown in bold.)
Page 1 of 3
On newton On galileo On einstein $ ./referee Referee is using port 2345 Referee is waiting for players Player 1 has connected Player 2 has connected P1 choice: Rock P2 choice: Scissors P1 wins P1 choice: Rock P2 choice: Exit Game has ended Referee is waiting for players $ ./player newton 2345 You are player 1. 0: Exit 1: Rock 2: Paper 3: Scissors Enter Choice: 1 Round 1: Player 1: Rock Player 2: Scissors You win! 0: Exit 1: Rock 2: Paper 3: Scissors Enter Choice:1 Game has ended Final Score Player 1: 1 Player 2: 0 $ $ ./player newton 2345 You are player 2. 0: Exit 1: Rock 2: Paper 3: Scissors Enter Choice: 3 Round 1: Player 1: Rock layer 2: Scissors Sorry, you lose 0: Exit 1: Rock 2: Paper 3: Scissors Enter Choice: 0 Game has ended Final Score Player 1: 1 Player 2: 0 $ Note that you should test your programs using different machines for each process. Note that all the Linux machines in CS Lab, KC-267, and KC-136 are file-served by csserver and all are the same hardware, so once you have created your programs, you just need to start your server on csserver, then log into two other machines and run the player program from each machine.
Page 2 of 3
Part 2: GUI Frontend for Player (35% points) We would like a player program with a GUI. The layout and interaction is your design, but at a minimum it should have the following functionality: • It should allow the user to give the machine name and port number of a referee process and connect to it using a connect button. • It should allow the user to indicate their item choice via mouse click (i.e., the user should not need to type the item choice), then send it to the referee using a send button. • It should display the referee result. • It should have a quit button that causes the player program to display the final results and require another button click to actually quit the program. Note that the GUI player program must follow the same network protocol as the text-only player program in Part 1. That is, there is only one referee program, and it will referee games between any two player programs whether they are text-only or have a GUI. Assignment Write a C/C++ program named gui-player that implements the GUI player. This program must use the GTK+ toolkit. This program must run on the CS Lab machines. What to submit • Provide a makefile named Makefile that will make all three programs (referee, player, and gui-player) for this assignment as the default target (typically called all). Each program must be a separate target. • Provide a README textfile with instructions on how to user your programs. • Create a tarfile or zipfile containing the program source files, the makefile, and the README file. • Submit your archive using the submission system (http://submission.evansville.edu). The grading script only will make the project and check that executables named referee, player, and gui-player are produced. It will not run anything.
Final Programming Project
As stated in the syllabus, the final programming project is worth 20% of the final grade. This final project has two parts. The first part is a TCP network client/server. The second part is the same client with a GTK+ GUI. Part 1: Rock, Paper, Scissors (65% points) We would like two programs (a referee and a player - there will be two players running at the same time) that interact over the Internet to play the "Rock, Paper, Scissors" game. In this game, two players secretly choose one item out of the set of rock, paper, and scissors. They then reveal their choice. A referee decides who wins as follows: • Paper beats rock (by covering it). • Rock beats scissors (by smashing it). • Scissors beats paper (by cutting it). • Matching choices are a draw. The winning player gets a point. In a draw, no points are awarded. The referee program (the "server") should create and bind a network socket with a random port chosen. The port number should be displayed. Then the referee should wait for two players to connect and then send data to the players indicating that the game may begin. The player program (the "client") should take a server machine name and a port number as commandline arguments. It should create a network socket and connect to the referee process . (If there is no referee process to connect to, the program should exit with an error message.) A player then should prompt the local user to enter a choice. The choice is sent to the referee. After the referee receives two choices, it should decide which player has won the round and send information about the round back to both players so that they may display the results to the local user. The system must implement the following network protocol. The player programs must send the string "READY" to the referee when they are ready to make a choice. The referee should then respond to each player with the string "GO". Thereafter, the players alternate sending an item choice and receiving the results of the round. (The format of this information is your choice.) When a user wishes to exit, the player program should send the "STOP" string to the referee. The referee should respond with the string "STOP" to both players followed by summary game information (number of rounds won by each player, etc., again the format of this information is your choice). The players should display this information to the local user and then exit. The referee should return to waiting for the next pair of player connections. (I.e., the referee process is intended to run indefinitely.) Assignment Write programs named referee and player that implement the referee and player programs. Here is an example of possible referee and player sessions running on (fictitious) machines named newton, galileo, and einstein. (User input is shown in bold.)
Page 1 of 3
On newton On galileo On einstein $ ./referee Referee is using port 2345 Referee is waiting for players Player 1 has connected Player 2 has connected P1 choice: Rock P2 choice: Scissors P1 wins P1 choice: Rock P2 choice: Exit Game has ended Referee is waiting for players $ ./player newton 2345 You are player 1. 0: Exit 1: Rock 2: Paper 3: Scissors Enter Choice: 1 Round 1: Player 1: Rock Player 2: Scissors You win! 0: Exit 1: Rock 2: Paper 3: Scissors Enter Choice:1 Game has ended Final Score Player 1: 1 Player 2: 0 $ $ ./player newton 2345 You are player 2. 0: Exit 1: Rock 2: Paper 3: Scissors Enter Choice: 3 Round 1: Player 1: Rock layer 2: Scissors Sorry, you lose 0: Exit 1: Rock 2: Paper 3: Scissors Enter Choice: 0 Game has ended Final Score Player 1: 1 Player 2: 0 $ Note that you should test your programs using different machines for each process. Note that all the Linux machines in CS Lab, KC-267, and KC-136 are file-served by csserver and all are the same hardware, so once you have created your programs, you just need to start your server on csserver, then log into two other machines and run the player program from each machine.
Page 2 of 3
Part 2: GUI Frontend for Player (35% points) We would like a player program with a GUI. The layout and interaction is your design, but at a minimum it should have the following functionality: • It should allow the user to give the machine name and port number of a referee process and connect to it using a connect button. • It should allow the user to indicate their item choice via mouse click (i.e., the user should not need to type the item choice), then send it to the referee using a send button. • It should display the referee result. • It should have a quit button that causes the player program to display the final results and require another button click to actually quit the program. Note that the GUI player program must follow the same network protocol as the text-only player program in Part 1. That is, there is only one referee program, and it will referee games between any two player programs whether they are text-only or have a GUI. Assignment Write a C/C++ program named gui-player that implements the GUI player. This program must use the GTK+ toolkit. This program must run on the CS Lab machines. What to submit • Provide a makefile named Makefile that will make all three programs (referee, player, and gui-player) for this assignment as the default target (typically called all). Each program must be a separate target. • Provide a README textfile with instructions on how to user your programs. • Create a tarfile or zipfile containing the program source files, the makefile, and the README file. • Submit your archive using the submission system (http://submission.evansville.edu). The grading script only will make the project and check that executables named referee, player, and gui-player are produced. It will not run anything.
1 file (132.2KB)
