Case 4 – Client-Server Computing
Think-Design-Write Test-Code
The command-response relationship for a client and a server.
- Description
Because you have done well your manager has assigned you permanently to work on the PRChat application team. Your team mates congratulate you and introduce you around. Shekar is the team lead. He assigns you to design and develop the data passing from the client to the server and the server to the client.
The requirements document says that this portion of the client/server relationship needs to be able to send a message to the server and store it. It also says that when the client starts up the user needs to login and received back all of the messages for that person that have been stored.
It also states that the client must be able to send multiple messages without reconnecting to the server once it is connected until a logout message is sent.
- Deliverables
- A UML use case for your solution
- A UML detailed use case for your solution
- A UML class diagram for your solution
- A UML State Diagram for the client and the server
- A working client and server
- A similar case including
- A presentation of your teams solution to the problem
- Resources
- sockets and the Knock Knock Server
- UML State Diagrams
- UML Use Case Diagrams
- UML Sequence Diagrams
- Diagram Descriptions
Document Type Description Level of Detail Use Case Diagram What can the user do? low Detailed Use Case Description How does the user do it? medium State Diagram How does the system change as the user uses it? low Sequence Diagram What objects, methods, and parameters does the system need to do it? high -
An example of a use case diagram for a bathroom shower
-
A state diagram showing the iterative nature of washing hair
-
A State diagram showing detailed actions within each state
-
An example of an iterative sequence diagram.
- detailed use case description template
- Java API: Socket, ServerSocket, PrintWriter, BufferedReader,InputStreamReader, InputStream, OutputStream, Class
- Visual Paradigm
