Hello. There is a database, and for it you need to make an ER-diagram. I’m about to wrap it up, but I’m not sure about the connections, namely where to put many to many, one to one, etc. Can you see, and in the case of an error prompt?

The base is used for the Help Desk coursebook. Ie each user with a certain level of rights (or status) logs in with his login and password, and makes a request in case of any malfunction.

Sample diagram

    1 answer 1

    1. Users should be combined into groups (many to many).
    2. For categories, you need permissions on user groups (many to many).
    3. The implementation of rights can be arbitrarily complex (or simple).
    4. There is not enough history of applications for the life cycle, by performers, etc. It can be implemented as system and user comments (one to many).
    5. There can be several performers in principle.
    6. The hierarchy of applications.
    7. The life cycle is a graph. For each category of its own.
    8. Categories - Hierarchy
    9. If necessary, the date of creation, deadline, acceptors, labor costs ...

    More:

    • Comment in applications
    • Status in applications (current status should be taken from history)
    • What is the status of users is not entirely clear

    Threat If this is a training task, cut off the excess, take what you need.

    • Thanks for the answer. I have to do it with such a base. That is, in fact, the base is already there, and you just need to make an ER diagram for it. I understand correctly that on my scheme all the connections will be one to one? Nr: one user can have only one status (or level of rights), or one application can have only one life cycle - ExzoTikFruiT
    • @ExzoTikFruiT, apparently, one to one. - Yura Ivanov