Best practices for logging user actions in production I was planning on logging a lot of different stuff in my production environment, things like when a user: Logs In, Logs Off Change Profile Edit Account settings Change password etc Is this a g
My use case diagram is a mess. What can I do? In a computer based interaction this means two primary actors don't actually touch the same use case unless there is some kind of symmetric chat involved (unlikely) For human face to face relations it's different, you do have two actors interacting, but over under the counter w r t to a computer system that would implement the exchange
design - How to model two-step Login in UML via Use Cases and Sequence . . . A use-case is an interaction between an actor and a system, where the actor uses the system to achieve a goal In your example, "login" is a proper use-case, but all the others are not They are just steps that are taken as part of the "login" use-case For a correct use-case diagram, you can just erase everything to the right of the "login
UML sequence diagrams - Software Engineering Stack Exchange I'm currently doing my OCPJEA assignment I have to draw several sequence diagrams for the use cases presented in the documentation One of the use cases (A) state that after some interaction, the
database as distinct operations in the Use Case diagram Try to avoid having "logging in" as the central or prominent focus of materials related to user interactions, unless it is specifically about logging in Whilst access control is an important application design feature, establishing a login session is usually an overarching process that precedes all other user interaction, and is typically perceived by users as being a fully-routine overhead
Should I use HTTP status codes to describe application level events The HTTP interaction itself--the request response forms, status codes, and so on--is mostly an affair of how to request, serve, and render arbitrary content as efficiently as possible, without getting in the way