Detailed Sequence Diagram

broken image


Sequence diagram. The sequence diagram shows an exemplar or 'sample execution' of some portion of the system under specific conditions. However, sequence diagrams are the last stop before coding, and as such need to show the real design in full detail. Turning your sequence diagram into a flowchart instead of using it to allocate behavior among objects. Remember that the sequence diagram is the primary vehicle for making behavior allocation decisions. SequenceDiagram.org is an online tool / software for creating UML sequence diagrams. Founded in 2014 with the purpose to improve the efficiency when creating and working with sequence diagrams by combining text notation scripting and drawing by clicking and dragging in the same model. Diagrams are the most common diagrams used in modeling object-oriented systems. Class diagrams address the static design view of a system. Sequence diagram is an interaction diagram. Interaction diagrams address the dynamic view of a system, besides sequence diagram, the other interaction diagram in UML is the Collaboration diagram. Sequence Diagram is an interaction diagram that details how operations are carried out - what messages are sent and when. Sequence diagrams are organized according to time. The time progresses as you go down the page. The objects involved in the operation are listed from left to right according to when they take part in the message sequence.

This appendix describes detailed sequence diagrams and message dumps of an application that provides a personalized ring back tone.

Personalized Ring Back Tone

The personalized ring back tone service is a terminating service that improves the traditional ring back tone by playing a personalized ring back tone to the calling party during the alerting phase of the call.

When the called party answers the call, the personalized ring back tone is stopped, and the parties are connected.

Figure A-1, Figure A-2 and Figure A-3 show the detailed sequence diagram of the personalized ring back tone service.

Figure A-2 Personalized Ring Back Tone (cont'd)


Message Dumps

This section provides dumps of messages shown on Figure A-1, Figure A-2, and Figure A-3.

Message #1: CAP InitialDP

Direction: MSC -> Service Broker

Message Content

Message #2: SIP INVITE

Direction: Service Broker -> Application

Message Headers

Message Body

Message #3: SIP_INVITE

Direction: Application -> Service Broker

Message Headers

Message Body

Message #4: CAP InitiateCallAttempt

Direction: Service Broker -> MSC

Message Content

Message #5: CAP InitiateCallAttempt Result

Direction: MSC -> Service Broker

Message Content

Message #6: SIP 183 SESSION PROGRESS

Direction: Service Broker -> Application

Message Headers

Message Body

Message #7: CAP RequestReportBCSMEvent

Direction: Service Broker -> MSC

Message Content

Message #8: CAP ContinueWithArgument

Direction: Service Broker -> MSC

Message Content

Message #9: SIP INVITE

Direction: Application -> Service Broker

Message Headers

Message Body

Message #10: CAP InitiateCallAttempt

Direction: Service Broker -> MSC

Message Content

Message #11: CAP InitiateCallAttempt Result

Direction: MSC -> Service Broker

Diagram

Message Content

Message #12: SIP 183 SESSION PROGRESS

Direction: Service Broker -> Application

Message Headers

Message Body

Message #13: CAP RequestReportBCSMEvent

Direction: Service Broker -> MSC

Message Content

Message #14: CAP ContinueWithArgument

Direction: Service Broker -> MSC

Message Content

Message #15: CAP EventReportBCSM

Direction: MSC -> Service Broker

Message Content

Message #16: SIP 180 RINGING

Direction: Service Broker -> Application

Message Headers

Message Body

Sequence diagram tool

n/a

Message #17: CAP EventReportBCSM

Direction: MSC -> Service Broker

Message Content

Message #18: SIP 180 RINGING

Direction: Service Broker -> Application

Message Headers

Message Body

n/a

Message #19: SIP 183 SESSION PROGRESS

Direction: Application -> Service Broker

Message Headers

Message Body

Message #20: CAP DisconnectLeg

Direction: Service Broker -> MSC

Message Content

Message #21: CAP DisconnectLeg Result

Direction: MSC -> Service Broker

Message Content

Message #22: CAP RequestReportBCSM

Direction: Service Broker -> MSC

Sequence Diagram Online

Message Content

Message #23: CAP ContinueWithArgument

Direction: Service Broker -> MSC

Message Content

Message #24: CAP MoveLeg

Direction: Service Broker -> MSC

Message Content

Message #25: CAP MoveLeg Result

Direction: MSC -> Service Broker

Message Content

Detailed Sequence Diagram

Message #26: CAP ContinueWithArgument

Direction: Service Broker -> MSC

Message Content

Project Sequence Diagram

Message #27: CAP EventReportBCSM

Direction: MSC -> Service Broker

Message Content

Message #28: SIP 200 OK

Direction: Service Broker -> Application

Message Headers

Message Body

Message #29: SIP 200 OK

Direction: Application -> Service Broker

Message Headers

Message Body

Message #30: CAP ContinueWithArgument

Direction: Service Broker -> MSC

Message Content

Message #31: CAP EventReportBCSM

Direction: MSC -> Service Broker

Message Content

Message #32: SIP 200 OK

Direction: Service Broker -> Application

Message Headers

Message Body

Message #33: CAP ContinueWithArgument

Sequence Diagram Tutorial

Direction: Service Broker -> MSC

Message Content

Message #34: SIP BYE

Direction: Application -> Service Broker

Message Headers

Message Body

n/a

Message #35: SIP 200 OK

Direction: Service Broker -> Application

Message Headers

Message Body

n/a

Message #36: CAP DisconnectLeg

Direction: Service Broker -> MSC

Message Content

Message #37: CAP DisconnectLeg Result

Direction: MSC -> Service Broker

Message Content

Sequence

Message Content

Message #12: SIP 183 SESSION PROGRESS

Direction: Service Broker -> Application

Message Headers

Message Body

Message #13: CAP RequestReportBCSMEvent

Direction: Service Broker -> MSC

Message Content

Message #14: CAP ContinueWithArgument

Direction: Service Broker -> MSC

Message Content

Message #15: CAP EventReportBCSM

Direction: MSC -> Service Broker

Message Content

Message #16: SIP 180 RINGING

Direction: Service Broker -> Application

Message Headers

Message Body

n/a

Message #17: CAP EventReportBCSM

Direction: MSC -> Service Broker

Message Content

Message #18: SIP 180 RINGING

Direction: Service Broker -> Application

Message Headers

Message Body

n/a

Message #19: SIP 183 SESSION PROGRESS

Direction: Application -> Service Broker

Message Headers

Message Body

Message #20: CAP DisconnectLeg

Direction: Service Broker -> MSC

Message Content

Message #21: CAP DisconnectLeg Result

Direction: MSC -> Service Broker

Message Content

Message #22: CAP RequestReportBCSM

Direction: Service Broker -> MSC

Sequence Diagram Online

Message Content

Message #23: CAP ContinueWithArgument

Direction: Service Broker -> MSC

Message Content

Message #24: CAP MoveLeg

Direction: Service Broker -> MSC

Message Content

Message #25: CAP MoveLeg Result

Direction: MSC -> Service Broker

Message Content

Message #26: CAP ContinueWithArgument

Direction: Service Broker -> MSC

Message Content

Project Sequence Diagram

Message #27: CAP EventReportBCSM

Direction: MSC -> Service Broker

Message Content

Message #28: SIP 200 OK

Direction: Service Broker -> Application

Message Headers

Message Body

Message #29: SIP 200 OK

Direction: Application -> Service Broker

Message Headers

Message Body

Message #30: CAP ContinueWithArgument

Direction: Service Broker -> MSC

Message Content

Message #31: CAP EventReportBCSM

Direction: MSC -> Service Broker

Message Content

Message #32: SIP 200 OK

Direction: Service Broker -> Application

Message Headers

Message Body

Message #33: CAP ContinueWithArgument

Sequence Diagram Tutorial

Direction: Service Broker -> MSC

Message Content

Message #34: SIP BYE

Direction: Application -> Service Broker

Message Headers

Message Body

n/a

Message #35: SIP 200 OK

Direction: Service Broker -> Application

Message Headers

Message Body

n/a

Message #36: CAP DisconnectLeg

Direction: Service Broker -> MSC

Message Content

Message #37: CAP DisconnectLeg Result

Direction: MSC -> Service Broker

Message Content

Message #38: CAP ContinueWithArgument

Direction: Service Broker -> MSC

Message Content

Message #39: SIP reINVITE

Direction: Application -> Service Broker

Message Headers

Message Body

Message #40: CAP MoveLeg

Direction: Service Broker -> MSC

Message Content

Message #41: CAP MoveLeg Result

Direction: MSC -> Service Broker

Message Content

Message #42: CAP ContinueWithArgument

Direction: Service Broker -> MSC

Message Content

Message #43: SIP 200 OK

Direction: Service Broker -> Application

Message Headers

Message Body

n/a

Message #44: CAP EventReportBCSM

Direction: MSC -> Service Broker

Message Content

Message #45: SIP BYE

Direction: Service Broker -> Application

Message Headers

Message Body

n/a

Message #46: SIP 200 OK

Direction: Application -> Service Broker

Message Headers

Message Body

n/a

Message #47: SIP BYE

Direction: Application -> Service Broker

Message Headers

Message Body

Message #48: SIP 200 OK

Direction: Service Broker -> Application

Message Headers

Message Body

n/a

Message #49: CAP ReleaseCall

Direction: Service Broker -> MSC

Message Content


Overview

The Sequence diagram is a type of Interaction diagram that focuses on the Message interchange between various Lifelines.

A Sequence diagram shows the interaction information with an emphasis on the time sequence. The diagram has two dimensions: the vertical axis representing time and the horizontal axis representing the participating objects. The time axis could be an actual reference point by placing the time labels as text boxes. The horizontal ordering of the objects is not significant to the operation, and you can rearrange them as necessary.

There are two Sequence Diagram modeling approaches:

  • Activation bars as the lifelines.
  • Activation bars as the Execution Specifications (new modeling approach).

Purpose

The purpose of the Sequence diagram is to represent some aspect of the communication between objects to perform a task. The main benefit of the diagram is that it helps to identify the messages exchanged between objects.

Usage

A Sequence diagram can be used to:

  • represent the details of a UML Use Case
  • model the logic of a sophisticated procedure, function, or operation
  • analyze the interaction of objects and components to complete a process
  • plan and understand the detailed functionality of an existing or future scenario.

Summary

Sequence diagrams are valuable because they:

  • allow seeing the specific questions, commands, and data being communicated during the execution of a specific task
  • identify the communication required to fulfill an interaction
  • identify the objects that participate in an interaction
  • identify the data that is passed as part of the interactions.
Example of a Sequence diagram

Related pages

  • Working with Execution Specifications




broken image
PreviousNext
Cookie Use
We use cookies to improve browsing experience, security, and data collection. By accepting, you agree to the use of cookies for advertising and analytics. You can change your cookie settings at any time. Learn More
Accept all
Settings
Decline All
Cookie Settings
Necessary Cookies
These cookies enable core functionality such as security, network management, and accessibility. These cookies can’t be switched off.
Analytics Cookies
These cookies help us better understand how visitors interact with our website and help us discover errors.
Preferences Cookies
These cookies allow the website to remember choices you've made to provide enhanced functionality and personalization.
Save