[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-655917-105":3,"detail-sidebar-cat-0-en-105":80,"doc-detail-655917-en":130},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":73,"head_meta":75,"extra_data":77,"updated_unix":79},105,"en","slides-chapter-3-part-iii-uml-sequence-diagram-example","Slides - Chapter 3 - Part III - UML Sequence Diagram Example","","UML sequence diagram examples explain how to design a system’s dynamic behavior after defining use cases and prototyped core objects with class diagrams. It describes interactions between user and system and focuses on instances and messages as the main elements. The text walks through a Logon sequence with steps for dialog display, credential entry, validation, success entry, and an alternative failure path. It further specifies how to label message calls using sequence, iteration, guards, operation names, and parameters, plus how time flows top to bottom.",{"@graph":14,"@context":72},[15,34,55],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/document/","Document",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/document/technology/","Technology",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/document/slides-chapter-3-part-iii-uml-sequence-diagram-example/655917/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/slides-chapter-3-part-iii-uml-sequence-diagram-example/655917.png","ImageObject",300,407,{"name":42,"@type":43},"Supernature","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-31","2026-10-25",true,{"@type":52,"interactionType":53,"userInteractionCount":33},"InteractionCounter",{"@type":54},"ViewAction",{"@type":56,"mainEntity":57},"FAQPage",[58,64,68],{"name":59,"@type":60,"acceptedAnswer":61},"What is the purpose of a UML sequence diagram in this material?","Question",{"text":62,"@type":63},"It captures the dynamic behavior of a single interaction case by showing how collaborating objects send messages to accomplish a task.","Answer",{"name":65,"@type":60,"acceptedAnswer":66},"What are the steps in the Logon use case example?",{"text":67,"@type":63},"A logon dialog is shown, the user enters a username and password, the user confirms with OK or Enter, credentials are checked, and the user is allowed into the system. If validation fails, the user can try again.",{"name":69,"@type":60,"acceptedAnswer":70},"How are message labels structured on the sequence diagram?",{"text":71,"@type":63},"The labels follow the pattern: Sequence Iteration [Guard] : name(parameters), where sequence indicates call order, iteration uses * for repeated calls, guards are optional boolean constraints, and name with parameters identifies the operation.","https://schema.org",{"og:url":32,"og:type":74,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":76,"canonical":32},"index,follow",{"doc_id":78,"site_id":7},655917,1792964848,{"code":4,"msg":81,"data":82},"success",[83,87,91,95,100,104,109,114,119,122,126],{"id":22,"doc_module":4,"doc_module_name":25,"category_name":84,"show_sort_weight":85,"slug":86},"Story & Novel",90,"story-novel",{"id":26,"doc_module":4,"doc_module_name":25,"category_name":88,"show_sort_weight":89,"slug":90},"Literature",80,"literature",{"id":33,"doc_module":4,"doc_module_name":25,"category_name":92,"show_sort_weight":93,"slug":94},"Exam",70,"exam",{"id":96,"doc_module":4,"doc_module_name":25,"category_name":97,"show_sort_weight":98,"slug":99},5,"Comic",60,"comic",{"id":101,"doc_module":4,"doc_module_name":25,"category_name":29,"show_sort_weight":102,"slug":103},6,50,"technology",{"id":105,"doc_module":4,"doc_module_name":25,"category_name":106,"show_sort_weight":107,"slug":108},7,"Healthcare",40,"healthcare",{"id":110,"doc_module":4,"doc_module_name":25,"category_name":111,"show_sort_weight":112,"slug":113},8,"Research & Report",30,"research-report",{"id":115,"doc_module":4,"doc_module_name":25,"category_name":116,"show_sort_weight":117,"slug":118},9,"Religion & Spirituality",20,"religion-spirituality",{"id":117,"doc_module":4,"doc_module_name":25,"category_name":120,"show_sort_weight":117,"slug":121},"World Cup","world-cup",{"id":123,"doc_module":4,"doc_module_name":25,"category_name":124,"show_sort_weight":123,"slug":125},10,"Lifestyle","lifestyle",{"id":127,"doc_module":4,"doc_module_name":25,"category_name":128,"show_sort_weight":96,"slug":129},19,"General","general",{"code":4,"msg":81,"data":131},{"doc_id":78,"user_id":132,"nickname":42,"user_avatar":133,"doc_module":4,"category_id":101,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":33,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":110,"language":139,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":140,"faqs":141,"seo_title":142,"seo_description":12,"update_tm":79,"read_time":117},962093270004,"https://ap-avatar.wpscdn.com/davatar_9964176cb1d06d4a9deccf72a44ae3dc","UML  \nSequence Diagram Example  \n1  \nSequence Diagram  \n􀀁 Interaction Diagrams-Sequence diagram  \n􀀁 Once the use cases are specified, and some of the core objects in the system are prototyped on class diagrams, we can start designing the dynamic behavior of the system.  \n􀀁 Recall that a use case encompasses an interaction between a user and a system. Typically, an interaction diagram captures the behavior of a single case by showing the collaboration of the objects in the system to accomplish the task.  \n2  \nSequence Diagram  \n􀀁 These diagrams show objects in the system and the messages that are passed between them.  \n􀀁 Let's start with the simple example: a user logging onto the system.  \n3  \nSequence Diagram  \n􀀁 The Logon use case can be specified by the following step:  \n1. Logon dialog is shown  \n2. User enters user name and password  \n3. User clicks on OK or presses the enter key  \n4. The user name and password are checked and approved  \n5. The user is allowed into the system  \n􀀁 Alternative: Logon Failed-if at step 4 the user name and password are not approved, allow the user to try again  \n4  \nSequence Diagram  \n􀀁 Now that we have a simple Use Case to work with, we can specify some of the classes involved in the interaction.  \n􀀁 The LogonDialog has public methods to show and hide the window, and a private method that is called when the user presses the ok button or clicks enter. For our example (and indeed most cases) you need not specify the interface elements of the dialog.  \n5  \nSequence Diagram  \n􀀁 Our design also includes a LogonManager class that will include one method that returns true if the logon is successful, false if it is not.  \n􀀁 A DatabaseAccess class will allow us to run queries against our database. We can pass a query string and a ResultSet of data will be returned.  \n6  \nSequence Diagram  \n􀀁 Now that we have prototyped the classes involved in our interaction, we can begin to make our interaction diagrams.  \n7  \nInstances and Messages  \n􀀁 Interaction diagrams are composed mainly of instances and messages. An instance is said to be the realization of a class, that is if we have a class Doctor, then the instances are Dr. Jones, Dr. Smith, etc. . In an object oriented application, instances are what exist when you instantiate a class (create a new variable with the class as its datatype) .  \n􀀁 In the UML, instances are represented as rectangles with a single label formatted as:  \ninstanceName: datatype  \n􀀁 You can choose to name the instance or not, but the datatype should always be specified.  \n8  \nInstances and Messages  \n􀀁 Below the name, you can also list the attributes and their values. In Visual Case, you can map attributes from your class and enter new values specific to that instance. Attributes need only be shown when they are important and you don't have to specify and show all of the attributes of a class.  \n9  \nMessages  \n􀀁 Messages represent operation calls. That is, if an instance calls an operation in itself or another class, a message is passed. Also, upon the completion of the operation a return message is sent back to the instance that initiated the call.  \nThe format for message labels is:  \nSequence Iteration [Guard] : name (parameters)  \n10  \nMessages  \nThe format for message labels is:  \nSequence Iteration [Guard] : name (parameters)  \n􀀁 Sequence: represents the order in which the message is called. The sequence is redundant on sequence diagrams  \n􀀁 Iteration: an asterix (*) is shown to represent iteration if the message is called repeatedly  \n􀀁 Guard: an optional Boolean expression (the result is either true or false) that determines if the message is called  \n􀀁 name: represents the operation being called  \n􀀁 parameters: represent the parameters on the operation being called  \n11  \nSequence Diagram  \n12  \nThings to Note  \n􀀁 The flow of time is shown from top to bottom, that is messages higher on the diagram happen before those lower down  \n􀀁 The blue boxes are instances of the repr","cbCaibLfYLkzPAMK","https://ap.wps.com/l/cbCaibLfYLkzPAMK","pdf",193603,"English","# Sequence Diagram\n## Interaction Diagrams\n## Logon Use Case Example\n## Instances and Messages\n## Messages Label Format\n## Things to Note\n## Asynchronous Messages","[{\"question\":\"What is the purpose of a UML sequence diagram in this material?\",\"answer\":\"It captures the dynamic behavior of a single interaction case by showing how collaborating objects send messages to accomplish a task.\"},{\"question\":\"What are the steps in the Logon use case example?\",\"answer\":\"A logon dialog is shown, the user enters a username and password, the user confirms with OK or Enter, credentials are checked, and the user is allowed into the system. If validation fails, the user can try again.\"},{\"question\":\"How are message labels structured on the sequence diagram?\",\"answer\":\"The labels follow the pattern: Sequence Iteration [Guard] : name(parameters), where sequence indicates call order, iteration uses * for repeated calls, guards are optional boolean constraints, and name with parameters identifies the operation.\"}]","Slides - Chapter 3 - Part III - UML Sequence Diagram Example | PDF"]