Uml sequence diagram if2/18/2024 ![]() ĭefines condition to a single call - the call will execute only if the supplied condition is true. altĭivides fragment into groups and defines condition for each group - only the one whose condition is true will execute. The following table provides guidance on the most useful operators, and their corresponding descriptions. For instance, in order to define that a call will execute only if a certain condition is true – we delimit the call with a fragment and use the operator ‘Opt’ to specify the condition. Interaction Operators (shown below) are used to characterize the fragment. ![]() The latter calls can be partitioned to groups (combined fragment) to show according to which condition each group will execute. With fragments we can delimit set of calls to show that they 1) execute only if a given condition is true 2) execute in a loop 3) run in parallel 4) reside within a critical section 5)etc. Using Interaction Frames (Combined Fragment)Īnother way of presenting control logic is using fragments (a.k.a interaction frames) together with Interaction Operators. The sequence bellow shows CarsManager that iterate though collection of Cars and execute a wash on each Car, which in turn delegate to the appropriate strategy according to the requested technique. Indeed, the activity diagram is more appropriate to model control logic that involves conditions, loop etc, but in practice, most developers prefer to stick with the sequence diagram to show how objects interact together with the control logic involved.Ī simple way of presenting conditions and loops is using simple notes. But for "simple" exception handling, I think a break is a better way to represent it, then alt.A common issue with sequence diagrams is how to show conditions and iterations. ConclusionĪs always, the best method depends on the scenario. This is ofcourse a very simple example, and you can have a lot more interaction in the break interaction operator, like logging or transaction handling. I think it even makes things better, because you can see where a sequence stops when an exception occurs. What I like about this way of displaying exception handling is that it makes the diagram much less cluttered. In this example the exception isn't caught until it enters the UI, in this case the ATM. Using a break interaction operator, it would look something like this: Let's take a look when the situation when something happens, what causes the ATM to decline de withdrawal. When the guard condition is true, the current interaction run is abandoned and the clause in the break interaction operand runs. The break interaction operator is similar to the break mechanism in other programming languages. This looks nice, for a small diagram, but once the diagram starts to grow and you get a lot of nested alt interaction operations, you might start to loose the overview. Using an alt interaction operator, it would look something like this: ![]() The else clause of the alternative combined fragment runs when no other option is selected. If there is no guard, the operand always runs when it is selected. However, as for any operand, the selected operand in the alternative structure runs only if the guard condition tests true. Only one of the offered alternatives runs on any pass through the interaction. The server confirms the withdrawal is approved and, the service passes this on to the ATM's UI and the ATM dispenses the money.Īn alternative interaction operator represents the logic equivalent of an if-then-else statement. The customer enters the data, the ATM calls a service, which calls the bank's server. I'll describe both methods using a classical example: withdraw money from an ATM when the balance is too low. They both use interaction operators, alt and break. 1Īfter searching for quite a while on how to model exception handling in a UML Sequence Diagram I found two ways to represent exception handling in a UML Sequence Diagram. There are several proposed notations for exception handling. Some clumsy approaches to model try-catch blocks are by utilizing combined fragments - alt (alternatives) and breaks, while adding stereotypes for reply messages representing thrown exceptions. UML provides neither notation to model exception handling in sequence diagrams nor any reasoning why it is absent. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |