[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-655737-105":59,"doc-detail-655737-en":122},{"code":4,"msg":5,"data":6},0,"success",[7,13,18,23,28,33,38,43,48,51,55],{"id":8,"doc_module":4,"doc_module_name":9,"category_name":10,"show_sort_weight":11,"slug":12},1,"Document","Story & Novel",90,"story-novel",{"id":14,"doc_module":4,"doc_module_name":9,"category_name":15,"show_sort_weight":16,"slug":17},2,"Literature",80,"literature",{"id":19,"doc_module":4,"doc_module_name":9,"category_name":20,"show_sort_weight":21,"slug":22},4,"Exam",70,"exam",{"id":24,"doc_module":4,"doc_module_name":9,"category_name":25,"show_sort_weight":26,"slug":27},5,"Comic",60,"comic",{"id":29,"doc_module":4,"doc_module_name":9,"category_name":30,"show_sort_weight":31,"slug":32},6,"Technology",50,"technology",{"id":34,"doc_module":4,"doc_module_name":9,"category_name":35,"show_sort_weight":36,"slug":37},7,"Healthcare",40,"healthcare",{"id":39,"doc_module":4,"doc_module_name":9,"category_name":40,"show_sort_weight":41,"slug":42},8,"Research & Report",30,"research-report",{"id":44,"doc_module":4,"doc_module_name":9,"category_name":45,"show_sort_weight":46,"slug":47},9,"Religion & Spirituality",20,"religion-spirituality",{"id":46,"doc_module":4,"doc_module_name":9,"category_name":49,"show_sort_weight":46,"slug":50},"World Cup","world-cup",{"id":52,"doc_module":4,"doc_module_name":9,"category_name":53,"show_sort_weight":52,"slug":54},10,"Lifestyle","lifestyle",{"id":56,"doc_module":4,"doc_module_name":9,"category_name":57,"show_sort_weight":24,"slug":58},19,"General","general",{"code":4,"msg":60,"data":61},"ok",{"site_id":62,"language":63,"slug":64,"title":65,"keywords":66,"description":67,"schema_data":68,"social_meta":115,"head_meta":117,"extra_data":119,"updated_unix":121},105,"en","interaction-diagram-notation-applying-uml-and-patterns-chapter-15-objectives","Interaction Diagram Notation - Applying UML and Patterns, Chapter 15 - Objectives","","Chapter 15 introduces interaction diagram notation used to model how objects collaborate through messages in UML. It explains the purpose of both sequence diagrams and collaboration diagrams, including their relative strengths and weaknesses for diagram layout and message ordering. The chapter provides an example collaboration diagram for makePayment and a corresponding sequence diagram with the same intent. It emphasizes careful design thinking, spending real effort on diagram creation, and doing the work collaboratively using design principles, patterns, and degrees of freedom.",{"@graph":69,"@context":114},[70,84,105],{"@type":71,"itemListElement":72},"BreadcrumbList",[73,77,79,82],{"item":74,"name":75,"@type":76,"position":8},"https://docshare.wps.com","Home","ListItem",{"item":78,"name":9,"@type":76,"position":14},"https://docshare.wps.com/document/",{"item":80,"name":30,"@type":76,"position":81},"https://docshare.wps.com/document/technology/",3,{"item":83,"name":65,"@type":76,"position":19},"https://docshare.wps.com/document/interaction-diagram-notation-applying-uml-and-patterns-chapter-15-objectives/655737/",{"url":83,"name":65,"@type":85,"image":86,"author":91,"headline":65,"publisher":94,"fileFormat":97,"inLanguage":63,"description":67,"dateModified":98,"datePublished":99,"encodingFormat":97,"isAccessibleForFree":100,"interactionStatistic":101},"DigitalDocument",{"url":87,"@type":88,"width":89,"height":90},"https://docshare.wps.com/thumbnails/interaction-diagram-notation-applying-uml-and-patterns-chapter-15-objectives/655737.png","ImageObject",300,407,{"name":92,"@type":93},"The weather in my hometown","Person",{"url":74,"name":95,"@type":96},"DocShare","Organization","application/pdf","2026-10-30","2026-10-25",true,{"@type":102,"interactionType":103,"userInteractionCount":24},"InteractionCounter",{"@type":104},"ViewAction",{"@type":106,"mainEntity":107},"FAQPage",[108],{"name":109,"@type":110,"acceptedAnswer":111},"What is recommended about how to create interaction diagrams?","Question",{"text":112,"@type":113},"Create interaction diagrams in pairs rather than alone. Collaborative design improves the diagram quality and helps partners learn quickly from each other.","Answer","https://schema.org",{"og:url":83,"og:type":116,"og:title":65,"og:site_name":95,"og:description":67},"article",{"robots":118,"canonical":83},"index,follow",{"doc_id":120,"site_id":62},655737,1793051892,{"code":4,"msg":5,"data":123},{"doc_id":120,"user_id":124,"nickname":92,"user_avatar":125,"doc_module":4,"category_id":29,"category_name":30,"doc_title":65,"doc_description":67,"doc_content":126,"file_id":127,"file_url":128,"file_type":129,"file_size":130,"view_count":24,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":131,"language":132,"language_code":63,"site_id":62,"html_lang":63,"table_of_contents":133,"faqs":134,"seo_title":135,"seo_description":67,"update_tm":136,"read_time":137},1374408744247,"https://ap-avatar.wpscdn.com/avatar/14001251d37d565ec6f?x-image-process=image/resize,m_fixed,w_180,h_180&k=1790672120290115972","From Craig Larman, Applying UML and Patterns: An Introduction to ObjectOriented Analysis and Design, and the Unified Process. 2nd Edition.  \nChapter 15  \nINTERACTION DIAGRAM  \nNOTATION  \nCats are smarter than dogs. You can't get eight cats to pull a sled through snow.  \nóJeffVaidez  \nObjectives  \nRead basic UML interaction (sequence and collaboration) diagram notation.  \nIntroduction  \nThe following chapters explore object design. The language used to illustrate the designs is primarily interaction diagrams. Thus, it is advisable to at least skim the examples in this chapter and get familiar with the notation before moving on.  \nThe UML includes interaction diagrams to illustrate how objects interact via messages. This chapter introduces the notation, while subsequent chapters focus on using them in the context of learning and doing object design for the NextGen POS case study.  \nRead the Following Chapters for Design Guidelines  \nThis chapter introduces notation. To create well-designed objects, design principles must also be understood. After acquiring some familiarity with the notation of interaction diagrams, it is important to study the following chapters on these principles and how to apply them while drawing interaction diagrams.  \n15-INTERACTION DIAGRAM NOTATION  \n15.1 Sequence and Collaboration Diagrams  \nThe term interaction diagram, is a generalization of two more specialized UML diagram types; both can be used to express similar message interactions:ï collaboration diagrams  \nï sequence diagrams  \nThroughout the book, both types will be used, to emphasize the flexibility in choice.  \nCollaboration diagrams illustrate object interactions in a graph or network format, in which objects can be placed anywhere on the diagram, as shown in Figure 15.1.  \nFigure 15.1 Collaboration diagram  \nFigure 15.2 Sequence diagram.  \nEach type has strengths and weaknesses. When drawing diagrams to be published on pages of narrow width, collaboration diagrams have the advantage of allowing vertical expansion for new objects; additional objects in a sequence diagrams must extend to the right, which is limiting. On the other hand, collaboration diagram examples make it harder to easily see the sequence of messages.  \nMost prefer sequence diagrams when using a CASE tool to reverse engineer source code into an interaction diagram, as they clearly illustrate the sequence of messages.  \n15.2 Example Collaboration Diagram: makePayment  \nFigure 15.3 Collaboration diagram.  \nThe collaboration diagram shown in Figure 15.3 is read as follows:  \n1. The message makePayment is sent to an instance of a Register. The sender isnot identified.  \n2. The Register instance sends the makePayment message to a Sale instance.  \n3. The Sale instance creates an instance of a Payment.  \n15-INTERACTION DIAGRAM NOTATION  \n15.3 Example Sequence Diagram: makePayment  \nFigure 15.4 Sequence diagram.  \nmakePayment(cashTendered)   \nThe sequence diagram shown in Figure 15.4 has the same intent as the prior collaboration diagram.  \n15.4 Interaction Diagrams Are Valuable  \nA common problem in object technology projects is a lack of appreciation for the value of doing object design via the medium of interaction diagrams. A related problem is doing them in a vague way, such as showing messages to objects that actually require much further elaboration; for example, showing the message runSimulation to some Simulation object, but not continuing on with the more detailed design, as though by virtue of a well-named message the design is magically complete.  \nSome non-trivial time and effort should be spent in the creation of interaction diagrams, as a reflection of thinking through details of the object design. For example, if the length of the timeboxed iteration is two weeks, perhaps a half or full day near the start of the iteration should be spent on their creation (and in parallel, class diagrams), before proceeding to programming. Yes, the design illustrated in the diagrams","cbCaigK6zxeFeGSf","https://ap.wps.com/l/cbCaigK6zxeFeGSf","pdf",647022,17,"English","# Interaction Diagram Notation\n## Sequence and Collaboration Diagrams\n## Example Collaboration Diagram: makePayment\n## Example Sequence Diagram: makePayment(cashTendered)\n## Interaction Diagrams Are Valuable\n## Common Interaction Diagram Notation Illustrating Classes and Instances","[{\"question\":\"What is recommended about how to create interaction diagrams?\",\"answer\":\"Create interaction diagrams in pairs rather than alone. Collaborative design improves the diagram quality and helps partners learn quickly from each other.\"}]","Interaction Diagram Notation - Applying UML and Patterns, Chapter 15 - Objectives | PDF",1792963524,43]