UML Diagram design of team project

• Team

member	Participation	Contribution ratio
031602406 Cheng (temporary leader)	Entity Relationship Diagram Design	11
031602501 CAI Aerospace	Entity Relationship Diagram Design	8
051501124 Wang Bin	Class diagram Design	8
031602438 ye Yi Fan	Class diagram design, swimlane map design	13
031602407 He Jia Jian	Activity diagram Design	9
031602410 Yellow Tides	Activity diagram Design	9
031602429 Wang Jinyang	State diagram design, timing diagram design	12
031602442 Zheng Kongyu	State diagram Design	10
181600215 Lin Xiang Yu	Use case diagram Design	10
031602421 Lin Shijie	Use case diagram Design	10

• UML diagram
• Part1
• What part of the system is described here?
  • This section mainly describes the system backend, users, photos, comments and mood features of the content
• What kind of problems will this part face?
  • The information intersection of each function is more, there is redundancy of information
• What issues are addressed in the following designs?
  • Clarify business processes and reduce back-end coupling levels

• Attached: Class diagram
  

• Part2
• What part of the system is described here?
  • This section mainly describes the user function selection and jump.
• What kind of problems will this part face?
  • Activity entry, exit, jump.
• What issues are addressed in the following designs?
  • Clarify function distribution, more intuitive display function entry, exit, jump.

• Attached: State diagram
  

• Part3
• What part of the system is described here?
  • Here is a use case diagram of the Travel Records Management System section
• What kind of problems will this part face?
  • This section will address the issue of how to manage user travel records and how users can edit travel records.
• What issues are addressed in the following designs?
  • The following design lists the management logic of travel records, users can add a new record and three categories by text, picture, video to see the existing records. For adding records, support for adding text, images, and videos. Users can save or delete existing records after they have finished editing.

• Attached: Use case diagram 1
  

• Part4
• What part of the system is described here?
  • Here is a use case diagram of the Travel records sharing System section.
• What kind of problems will this part face?
  • This section will face the question of how users share and share what functions.
• What issues are addressed in the following designs?
  • The following design lists three forms of user-generated sharing: The user can select a series of travel records to generate a travel story, or to connect the places they've been to to create a road map, or to label the places they've gone to to create a travel map. When users share, others can click to comment.

• Attached: Use case diagram 2
  

• Part5
• What part of the system is described here?
  • Here is a use case diagram of the User Center and the Travel recommendation System section.
• What kind of problems will this part face?
  • This part will face the user login management, user information maintenance and how to recommend the location of the problem.
• What issues are addressed in the following designs?
  • The following design lists basic login exits and user information maintenance features. Users can view and modify personal information to send feedback. For tourist location recommendations, you can choose to recommend nearby locations or, depending on past travel preferences, recommend the next place to visit.

• Attached: Use case diagram 3
  

• Part6
• What part of the system is described here?
  1. View different map layouts and personal information sections
  2. Record text, photos, videos and generate travel short story sections
  3. View user information and system Information and provide feedback section
  4. Generate travel story sections for each time period
  5. Share different versions of the route map section
  6. Based on the information generated near and next tour location part
• What kind of problems will this part face?
  • Features that contain more than a few parts, as well as the functionality of each part, are broken down, making it difficult to sort out the processes of each part and the linkage of each function and the combination of parts.
• What issues are addressed in the following designs?
  -After the design of the activity diagram, it is clear and intuitive to embody the entire operation of the activity flow, understand the division into different parts, and the various parts contained in the specific functions and functions.

• Attached: Activity diagram
  

• Part7
• What part of the system is described here?
  • This section mainly describes the information requirements and the type of data information stored in the database.
• What kind of problems will this part face?
  • Clarify the relationship between real entities and visually describe the entity attributes and the relationships between entities.
• What issues are addressed in the following designs?
  • Facilitate the analysis of requirements and facilitate the storage of database information

• Attached: E-r chart
  

• Part8
• What part of the system is described here?
  • The relationship between the administrator, the user, and the backend.
• What kind of problems will this part face?
  • Different role permissions, functional induction
• What issues are addressed in the following designs?
  • Get a better understanding of role relationships and more safe and convenient interactions

• Attached: Swimlane map

• Part9
• What part of the system is described here?
  • The sequence of functions jumps and returns.
• What kind of problems will this part face?
  • There may be confusion between features
• What issues are addressed in the following designs?
  • Resolves the problem of functional order confusion

• Attached: Timing diagram
  

• The feeling of changing team classmates
  The third group has a good working range, and there is no dispute at the same time. Team leader directly through the QQ group release tasks, simple straightforward. The driving force is very high, after the delivery of the mission, everyone began to do their own tasks, and before the deadline was submitted on time. The temporary captain may be the reason for the lack of maturity, and we ask for less.

UML Diagram design of team project