kevinveenbirkenbach/infinito
1
0
Fork 0
mirror of https://github.com/kevinveenbirkenbach/infinito.git synced 2025-04-16 10:16:22 +02:00
Code Issues Packages Projects Releases Wiki Activity

Implemented UML class diagram for domain request management

Browse Source
This commit is contained in:
Kevin Frantz 2019-02-12 22:13:32 +01:00
parent 5e601df541
commit bffb5c18b2
3 changed files with 2288 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
application/symfony/src/Domain/RequestManagement/.meta/uml-class-diagram.dia Normal file
View File

Binary file not shown.

2282
application/symfony/src/Domain/RequestManagement/.meta/uml-class-diagram.svg Normal file
View File

File diff suppressed because it is too large Load Diff
Side by Side

After

Width:  |  Height:  |  Size: 244 KiB

8
application/symfony/src/Domain/RequestManagement/README.md
View File

@ -1,11 +1,11 @@
# Request Management # Request Management
The request management works with different layers. The request management works with different layers.
### Layers ## Layers
Each layer contains out of __2 classes__ and __2 interfaces__ for it. 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). 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 A **requested entity** contains the attributes to manage the entity which should be handled by an action
#### Right #### Right
This is the basic request layer from which the other layers inhiere. A **requested right** contains a **requested entity**. 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**. A **requested user** is a parent of **requested action** and contains out of one **requested right**.
#### Action #### Action
A **requested action** inhieres from **requested user** and contains a **requested user**. 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)