12/7/2023 0 Comments Draw sequence diagram in draw ioThis simplicity is even clearer in the next two diagrams that visualize what happens when a user performs a habit check-in – both the parallel execution and the two conditions are ignored. This is simply not visible in the communication diagram. In the example sequence diagram above, you can see a loop, where every habit’s history is fetched and displayed. They don’t represent iterations, conditionals or parallel operations, all of which are possible in the more complex sequence diagrams. UML communication diagrams are clearly much simpler than sequence diagrams – they help you focus on the function calls, the data passed between the different objects and roles and the basic sequence. UML communication diagrams only show messages Of course, the message it sends to itself is still numbered so you can see in which order all of the messages are sent. This relationship is indicated with a link ‘loop’. In the simple example below, both the communication diagram and its matching sequence diagram visualize one scenario (user interaction) in the Habit Tracker app – the example used throughout all of the UML diagram blog posts.Īs you can see in the communication diagram above, there are two functions that the user interface (UI) runs and sends messages “to itself”. You can clearly see which message belongs to which function call. The labels on these additional connectors should start with a number to indicates the sequence of the messages. Messages can be nested – simply use a decimal point 1.1, 1.1.2, etc. Indicate the sequence in the message labels
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |