mirror of
https://github.com/kevinveenbirkenbach/infinito.git
synced 2024-12-04 23:17:19 +01:00
Implemented UML class diagram for domain request management
This commit is contained in:
parent
5e601df541
commit
bffb5c18b2
Binary file not shown.
File diff suppressed because it is too large
Load Diff
After Width: | Height: | Size: 244 KiB |
@ -1,11 +1,11 @@
|
||||
# Request Management
|
||||
The request management works with different layers.
|
||||
|
||||
### Layers
|
||||
## Layers
|
||||
Each layer contains out of __2 classes__ and __2 interfaces__ for it.
|
||||
One class contains the __logic__ and the other class contains the __service__. This makes the classes easier testable and mockable and follows the [SOLID Design Principles](https://en.wikipedia.org/wiki/SOLID).
|
||||
|
||||
#### Entity
|
||||
### Entity
|
||||
A **requested entity** contains the attributes to manage the entity which should be handled by an action
|
||||
#### Right
|
||||
This is the basic request layer from which the other layers inhiere. A **requested right** contains a **requested entity**.
|
||||
@ -14,3 +14,7 @@ This is the basic request layer from which the other layers inhiere. A **request
|
||||
A **requested user** is a parent of **requested action** and contains out of one **requested right**.
|
||||
#### Action
|
||||
A **requested action** inhieres from **requested user** and contains a **requested user**.
|
||||
|
||||
## UML Class Diagram
|
||||
The following diagram shows the relations between the different request layers and services:
|
||||
![UML Class Diagram](.meta/uml-class-diagram.svg)
|
||||
|
Loading…
Reference in New Issue
Block a user