![]() Once all the messages in the break combination have been sent, the sequence exits without sending any of the remaining messages (e.g., addDebitTransaction).Īn important thing to note about breaks is that they only cause the exiting of an enclosing interaction’s sequence and not necessarily the complete sequence depicted in the diagram. However, in cases where the balance is less than the amount, then the sequence enters the break combination fragment and its messages are sent. If the balance is not less than the amount, the next message sent is the addDebitTransaction message, and the sequence continues as normal. When the sequence gets to the return value “balance,” it checks to see if the balance is less than the amount. The figure below uses a break combination fragment since it treats the balance < amount condition as an exception instead of as an alternative flow. First, a break’s frame has a name box stating “break” instead of “option.” Second, when a break combined fragment’s message is to be executed, the enclosing interaction’s remainder messages will not be executed because the sequence breaks out of the enclosing interaction.īreaks are utilized to model exception handling. The break combined fragment is similar to the option combined fragment. ![]() If you do recall, back in the post called – The Basics & the Purpose of Sequence Diagrams ~ Part 2 – there was information on combined fragments known as “alternative,” “option,” and “loop.” While these combined fragments are what most people will utilize the most, there are other combined fragments, such as break and parallel, which a large share of people will find useful. While we did spend some time discussing Gates and its use or relevance to Sequence Diagrams, we now concentrate on just two elements known as Combined fragments. We got the final part of this series right here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |