Dynamic Modeling - Chair for Applied Software Engineering

More documents

Recommendations

Info

The term ‘Event’ is often used in two ways • Instance of an event class: • “Slide 10 shown on Tuesday Dec 5 at 10:30”. • Event class “Lecture Given”, Subclass “Slide Shown” • Attribute of an event class • Slide Update(5:30 AM, 12/4/2006) • Train_Leaves(4:45pm, Manhattan) • Mouse button down(button#, tablet-location) © 2006 Bernd Bruegge Software Engineering WS 2006/2007 10
Sequence Diagram • A sequence diagram is a graphical description of the objects participating in a use case using a DAG notation • Heuristic for finding participating objects: • A event always has a sender and a receiver. • Find them for each event => These are the objects participating in the use case • Relation to object identification: • Several objects/classes have already been identified during object modeling • New objects are now identified as a result of dynamic modeling © 2006 Bernd Bruegge Software Engineering WS 2006/2007 11
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: What is an Event • Something that
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 and 44: Let’s Do Analysis • Analyze the
Page 45 and 46: Find the Functional Model: Use Case
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
show all

Dynamic Modeling - Chair for Applied Software Engineering

Create successful ePaper yourself

Delete template?

Save as template?