$$ Players send units to attack the enemy$$s fortress, which is executed by the units

autonomously. $($Use Case: Attack Opponent$)$

$$ The game concludes either when the time is up$,$ or a player$$s score hits the

winning point. $($Use Case: End Game$)$

$$ The game announces the winner based on the final score and updates the players'

records. $($Use Case: Declare Winner$)$

$$ Players exit to the main menu or close the game entirely after a match concludes.

$($Use Case: Leave Game$)$

$3.$ Use Case Descriptions

Use Case Name: Authentication

Actors: Players, Game Server

$1.$ Players open the game and are asked to login$.$

$2.$ Players enter their credentials.

$3.$ The Game Server verifies the credentials.

$4.$ Once the verification is successful, players are granted access to the game lobby.

Use Case: Incorrect Login

Actors: Players, Game Server

Related Use$-$Case: Authentication

Extension$-$Of: Extension Point occurs at Step $3$

If the credentials are incorrect:

$1.$ Players receive an error message.

$2.$ Players can attempt to log in again or reset their password.

Use Case Name: Join Game

Actors: Registered Player, Game Server

$1.$Registered players select 'Join Game' from the lobby.

$2.$The Game Server places the player in a suitable game session.

$3.$The game session starts on the player's client.

Entry Condition:

$$ Players are authenticated.

Use Case Name: Resource Collection

Actors: Players

$1.$ Players select a unit.

$2.$ Players command the unit to collect resources.

$3.$ Units collect and return resources to the player's inventory.

Use Case Name: Build Defense

Actors: Players

$1.$ Players select a building option.

$2.$ Players place the defense on the game map.

$3.$ Units construct the defense.

Use Case Name: Soul$-$Cast

Actors: Players

$1.$ Players open the Soul$-$Casting menu.

$2.$ Players select the unit to create.

$3.$ Units are created and placed in the player's area.

Entry conditions:

$$ Players have the required resources.

Use Case Name: Assign tasks.

Actors: Players

$1.$ Players select a unit.

$2.$ Players assign a specific task to the unit.

$3.$ Units begin executing the assigned task.

Entry conditions:

$$ Units are available for task assignment.

Use Case Name: Reassign Tasks to Units

Actors: Players

$1.$ Players select an active unit.

$2.$ Players assign a new task to the unit.

$3.$ The unit switches to the new task.

Use Case Name: Display unit progress.

Actors: Game

$1.$ Units perform tasks such as resource collection or defense construction.

$2.$ The game updates the progress indicators for each task.

$3.$ Players receive visual feedback on unit activity.

Use Case Name: Attack opponent.

Actors: Players

$1.$ Players select units.

$2.$ Players command units to attack an opponent.

$3.$ Units engage in combat with the opponent.

Use Case Name: End Game

Actors: Game

$1.$ The game monitors the session time and player scores continuously.

$2.$ The game concludes when the session time expires or a player's score reaches the set

point for the victory.

$3.$ The game server updates all session states to reflect the end of the game.

Entry conditions:

$$ At least one player is in an active game session.

Use Case:

Actors: Players, Game

Related Use$-$Case: End Game

Extension$-$Of: Extension Point occurs at Step $3$

if a player reaches the winning score before time expiration:

$1.$ The game immediately proceeds to declare the winner.

If the session time expires without any player reaching the winning score:

$2.$ The game checks for the highest score.

$3.$ If there is a tie, the game may enforce additional conditions to determine the winner.

Use Case Name: Declare Winner

Actors: Game

$1.$The game evaluates the final scores of the players.

$2.$The player with the highest score is identified as the winner.

$3.$The game displays the victory announcement and updates the players' records

accordingly.

Entry conditions:

$$ The game session has ended.

Use Case Name: Leave Game

Actors: Players

$1.$ Players receive the end$-$game summary screen.

$2.$ Players select the option to leave the game session.

$3.$The game server processes the request and directs the player to the main menu or

closes the game application

Implement the Class Diagram of this system i just provided, and note that we are using papyrus environment for this.