Team Project-requirement and UML diagram-change

Because the actual results of the previous solution were not satisfactory and did not match the initial project reported to the teacher, I switched to the original idea here to continue the game. We still plan to use the unity engine for development, but due to the characteristics of one stroke, this finished product should be a 2D horizontal version of the platform to solve the puzzle class game, the following project is the demand and UML diagram.

Requirements:

1. The game world is a 2D horizontal scroll

2. The main character is riding a motorcycle in a single direction in the game world (no retreat, orientation unchanged)

3. Similar to reality, motorcycles can only be driven on the ground (not float)

4. scenes in the gaming world are composed of the starting point, platform, agency, and terminal.

5. In a level, players start from the start point and arrive at the end point as a victory

6. In a level, a role (not including a motorcycle) is killed when it is hit by an attack authority (in case of a collision). This function is regarded as a failure.

7. In a level, if a role (not including a motorcycle) collides with the platform, it is deemed to have died.

8. Players can use the keyboard to manipulate the horizontal movement of the motorcycle (acceleration and brakes)

9. Players can use the keyboard to manipulate the rotation of motorcycles in the air (clockwise and counterclockwise)

10. Players draw tracks in the game world with their mouse and are considered as platforms (on which to drive)

11. Within a level, the length of a player's track is limited.

12. Within a level, players can draw only one track.

13. The above is not the final requirement and may change at any time

UML diagram:

Class diagram:

Since we use unity for development, we use multiple built-in unity classes. Here, we only detail the detailed members and types of custom classes, while the built-in classes are omitted.

(Built-in classes include but are not limited to gameobject, rigidbody2d, collider2d, monobehaviour, vector3, audioclip)

Use case diagram:

The use case diagram consists of two systems: The Menu System and the game master system. The menu system is responsible for setting and viewing the corresponding in-game settings. The main game system is responsible for rendering the screen, calculating the physical effect, and managing the running logic.

 

Status chart:

The status chart here is not a status chart of a specific class. Because the unity engine encapsulates the chart, we cannot see the actual class and internal running sequence of the Main Loop of a specific game, therefore, the status chart is drawn from the user (player) perspective based on the game process.

 

Team Project-requirement and UML diagram-change