Modeling Dynamic Behavior

Transcription

1 Dr. Michael Eichberg Software Engineering Department of Computer Science Technische Universität Darmstadt Software Engineering Modeling Dynamic Behavior The following slides use material from: Craig Larman; Applying UML and Patterns, 3rd Edition; Prentice Hall

2 UML Interaction Diagrams Two types of diagrams can be distinguished: UML Sequence Diagrams UML Communication Diagrams

3 UML Interaction Diagrams - Introduction 3 Interaction diagrams are used to visualize the interaction via messages between objects; they are used for dynamic object modeling.

4 UML Interaction Diagrams - Introduction 4! Modeling the dynamic behavior is often more rewarding w.r.t. understanding the domain than modeling the static structure.

5 Four types of interaction diagrams are available. UML Interaction Diagrams - Introduction 5 Sequence diagrams (which use a fence format.) Communication diagrams (which use a graph or network format) Timing diagrams (not discussed) :A myb:b do1 do2 do3 E x a m p l e Interaction overview diagrams (not further discussed)

6 Four types of interaction diagrams are available. UML Interaction Diagrams - Introduction 6 Sequence diagrams (which use a fence format.) Communication diagrams (which use a graph or network format) Timing diagrams (not further discussed) Interaction overview diagrams (not further discussed) do1 :A E x a m p l e 1: do2 2: do3 myb:b

7 Java Code for Interaction Diagrams UML Interaction Diagrams - Introduction 7 do1 :A myb:b do2 do3 E x a m p l e Sequence Diagram public class A { private B myb =...; } public void do1() { myb.do2(); myb.do3(); }

8 Java Code for Interaction Diagrams UML Interaction Diagrams - Introduction 8 do1 :A E x a m p l e 1: do2 2: do3 myb:b Communication Diagram public class A { private B myb =...; } public void do1() { myb.do2(); myb.do3(); }

9 Java Code for Interaction Diagrams UML Interaction Diagrams - Introduction 9 :A myb:b do2 do1 :A do3 1: do2 2: do3 E x a m p l e myb:b public class A { private B myb =...; } public void do1() { myb.do2(); myb.do3(); }

10 Common Notations for UML Interaction Diagrams UML Interaction Diagrams - Introduction 10 :Sale Lifeline box representing an unnamed instance of class Sale.

11 Common Notations for UML Interaction Diagrams UML Interaction Diagrams - Introduction 11 s1:sale Java Code: Sale s1 = ; Lifeline box representing a named instance (s1) of Sale.

12 Common Notations for UML Interaction Diagrams UML Interaction Diagrams - Introduction 12 «metaclass» Font Java Code: Class<Font> fontclass = Font.class; Lifeline box representing the class Font, or more precisely, that Font is an instance of class Class - an instance of a metaclass.

13 Common Notations for UML Interaction Diagrams UML Interaction Diagrams - Introduction 13 sales:arraylist<sale> Java Code: ArrayList<Sale> sales = ; Lifeline box representing an instance of an ArrayList class, parameterized to hold Sale objects.

14 Common Notations for UML Interaction Diagrams UML Interaction Diagrams - Introduction 14 Java Code: sales[i]:sale ArrayList<Sale> sales = ; Sale sale = sales.get(i); Lifeline box representing one instance of class Sale, selected from the sales ArrayList<Sale> collection.

15 Common Notations for UML Interaction Diagrams UML Interaction Diagrams - Introduction 15 :Sale s1:sale «metaclass» Font sales:arraylist<sale> sales[i]:sale O v e r v i e w

16 Common Notations for UML Interaction Diagrams - Format for Interaction Messages UML Interaction Diagrams - Introduction 16 Commonly Used Grammar: return = message(parameter:parametertype):returntype Parentheses are usually excluded if there are no parameters. Type information may be excluded if unimportant. initialize(code) initialize d = getproductdescription (id) E x a m p l e s d = getproductdescription (id : ItemId) d = getproductdescription (id : ItemId) : ProductDescription The same syntax is used by, e.g., the Scala programming language.

17 UML Sequence Diagrams

18 Modeling (Synchronous) Messages UML Sequence Diagrams 18 a found message whose sender will not be specified typical synchronous message shown with a filled-arrow line report execution specification bar indicates :Register getdate :Sale focus of control (optional) dt. Ausführungssequenz tostring getregno

19 Modeling (Synchronous) Messages UML Sequence Diagrams 19 a found message whose sender will not be specified report execution specification bar indicates focus of control (optional) UML Superstructure If the Message represents a CallAction, :Register getdate dt. Ausführungssequenz tostring getregno typical synchronous message shown with a filled-arrow line there will normally be a reply message from the called Lifeline back to the calling :Sale lifeline before the calling lifeline will proceed.

20 Self messages can be modeled using nested execution specification bars. UML Sequence Diagrams 20 canceltransaction :Register self message log

21 To show the return value of a message you can either use the message syntax (A) or use a message line at the end of an execution specification bar (B). execution specification bar =dt. Ausführungssequenz UML Sequence Diagrams 21 report :Register thereport = report :Sale Variant A report Variant B :Register :Sale report thereport

22 Object Instance Creation UML Sequence Diagrams 22 :Register makepayment(cashtendered) :Sale Newly created objects are placed at their creation height. create(cashtendered) :Payment authorize The name create is an UML idiom; it is not required.

23 Object Instance Destruction UML Sequence Diagrams 23 :Register makepayment(cashtendered) :Sale create(cashtendered) :Payment... X Not strictly required by the UML. The object destruction notation is also used to mark objects that are no longer usable.

24 Invoking Static Methods (Class Methods) UML Sequence Diagrams 24 report :Register locales = getavailablelocales Calendar Beware, other notations are also used (e.g. underlined method names).

25 Invoking Static Methods (Class Methods) UML Sequence Diagrams 25 report :Register locales = getavailablelocales Calendar public class Register { public void report() { Locale[] locales = Calendar.getAvailableLocales(); } } Corresponding Java Code

26 Diagram frames in UML sequence diagrams are used to support - among others - conditional and looping constructs. Frames have an operator and a guard. Diagram Frame ~dt. Fragment UML Sequence Diagrams 26 :Sale lineitems[i] : SalesLineItem t = gettotal loop [0 < i < lineitems.size] i++ st = getsubtotal E x a m p l e

27 How to model the iteration over a collection? UML Sequence Diagrams 27 Modeling task: Calculate the total of a sale by summing up the sub totals for each sales line item.

28 Use a UML loop frame to iterate over a collection. UML Sequence Diagrams 28 :Sale lineitems[i] : SalesLineItem t = gettotal loop [0 < i < lineitems.size] st = getsubtotal i++ Modeling task: Calculate the total of a sale by summing up the sub totals for each sales line item.

29 Use a UML loop frame to iterate over a collection. UML Sequence Diagrams 29 :Sale lineitems[i] : SalesLineItem t = gettotal loop [for each sales line item] st = getsubtotal Modeling task: Calculate the total of a sale by summing up the sub totals for each sales line item.

30 Java code corresponding to a UML loop frame. UML Sequence Diagrams 30 :Sale lineitems[i] : SalesLineItem t = gettotal public class Sale { private List<SalesLineItem> lineitems = new ArrayList<SalesLineItem>(); loop [for each sales line item] st = getsubtotal public Money gettotal() { Money t = new Money(); Money st = null; for (SalesLineItem lineitem : lineitems) { st = lineitem.getsubtotal(); t.add(st); } return t; } } Modeling task: Calculate the total of a sale by summing up the sub totals for each sales line item.

31 How to model the sending of a message only if a guard condition matches? UML Sequence Diagrams 31 Modeling task: Get the sum of all sales that happened today after 18:00 o clock.

32 Use a UML opt frame to model the sending of a message if the guard condition matches. UML Sequence Diagrams 32 :Register sales[i] : Sale r = gettotal(startdate) loop [for each sale] date = getdate opt [startdate < date] t = gettotal Frames can be nested. Modeling task: Get the sum of all sales that happened today after 18:00 o clock.

33 How to model mutually exclusive alternatives? UML Sequence Diagrams 33 Modeling task: A register should be able to handle credit card payments and cash payments.

34 Use the UML alt frame to model between 2 and n mutually exclusive alternatives. makepayment(type,sale) :Register UML Sequence Diagrams 34 alt [type = CreditCardPayment] create :CreditCardPayment [type = CashPayment] create :CashPayment Modeling task: A register should be able to handle credit card payments and cash payments.

35 Diagram frames in UML sequence diagrams are used to support - among others - conditional and looping constructs. makepayment(type,sale) :Register UML Sequence Diagrams 35 alt [type = CreditCardPayment] create In general, sequence diagrams [type = CashPayment] create :CreditCardPayment are not really well suited to show looping and conditional behavior. Activity diagrams and code may be alternatives. :CashPayment Modeling task: A register should be able to handle credit card payments and cash payments.

36 An interaction occurrence (interaction use) is a reference to an interaction within another interaction. UML Sequence Diagrams References are used to simplify a diagram and factor out a portion into another diagram or to enable reuse. 36 Modeling task: We want to calculate the store s overall total. interaction occurrence ~dt. Interaktionsauftreten

37 An interaction occurrence (interaction use) is a reference to an interaction within another interaction. UML Sequence Diagrams 37 :Register sales[i] : Sale r = gettotal(startdate) loop [for each sale] date = getdate opt [startdate < date] t = gettotal given

38 An interaction occurrence (interaction use) is a reference to an interaction within another interaction. sd = sequence diagram UML Sequence Diagrams 38 sd CalculatePerRegisterTotal r = gettotal(startdate) :Register sales[i] : Sale loop [for each sale] date = getdate opt [startdate < date] t = gettotal given

39 An interaction occurrence (interaction use) is a reference to an interaction within another interaction. UML Sequence Diagrams 39 sd CalculatePerRegisterTotal r = gettotal(startdate) :Register sales[i] : Sale loop [for each sale] date = getdate opt [startdate < date] t = gettotal

40 An interaction occurrence (interaction use) is a reference to an interaction within another interaction. UML Sequence Diagrams 40 :Store :Register sales[i] : Sale mr = managementreport r = gettotal(startdate) ref CalculatePerRegisterTotal...

41 How to model the sending of asynchronous messages? How to model objects that have their own thread of execution? UML Sequence Diagrams 41 Modeling task: The log information should automatically be collected and processed in the background.

42 Asynchronous messages are messages that don t block. An active object is an object where each instance runs on and controls its own thread of execution. UML Sequence Diagrams 42 create :Register Active objects are modeled using double vertical lines on the left and right side of the lifeline boxes. create :LogManager run Asynchronous messages are shown using stick arrows. Modeling task: The log information should automatically be collected and processed in the background.

43 UML Communication Diagrams

44 Links and Messages in Communication Diagrams UML Communication Diagrams 44 A link is a connection path between two objects (it is an instance of an association) A link indicates that some form of navigation and visibility between the objects is possible. Each message between objects is represented with a message expression and a small arrow indicating the direction of the message Sequence numbers are added to show the sequential order of messages in the current thread of control; the starting message is often not numbered. makepayment 1: makepayment(cashtendered) :Register 2: gettaxes 2.1. getdate :Sale

45 Links and Messages in Communication Diagrams Modeling self messages UML Communication Diagrams 45 makepayment :Register 1: verify

46 Alternative Notations for Modeling Instance Creation UML Communication Diagrams 46 Create message, with optional initializing parameters. This will normally be interpreted as a constructor call. :Register 1: create(cashier) :Sale :Register 1: create(cashier) :Sale{new} :Register «create» 1: make(cashier) :Sale If an unobvious creation message name is used, the message may be stereotyped for clarity.

47 Message Number Sequencing The initial message ist not numbered to make the numbering easier to comprehend. UML Communication Diagrams 47 second message third message i_msg 1: j_msg :A :B first message 2: n_msg 1.1: k_msg 2.1: l_msg :C fifth message forth message 2.2: m_msg :D sixth message

48 Modeling Conditional Messages UML Communication Diagrams 48 msg :E 2: msg6 Small letters are sometimes used to mark methods that are executed in parallel. 1a [test1]: msg2 :A :B 1b [not test1]: msg4 1a.1: msg3 :D 1b.1: msg5 :C The message is only sent if the condition evaluates to true. The condition is written in square brackets. In case of modeling mutually exclusive message conditional path letters are prepended.

49 Messages to Class Objects UML Communication Diagrams 49 makepayment :Sale 1: locs = getavailablelocales «metaclass» Calendar e.g. to format the date as either 3/2/2009 or

50 UML Communication vs. UML Sequence Diagrams

51 Strengths and Weaknesses Interaction Diagrams UML Interaction Diagrams 51 Type Strengths Weaknesses Sequence Diagram clearly shows sequence or time ordering of messages large set of detailed notation options - forced to extend to the right when adding new objects; consumes horizontal space Communication Diagram space economical - flexibility to add new objects in two dimensions - more difficult to see sequence of messages - fewer notational options

52 Strengths and Weaknesses Interaction Diagrams UML Interaction Diagrams 52 Type Strengths Weaknesses Sequence Diagram Communication Diagram clearly shows sequence or time ordering of messages large set of detailed notation options of their greater notational power. space economical - flexibility to add new objects in two dimensions - forced to extend to the right when adding new objects; consumes horizontal space UML tools often emphasize sequence diagrams, because - more difficult to see sequence of messages - fewer notational options

53 Summary

54 Goal of the Lecture 54 The goal of this lecture is to enable you to systematically carry out small(er) software projects that produce quality software. Modeling the dynamic behavior is often more rewarding than modeling the static structure w.r.t. understanding a domain Modeling the dynamic behavior is often particularly useful if the control-flow is more involved; but only draw the part that is relevant to understand the problem at hand The UML is often used informally - this is OK if everyone interprets the diagrams in the same way

55 Goal of the Lecture 55 The goal of this lecture is to enable you to systematically carry out small(er) commercial or open-source projects. Modeling Software Project Management Project Start Requirements Management Domain Modeling Modeling Testing Project End