logistics
play

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


  1. Logistics • E-mail UML 2 – Should have received mail from me. – If not: • Check LDAP entry • Indicate on attendance sheet Announcements Plan for today • It’s Co-op time • Building a software system – Orientation – Documenting your design using UML – Wednesday, Sept 17 th , 4:00 pm – 5:30 pm, 77- – Last time we looked at: A190 – Thursday, Sept 18 th , 12:00 pm – 1:30 pm, 70- 1455 • Class Diagram – Friday, Sept 19 th , 1:00 pm – 2:30 pm, 76- 1125 • Use Case Diagram – Friday, Sept 26 th , 1:00 pm – 2:30 pm, 76- 1125 – Today – Tuesday, Oct 7 th , 1:00 pm – 2:30 pm, 76- 1125 – Wednesday, Oct 22 nd , 4:00 pm – 5:30 pm, 77- A190 • Sequence Diagram • Job Fair • Rose Demo – Wednesday, Oct 15, 1-6pm, Clark Gym Class Diagram – Summary Use Case – Relationships

  2. Sequence Diagram 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 object 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 – Messages Sequence Diagram – Messages • Return values – dotted arrow � Create – object suddenly appears Object 1 Object 2 action() Object 1 return type � Destroy – object Xed out create Object 2 Object 1 Object 2 destroy Sequence Diagram – Messages Sequence Diagram -- Summary • Send – Half arrow • Illustrates time ordering of messages that go back and forth between objects in Object 1 Object 2 performing a given scenario action() – show examples of important interactions; they � Objects / classes can talk to themselves are not graphical representations of method code Object 1 • Questions action()

  3. The Microwave Example The Microwave Example • There is a single control button available for the • There is a light inside the oven. user of the oven. – Anytime the oven is cooking, the light must be – If the oven door is closed and you push the button, the turned on. oven will cook (energize the power tube) for 1 minute. – Any time the door is open, the light must be on. – If you push the button at any time when the oven is – If you close the door, the light goes out. cooking, you get an additional minute of cooking time. – Pushing the button when the door is open has no effect. – If the oven times out, it turns off both the power tube and the light. It then emits a warning beep – Opening the door stops the cooking and clears the timer to 0. to tell you that it is finished. Demo time • Example / demo of building UML diagrams using Rational Rose.

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend