UML behavior models. Kristian Sandahl

Transcription

1 UML behavior models Kristian Sandahl

2 Maintenance Validate Requirements, Verify Specification Requirements System Design (Architecture, High-level Design) Verify System Design Acceptance Test (Release testing) System Testing (Integration testing of modules) Module Design (Program Design, Detailed Design) Verify Module Design Verify Implementation Module Testing (Integration testing of units) Implementation of Units (classes, procedures, functions) Unit testing Project Management, Software Quality Assurance (SQA), Supporting Tools, Education 2

3 The goals of module design, again Provide the expected function Prepare for change: Separation of concern Testability Understandability Contribute to quality, eg: Performance Usability Reliability... Map for the implementers and testers 3

4 Well-known s of UML UML/Kristian Sandahl UML Structure Behavior Class Object Package Component Use-Case State Machine Interaction Deployment Sequence 4

5 Well-known s of UML UML/Kristian Sandahl UML Structure Behavior Class Object Package Component Use-Case State Machine Interaction Deployment Sequence 5

6 Different instance models 6 Specific Kristian : CoffeeCustomer buys Cup1 : CupOfCoffee makes IDA-B-house : Machine Generic acoffeecustomer : CoffeeCustomer buys acup : CupOfCoffee makes amachine : Machine Short hand : CoffeeCustomer buys : CupOfCoffee makes : Machine Related: Roles : CoffeeCustomer buys : CupOfCoffee makes : Machine

7 For class CoinHandler: State machine diagram start state marker transiton this object checking falsecoin()/returncoin(self) insertcoin()/checkcoin(self) idle state trigger event, causing transition action, reaction to the event 7

8 A few more states Kristian s alarm clock starts sounding at 6.00 with a nasty signal. He can now do either of three things: a) Turn the alarm off; b) Press the snooze button; or c) Do nothing. If the snooze button is pressed the signal will turn off and start sounding after 5 minutes again. When an hour has passed from the first time the alarm sound started, the snooze button has no effect. After that the alarm sound starts, the signal will last for 2 minutes. If no action has been taken during these 2 minutes, the absence of action will have the same effect as if the snooze button were pressed exactly when the alarm stopped to sound. 8

9 Orthogonal, composite states course attempt state machine Studying orthogonal state lab1 done Lab 1 Lab 2 lab2 done Project Final exam project done pass orthogonal region fail Failed Passed

10 course attempt Explicit exit points Studying lab1 done Lab 1 Lab 2 lab2 done Project Final exam project done pass fail failed passed

11 Activity diagram State diagram Initial node decision insert coin coin accepted? final [no] node fork [yes] brew coffee add sugar/whitener add hot water to adjust strength join pour coffee

12 role Sequence diagram : Interface : CoffeeCustomer insertcoin machineready pressbutton(b1) Life line of object Message (synchronous) Procedure is active time pourcoffee

13 Sequence diagram with several roles : Interface : CoinHandler : Brewer : CoffeeCustomer insertcoin transport Return message Timing constraint { 0 < 5s} litindicators coinaccepted warmup pressbutton(b1) makeorder(o1) pourcoffee pourcoffee

14 Combining fragments of sequence diagrams SD processorder :Order :TicketDB :Account create ref Get existing customer data gate loop loop [get next item] reserve(date,no) loop condition add(seats) destruction answer

15 Combining fragments of sequence diagrams SD Get existing customer data :Order :TicketDB :Account create Getdata(c1) Data(c1)

16 Combining fragments of sequence diagrams SD processorder create :Order :TicketDB :Account ref Get existing customer data loop loop [get next item] reserve(date,no) loop condition add(seats) destruction answer

17 More fragments of sequence diagrams :Order :TicketDB loop [get next item] reserve(date,no) guard condition alt [available] add(seats) reject [unavailable] nested conditional alternate branches

18

19 Lecture exercise Create an architecture of a system. Break the system down in (probably) less than 10 elements. Don t forget a little explaining text of what we will see. Line-and-box is OK. Reflect on quality factors. Are they facilitated or impeded? What view do you expose to the reader? Create a sequence diagram. Use fragments if it eases interpretation. Maybe it helps to write the use-cases first?

20