Create new class diagramms #9
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: lfk/org#9
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We really need to update our class diagramms and create some kind of static documentation repo.
Why?
Well the longer different people work on frontend and backend the higher the amount of problems created by misscommunications or beliveing something works in a way it doesn't.
And to be honest: That's not the fault of the party misunderstanding something or the fault of the party not realising that there is a missunderstanding.
For what?
Well missunderstandings will still occur, right?
Yes, but explaining something w/ documentation and a class diagramm at hand decreases the risk of explaining it in a way that is easy to missunderstand.
I Tried to generate a class diagramm for our entities.
See attached below.
I just generated a bunch of new class-diagramms for the backend (follwing r/n) :)