The database responds and the user is either allowed to enter the site or not. This page in turn sends those credentials to the database that stores user information. If not, you will usually get a response telling you to try again.įrom the point of view of the sequence diagram, the user is the first active object and sends credentials to the login page. If everything is correct, you get cleared to enter the site. The server will then run some complicated algorithms to check whether you have submitted the correct password. You enter your data and submit the form, and this is when the sequence diagram kicks in and shows how useful it can be.Īssuming you have filled in both the username/email address and password, the server will first check that the username exists in the system. This is often just your email address and a password. Once the page has loaded, you’re usually presented with a form that allows you to enter your credentials, or in other words the information that you used to sign up for the site. So what actually happens when you arrive on the login page for your favorite website? That’s exactly what a sequence diagram is designed to show. Behind the scenes, any login page involves messages being sent back and forth, objects being activated, and responding with data, and it happens over a discrete period of time. How can you create a sequence diagram for a login system?Ī great example of sequence diagrams is a user login system. For much more detail, you should check out our sequence diagram page on Gleek. That gives you an overview of what to expect from a sequence diagram. The arrows are usually labeled so that you can easily understand the content of the message.
Messages can be sent back and forth, from left to right, and the arrow shows which is the receiver and which the sender of the message. These messages are represented by a line with an arrow. Activity in the system is shown by messages that pass between the objects.
0 kommentar(er)
