01. doc object - MuchChaca/KelKannes GitHub Wiki
UML
Use-case diagram

Class diagram
Very "straight forward" minded

A few clarifications
In deed, it is not very clear on this picture, but there are actually 3 associations, which are defined like so:
- A user can be the
chauffeuron manyticketsbut atickethas a singlechauffeur - A user can be the
coupeuron manytickets` but atickethas a singlecoupeur`` - A user can be the
chargeuron manyticketsbut atickethas a singlechargeur
This might not be fully updated, please refer to doc/sql from the source code.