Logistics E-mail UML 2 Should have received mail from me. If - - PDF document

logistics
SMART_READER_LITE
LIVE PREVIEW

Logistics E-mail UML 2 Should have received mail from me. If - - PDF document

Logistics E-mail UML 2 Should have received mail from me. If not: Check LDAP entry Indicate on attendance sheet Announcements Plan for today Its Co-op time Building a software system Orientation


slide-1
SLIDE 1

UML 2 Logistics

  • E-mail

– Should have received mail from me. – If not:

  • Check LDAP entry
  • Indicate on attendance sheet

Announcements

  • It’s Co-op time

– Orientation

– Wednesday, Sept 17th, 4:00 pm – 5:30 pm, 77- A190 – Thursday, Sept 18th, 12:00 pm – 1:30 pm, 70- 1455 – Friday, Sept 19th, 1:00 pm – 2:30 pm, 76- 1125 – Friday, Sept 26th, 1:00 pm – 2:30 pm, 76- 1125 – Tuesday, Oct 7th, 1:00 pm – 2:30 pm, 76- 1125 – Wednesday, Oct 22nd, 4:00 pm – 5:30 pm, 77- A190

  • Job Fair

– Wednesday, Oct 15, 1-6pm, Clark Gym

Plan for today

  • Building a software system

– Documenting your design using UML – Last time we looked at:

  • Class Diagram
  • Use Case Diagram

– Today

  • Sequence Diagram
  • Rose Demo

Class Diagram – Summary Use Case – Relationships

slide-2
SLIDE 2

Sequence Diagram

  • Messages

– A communication between objects – Types:

  • Call and return – Calls a method on an object and waits for it’s

return

  • Create action – creates a new object
  • Destroy action – destroys an existing object
  • Send – A signal is sent to an object. Asynchronous! Sending
  • bject does NOT wait for ack or return
  • A Sequence Diagram illustrates time ordering of

messages that go back and forth between objects in performing a given scenario

Sequence Diagram Sequence Diagram – Messages

  • Return values – dotted arrow

Destroy – object Xed out

Object 1 Object 2

action() return type

Object 1 Object 2

destroy

Sequence Diagram – Messages

Create – object suddenly appears

Object 1 Object 2

create

Sequence Diagram – Messages

  • Send – Half arrow

Objects / classes can talk to themselves

Object 1 Object 2

action()

Object 1

action()

Sequence Diagram -- Summary

  • Illustrates time ordering of messages that go

back and forth between objects in performing a given scenario

– show examples of important interactions; they are not graphical representations of method code

  • Questions
slide-3
SLIDE 3

The Microwave Example

  • There is a single control button available for the

user of the oven.

– If the oven door is closed and you push the button, the

  • ven will cook (energize the power tube) for 1 minute.

– If you push the button at any time when the oven is cooking, you get an additional minute of cooking time. – Pushing the button when the door is open has no effect. – Opening the door stops the cooking and clears the timer to 0.

The Microwave Example

  • There is a light inside the oven.

– Anytime the oven is cooking, the light must be turned on. – Any time the door is open, the light must be on. – If you close the door, the light goes out. – If the oven times out, it turns off both the power tube and the light. It then emits a warning beep to tell you that it is finished.

Demo time

  • Example / demo of building UML diagrams

using Rational Rose.