简体繁体 English

登录和注册android应用程序的序列图

[英]Login and register sequence diagram for android application

原文 2016-05-02 19:47:47 6 1 java/ database/ uml/ diagram/ sequence-diagram

When the user logs in using the Login activity their information is checked in a database. 当用户使用登录活动登录时，将在数据库中检查其信息。 A response is then send to the Login activty telling the user if their login attempt has been successful. 然后，响应将发送到Login activty，告知用户他们的登录尝试是否成功。

When a new user registers, the data they enter is validated in the Register activity. 当新用户注册时，他们输入的数据将在Register活动中得到验证。 Their information is then send to the database. 然后将他们的信息发送到数据库。 The database will then send a response letting them know if it was successfully entered. 然后，数据库将发送一个响应，让他们知道它是否已成功输入。

Is this the correct way to illustrate these actions in sequence diagrams? 这是在序列图中说明这些操作的正确方法吗？

1 个解决方案

The vertical lifelines typically do not represent activities, they typically represent instances of classes. 垂直生命线通常不表示活动，它们通常表示类的实例。 (Yes, it is syntactically possible in UML to use an activity, but it is a very strange thing to do.) Those instances are usually typed by classes or interfaces that either have operations or signal receptions that can be invoked via messages. （是的，在UML中在语法上可以使用一个活动，但这是一件非常奇怪的事情。）这些实例通常由具有可通过消息调用的操作或信号接收的类或接口类型化。 Moreover, in UML, there is no message kind that has a white arrowhead. 而且，在UML中，没有具有白色箭头的消息类型。

Therefore, no, those diagrams are not quite the correct way to illustrate the actions in a sequence diagram. 因此，不，这些图表不是用于说明序列图中的动作的正确方法。