1 / 6

Mastering Time Sequence Diagrams at Dr. Zhen Jiang's West Chester University

Explore the fundamentals of time sequence diagrams and their use to depict message ordering in interactions. Learn about lifelines, focus of control, and how to represent object actions over time. Valuable tips and sample projects included.

annyang
Download Presentation

Mastering Time Sequence Diagrams at Dr. Zhen Jiang's West Chester University

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Time Sequence Diagram Dr. Zhen Jiang West Chester University E-mail: zjiang@wcupa.edu url: www.cs.wcupa.edu/~zjiang

  2. Sequence Diagrams • A sequence diagram is an interaction diagram that focuses on the time ordering of messages • A vertical dashed line is used to represent the lifetime of an object (it’s the object’s lifeline) • A focus of control is a tall, thin rectangle that shows the period of time during which an object is performing an action • Details can be found at http://www.ibm.com/developerworks/rational/library/3101.html

  3. : Pilot : ATC : Radar requestLdgClearance(r) checkWeather checkRunwayClear(r) clear clearance

  4. Tips for Time Sequence Diagram • The lifetime of an object is expressed by a rectangle box. It must show when the object starts and when it ends. For different objects with the same class, separated boxes are needed. • The time sequence (which action is conducted first) depends on the execution of objects, NOT user. • “…” will be used in only two places. • No lifetime box for user. • All interface classes must be in interface level. • Any display results using interface objects must be seen in time sequence diagram. • Interface must be organized.

  5. Samples • Grading system • Shopping system • Ticket/Box system

More Related