Split diagram for better visibility

docs/src/08_concepts.adoc

@@ -93,10 +93,6 @@ class Role {
     + setName(name: String): void
 }
 
-class WiqEs04bApplication {
-    + main(args: String[]): void
-}
-
 interface PlayerService {
     + addNewPlayer(playerDto: PlayerDto): Player
     + getUsers(): List<Player>
@@ -155,6 +151,28 @@ class RoleDto {
     + name: String
 }
 
+Question "1" *- "1" Category
+GameSession "*" *-- "1" Player
+Role "*" - "*" Player
+PlayerService <|.. PlayerServiceImpl
+RoleService <|.. RoleServiceImpl
+PlayerService ..> Player
+RoleService ..> Role
+PlayerService ..> PlayerDto
+PlayerServiceImpl ..> PlayerRepository
+RoleServiceImpl .> RoleRepository
+RoleService ..> RoleDto
+PlayerRepository --|> CrudRepository
+RoleRepository -|> CrudRepository
+@enduml
+----
+
+[plantuml, domain-model-2, svg]
+----
+@startuml
+class WiqEs04bApplication {
+    + main(args: String[]): void
+}
 class CustomErrorController {
    + error(model: Model, webRequest: HttpServletRequest): String
 }
@@ -181,23 +199,9 @@ class CustomAuthenticationFailureHandler {
     + onAuthenticationFailure(request: HttpServletRequest, response: HttpServletResponse, exception: AuthenticationException): void
 }
 
-Question "1" *- "1" Category
-GameSession "*" *-- "1" Player
-Role "*" - "*" Player
-PlayerService <|.. PlayerServiceImpl
-RoleService <|.. RoleServiceImpl
-PlayerService ..> Player
-RoleService ..> Role
-PlayerService ..> PlayerDto
-PlayerServiceImpl ..> PlayerRepository
-RoleServiceImpl .> RoleRepository
-RoleService ..> RoleDto
-PlayerRepository --|> CrudRepository
-RoleRepository -|> CrudRepository
 @enduml
 ----
 
-
 === Hexagonal Architecture
 
 Our application is structured using hexagonal architecture principles, which prioritize the separation of core logic from peripheral concerns like user interface and external API interactions.