But I don’t think that you want to say that the Admin will always do all these actions and in this precise order. This diagram says that the Admin will login, then edit a user, the view a user, then delete a user. Ports of the encloser may be shown separately even when self is included. This diagram shows too much and in a misleading way. The following image is part of the registration process, would any one take a look and correct me if I did any mistake. It's confusing to me because this is the first time I use this technique with a real project. The web application obtains an access token instead of using Facebook user credentials to access protected resources. Can you represent a port as a lifeline in UML sequence diagram In section '17.3.4.1 Lifeline' of UML Specification 2.5.1, it writes: 'If the name is ‘self’, then the Lifeline represents the object of the classifier that encloses the Interaction that owns the Lifeline. 1 I'm preparing the sequence diagram for a project. Without the context it will be misleading, but with knowing it you explain certain details. A diagram is a certain view on some part of your model. You must not include every bit in a SD (or any other UML diagram). Facebook uses the OAuth 2.0 protocol framework, which enables web applications (called "clients") that are not normally Facebook resource owners but represent Facebook users to request access to resources controlled by Facebook users and hosted by Facebook servers. Simply spoken: if your diagram is confusing the reader it's of no help and not of worth. This is an example of a UML sequence diagram, which shows how to authenticate Facebook users in a web application to allow access to their Facebook resources. This creates a Hibernate session behind the background interceptor and starts a Hibernate JDBC transaction, so the business method will run in the context of the new transaction.Įxample2: Facebook User Authentication Sequence Diagram When a certain business method is called, Spring Transaction Interceptor may intercept it. The Spring application development framework for enterprise Java integrates Hibernate transaction management. Here, we provide an example of a UML sequence diagram that illustrates transaction management related to exception handling. Example1: Spring and Hibernate Transaction Sequence Diagram
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |