5/5/2008
User-Client Prototyping Report
Team 12
Erin Carson
Sholanda McCullough
John Will
Prototyping Plan
• Goals
o A working, functional prototype
o Simple error handling in user input
o Implement the communication requirements described below
• Requirements
o Client will be able to
Recognize user input as commands to server
Send the messages to the server
Receive messages from the server and update client-side data
accordingly
Display current player state (username, room, items, inventory,
other players) to the user
o Supported messages
/logon <username>
/exit <username>
/pickup <object>
/drop <object>
Prototyping Status
• Error checking in user-input commands
o The client currently ensures that the user has input a valid command that
will be understood by the server (/logon, /exit, /drop, /pickup)
• Logon functionality
o The client supports the logon function.
o Error handling: if the user types the /logon command at times other than
initial connection, an error message is printed and the message is not sent
to the server
• Pickup functionality
o The client support the pickup function
5/5/2008
o Error handling: if the user attempts to pickup an object that is not currently
in the room, an error message is printed and the message is not sent to the
server
• Drop functionality
o The client supports the drop function
o Error handling: if the user attempts to drop an object that is not currently
in their inventory, an error message is printed and the message is not sent
to the server
• Exit functionality
o The client supports the exit function. When the user types the command to
exit, the server connection is closed, a logout message is printed to the
user’s console, and the client-program exits
• Current State Display
o The client currently parses update messages from the server, updates the
information on the client-side, and displays this information to the user
o The client will print out current status information only when an update
message from the server indicates that the client’s status has changed