![]() The diagram's purpose The sequence diagram is used primarily to show the interactions between objects in the sequential order that those interactions occur. Or you could use state machine diagram to track the mutation of the user - the UML vocabularly is rather large, so no need to limit yourself just to one type. Please note, again, that the examples provided below are based on the new UML 2 specification. That being said, UML has interaction overview diagrams ( ), that allow you sow together various diagrams, so you could split it into two, and then just connect them differently. That way you wouldn't need to worry about connecting the two diagrams as they are really not that dependent. second diagram takes as an input unverified user and produces a verified user The canonical case is a UML Sequence Diagram (where the notation comes from), which represents the messages exchanged between objects in a software system.first diagram takes as an input unregistered user and produces a unverified user Traffic Light Example with Hierarchy for Sequence Diagrams The traffic signal cycles from green to yellow to red.In your particular example, breaking it into (at least) two sequence diagrams would be a good option, as both those activities are usually performed at different times. If you are doing it for documentation / informing purpose then clarity should be your priority. The best way to understand sequence diagrams is to look at some examples of sequence diagrams. 247 of the UML User Guide, illustrates the dynamic creation and destruction of objects, an object. Generally speaking the smaller diagram, the better. 2 I am trying to build a sequence diagram where I show that a user can: Log in to an application if their details are correct. The following diagram, based on the one appearing on p. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |