UML Modeling Sequence diagram University of Centeral Punjab Fsd Campus UML Modeling Sequence diagram

Requirements Modeling Strategies Flow-Oriented Modeling Data Flow Diagram Control Flow Modeling State/Activity Diagram Behavior Modeling Sequence Diagram

Sequence Diagram Sequence Diagram: an "interaction diagram" that models a single scenario executing in the system perhaps 2nd most used UML diagram (behind class diagram) University of Centeral Punjab Fsd Campus

Sequence Diagram definition A sequence diagram is an interaction diagram that emphasizes the time ordering of messages. It shows a set of objects and the messages sent and received by those objects. Graphically, a sequence diagram is a table that shows objects arranged along the X axis and messages, ordered in increasing time, along the Y axis.

Sequence Diagram Participant: an object or entity that acts in the sequence diagram sequence diagram starts with an unattached "found message" arrow Message: communication between participant objects The axes in a sequence diagram: horizontal: which object/participant is acting vertical: time (down -> forward in time) University of Centeral Punjab Fsd Campus

Importance of Sequence Diagrams Depict object interactions in a given scenario identified for a given Use Case Specify the messages passed between objects using horizontal arrows including messages to/from external actors Time increases from Top to bottom University of Centeral Punjab Fsd Campus

Rules of Sequence Diagrams Sequence Initiation

Sequence Diagram An object in a sequence diagram is rendered an Order Line An object in a sequence diagram is rendered as a box with a dashed line descending from it. The line is called the object lifeline, and it represents the existence of an object over a period of time. Software Design (UML)

Messages between objects message (method call) indicated by horizontal arrow to other object write message name and arguments above arrow

Sequence Diagram Messages are rendered as horizontal an Order Line a Stock Item Messages are rendered as horizontal arrows being passed from object to object as time advances down the object lifelines. Conditions ( such as [check = “true”] ) indicate when a message gets passed. check() [check = “true”] remove() Software Design (UML)

Sequence Diagram an Order a Order Line * prepare() An iteration marker, such as * (as shown), or *[i = 1..n] , indicates that a message will be repeated as indicated. Iteration marker Software Design (UML)

Rules of Sequence Diagrams Identify objects needed to support use case, determine sequence of internal events following the external initiating event Diagrams that are not initiated with an external actor represent only a partial sequence Partial sequence diagrams should clearly identify the actor initiated sequence diagrams from which they are launched

System Sequence Diagram for Deposit Money Use Case

Sequence dg. from use case University of Centeral Punjab Fsd Campus

Sequence Diagram for ATM Sample

Example

Example

Example

Draw Complete withdraw of money diagram !!

Sequence Diagram(make a phone call) ???

Sequence Diagram(make a phone call) Caller Phone Recipient Picks up Dial tone Dial Ring notification Ring Picks up Hello

Task!! Draw Sequence Diagram for Seat Reservation

Example

Modeling for WebApps Content Analysis. The full spectrum of content to be provided by the WebApp is identified, including text, graphics and images, video, and audio data. Data modeling can be used to identify and describe each of the data objects. Interaction Analysis. The manner in which the user interacts with the WebApp is described in detail. Use-cases can be developed to provide detailed descriptions of this interaction.

Modeling for WebApps Functional Analysis. The usage scenarios (use-cases) created as part of interaction analysis define the operations that will be applied to WebApp content and imply other processing functions. All operations and functions are described in detail. Configuration Analysis. The environment and infrastructure in which the WebApp resides are described in detail.

When Do We Perform Analysis? In some Web situations, analysis and design merge. However, an explicit analysis activity occurs when … the WebApp to be built is large and/or complex the number of stakeholders is large the number of Web engineers and other contributors is large the goals and objectives (determined during formulation) for the WebApp will effect the business’ bottom line the success of the WebApp will have a strong bearing on the success of the business