33

Product owner:

Okay we have users and groups. Users have roles, roles have permissions, but groups can also have roles or permissions. Clients have users and these client-users can have special kinds of permissions. Now we need to add projects which have pages and special project users who manage the projects, but only the client-users can set rights for which project owners can manage pages. Pages are coupled to roles, and assigned to workflows, unless the client-user already had the permission to... wait where are you going?"

Me: "Fetching a new SSD. I ran out of hard disk space trying to model the database design. Could you please start from the top when I get back?"

Comments
  • 2
    I did something very similar to that once, but it also included employee info
  • 3
    @AlexDeLarge Except this is like 5% of the total plan, and it includes so many permission management pages and groups within groups within groups, that the users will probably need a 2-week bootcamp before they can even start using the product.

    This is what happens when a product plan grows a bit too "organically". Someone decides that Bob the intern shouldn't see page x but must be able to click button y, and that his manager should be able to set permissions, but not all permissions, so there are permissions which determine who can set which permissions, etc.

    The meta-ness of the layers would impress me, if I didn't have to build it.
  • 1
    UML is your friend. Helping communication for decades
  • 1
    Product owner: We also need it to be written in assembly.
  • 0
Add Comment