Subject: CS340: demo instructions and tasks From: Tom Horton Date: Sun, 27 Apr 2008 16:58:04 -0400 To: cs340-1@toolkit.itc.virginia.edu Below is a plan for the demo session each pair of groups should do with me this coming week. Getting all this done in a 10-minute slot in Monday's lab will be tight, so you Monday folks should be be careful to be on time and get your SW running promptly -- thanks in advance! What I list below is what I think are the basics of the functionality requested by "the customer". I know many of your programs will do more, and I will want to see that. Also, I am sure that some things won't work for some groups, and don't panic about that during the demo. (Room connections to a 2nd server's world is probably the most challenging requirement, and it would not surprise me at all if not many groups got to this.) Note that each group has to bring a piece of paper with a list of things on it -- see below. This is not intended to be a formal document, just an aid for the instructor to look at while you explain things. Good luck, everyone! I'm looking forward to seeing what you have. ===== Instructions: ============= Groups should arrive *at least* five minutes before demo time. Groups find out from instructor or TA how to download submitted files. Groups find at least two PCs to use (maybe 3 -- see below for why). Download files and get them ready to run promptly at the appointed time. When the instructor/TA arrives: Start the server. Start the server on 2nd PC if you'll demo server-to-server room connections. Each group must give the instructor/TA a piece of paper with a list of features that work (based on task-list below but also including additional features you completed). Also include major features that your partner group specified that you didn't get implemented. This does not have to be a formal document. Tasks to Demo the Admin Client (5 minutes): 0) Start up and connect to a server. 1) Show contents of current world. 2) Show contents of a given room, including items, characters, etc. 3) Create a new room and connect to an existing room. Modify its properities. 4) Create a new item in a room. Modify its properties. 5) Create connection to a room on server running on a 2nd PC. 6) (During player-client demo later) Show that display updates appropriately when a player interacts with world. 7) Create a connection to a room on the 2nd server and show that both servers' worlds recognize this. 8) Demo any other features you have implemented. Other management operations? Other chat operations? Etc. 9) Briefly note any features that are known to be buggy or problematic. Tasks to Demo the Player Client (5 minutes): 0) Start up and connect to server. 1) Start up 2nd player-client on a 2nd PC. 2) Display what's in current room. 3) Move to an adjacent room. 4) Pick up object, then set it down. 5) Chat with character from player-app running on 2nd PC. 6) Show that changes in world made by the player-app update what is shown in 2nd player-app's display (and admin client). 7) Show that changes made by admin client update player-app's display. 8) Move from current server's world to a world on the 2nd server. 7) Demo any other features you have implemented. 8) Briefly note any features that are known to be buggy or problematic. 9) If you save info from run-to-run of the player client etc., describe that. If there's time at the end of your ten-minute slot, both groups should be ready to chat informally about these things: a) What were the biggest challenges (technical, group-interaction, management)? b) What things most helped you succeed? c) What would you have done differently? After completing the demo, groups are encouraged to do something to celebrate the completion of their project! Shouts of joy, everyone going for a cup of coffee, sharing a pizza, champagne and streamers, distribution of bonus-pay by group-leader, etc. are appropriate displays of celebration! :-) -- Dr. Tom Horton, Associate Professor Dept. of Computer Science, University of Virginia 151 Engineer's Way, P.O. Box 400740 Charlottesville, VA 22904-4740 Phone: 434 982-2217 FAX: 434 982-2214 horton@virginia.edu http://www.cs.virginia.edu/~horton