Dynamic Modeling - Chair for Applied Software Engineering

More documents

Recommendations

Info

Problem Statement: Direction Control for a Toy Car • Power is turned on • Car moves forward and car headlight shines • Power is turned off • Car stops and headlight goes out. • Power is turned on • Headlight shines • Power is turned off • Headlight goes out • Power is turned on • Car runs backward with its headlight shining • Power is turned off • Car stops and headlight goes out • Power is turned on • Headlight shines • Power is turned off • Headlight goes out • Power is turned on • Car runs forward with its headlight shining © 2006 Bernd Bruegge Software Engineering WS 2006/2007 44
Find the Functional Model: Use Cases • Use case 1: System Initialization • Entry condition: Power is off, car is not moving • Flow of events: 1. Driver turns power on • Exit condition: Car moves forward, headlight is on • Use case 2: Turn headlight off • Entry condition: Car moves forward with headlights on • Flow of events: 1. Driver turns power off, car stops and headlight goes out. 2. Driver turns power on, headlight shines and car does not move. 3. Driver turns power off, headlight goes out • Exit condition: Car does not move, headlight is out © 2006 Bernd Bruegge Software Engineering WS 2006/2007 45
Page 1 and 2: Dynamic Modeling Software Engineeri
Page 3 and 4: How do you find classes • We have
Page 5 and 6: Interaction Diagram • Two types o
Page 7 and 8: Dynamic Modeling • Definition of
Page 9 and 10: What is an Event • Something that
Page 11 and 12: Sequence Diagram • A sequence dia
Page 13 and 14: Sequence Diagram for “Get SeatPos
Page 15 and 16: ARENA Sequence Diagram: Create Tour
Page 17 and 18: League Owner Attributes Operations
Page 19 and 20: Impact on ARENA’s Object Model (2
Page 21 and 22: League Owner Attributes Operations
Page 23 and 24: Fork Diagram • The dynamic behavi
Page 25 and 26: Fork or Stair • Object-oriented s
Page 27 and 28: UML Statechart Diagram Notation Eve
Page 29 and 30: State • An abstraction of the att
Page 31 and 32: Example of a Nested Statechart Diag
Page 33 and 34: Example of a Nested Statechart Diag
Page 35 and 36: Superstates • Sets of substates i
Page 37 and 38: Example of Concurrency within an Ob
Page 39 and 40: Dynamic Modeling of User Interfaces
Page 41 and 42: Practical Tips for Dynamic Modeling
Page 43: Let’s Do Analysis • Analyze the
Page 47 and 48: Use Cases Continued • Use case 5:
Page 49 and 50: Dynamic Modeling: Create the Sequen
Page 51 and 52: Toy Car: Dynamic Model Headlight Wh
Page 53 and 54: When is a Model Dominant • Object
Page 55 and 56: Outline of the Lecture Dynamic mode
Page 57 and 58: Verification and Validation • Ver
Page 59 and 60: Checklist for the Requirements Revi
Page 61 and 62: Different spellings in different UM
Page 63 and 64: Requirements Analysis Document Temp
Page 65 and 66: Summary • In this lecture, we rev
Page 67: Is this a good Sequence Diagram Sma

Dynamic Modeling - Chair for Applied Software Engineering

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?