Team Project Summary 1---Requirements analysis and class diagram

The study of the soft-work course has just ended, and the first version of our small online game development has been completed. The development documentation was also completed and the teacher was asked to review to give some advice.

In the use Case Diagram section, we were previously divided into client and server use case diagrams, which were criticized by the teacher. Use case diagram is based on the customer's point of view, we have been unable to change the mindset, from the point of view of the code to divide the system into two parts, which is not right. Later we changed the use case diagram, divided into the player use case diagram, carrier use case diagram, database administrator use case diagram, operator-player use case diagram. Also must pay attention to the naming the specification, the verb noun can reflect the use case function.

Below, is the summary of the part I completed in the project

I and the crew Wang Yishao completed the game server design and improvement

1. Use case diagram

About the server, the customer is the operator, the database administrator. The operator runs and maintains the entire server, and the database administrator manages all registered player information.

2. Service-Side Overview design

• Initializing the network
• Receiving messages
• Processing messages

Hierarchy Chart

3. Detailed design of the service end

Class diagram

Class Diagram Description: The server's functional implementation is mainly implemented by three classes. Is the Client interface class Cnetwork, server function implementation class Cserver,

The database class that stores the data is Cado. Their functions and links are as follows:

1. Cnetwork: An interface class between a server and a client that accomplishes the transmission of messages between a client and a server through this class. This includes current user blood levels, XP and mana values, as well as current player status and chat information.
2. Cserver: The server functions the implementation class, including the calculation of the entire game running logic, receiving the currently connected player messages and processing forwarding this message.
3. Cado: Database class, complete the storage and query of player data. All registered player information is recorded.

Detailed level diagram: According to the divided subsystem, the Server subdivision module

　　

　　

Team Project Summary 1---Requirements analysis and class diagram