[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-656234-105":59,"doc-detail-656234-en":130},{"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":123,"head_meta":125,"extra_data":127,"updated_unix":129},105,"en","system-sequence-diagrams-ssd-applying-uml-and-patterns","System Sequence Diagrams - SSD - Applying UML and Patterns","","Slides outline how a system sequence diagram (SSD) represents input/output events for a single use-case scenario, treating the system as a black-box. It explains that SSDs are derived from use cases, focus on main success scenarios and key alternatives, and are later used as input for object design. The material then introduces system operations and operation contracts, including template elements and a worked example for enterItem(), culminating in an SSD example for the Process Sale scenario.",{"@graph":69,"@context":122},[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/system-sequence-diagrams-ssd-applying-uml-and-patterns/656234/",{"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/system-sequence-diagrams-ssd-applying-uml-and-patterns/656234.png","ImageObject",300,407,{"name":92,"@type":93},"SANS","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,114,118],{"name":109,"@type":110,"acceptedAnswer":111},"What does a system sequence diagram (SSD) show?","Question",{"text":112,"@type":113},"An SSD shows, for one use-case scenario, the events external actors generate, their order, and inter-system events. The system is treated as a black-box.","Answer",{"name":115,"@type":110,"acceptedAnswer":116},"How are SSDs derived and what are they used for?",{"text":117,"@type":113},"SSDs are derived from use cases and are often drawn for main success scenarios and frequent or complex alternative scenarios. They are used as input for object design.",{"name":119,"@type":110,"acceptedAnswer":120},"What is included in an operation contract for a system operation?",{"text":121,"@type":113},"An operation contract includes the operation name and parameters, cross references to use cases, preconditions before execution, and postconditions describing domain model changes such as created instances and formed or broken associations.","https://schema.org",{"og:url":83,"og:type":124,"og:title":65,"og:site_name":95,"og:description":67},"article",{"robots":126,"canonical":83},"index,follow",{"doc_id":128,"site_id":62},656234,1793073204,{"code":4,"msg":5,"data":131},{"doc_id":128,"user_id":132,"nickname":92,"user_avatar":133,"doc_module":4,"category_id":29,"category_name":30,"doc_title":65,"doc_description":67,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":24,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":139,"language":140,"language_code":63,"site_id":62,"html_lang":63,"table_of_contents":141,"faqs":142,"seo_title":143,"seo_description":67,"update_tm":144,"read_time":145},962090760505,"https://ap-avatar.wpscdn.com/davatar_155a257f0dc6eb9ab79c44ca47cae57d","Dr. Michael Eichberg  \nSoftware Engineering Department of Computer Science Technische Universität Darmstadt  \nSoftware Engineering  \nSystem Sequence Diagrams  \nThe following slides make extensive use of material from:  \nApplying UML and Patterns, 3rd Edition; Craig Larman;  \nPrentice Hall  \nA system sequence diagram (SSD) illustrates input and output events.  \n System Sequence Diagram | 2   \n• An SSD shows – for one particular scenario of a use case –  \n• the events that external actors generate,  \n• their order, and  \n• inter-system events  \n• The system is treated as a black-box  \n• SSDs are derived from use cases; SSDs are often drawn for the main success scenarios of each use case and frequent or complex alternative scenarios  \n• SSDs are used as input for object design  \nSystem Events and System Operations  \n Object-oriented Design | 3  \n• System operations are the operations that the system as a blackbox component offers in its public interface. These are high-level operations triggered by an external input event / system event generated by an external actor  \n• During system behavior analysis, system operations are assigned to a conceptual class System  \nThe system operations are shown in the system sequence diagram (SSD) .  \n Object-oriented Design | 4   \n• To provide more analysis detail on the effect of the system operations implied use cases,(System) Operation Contracts may  \nbe considered  \nProcess Sale Scenario  \n\n|  loop [more items]\u003Cbr>| |\n| --- | --- |\n\n:System  \n\n| makeNewSale\u003Cbr>enterItem(itemId, quantity)\u003Cbr>\u003Cbr>description, price, total |\n| --- |\n| endSale\u003Cbr>total with taxes |\n|  |\n\n:Cashier  \nOperation Contract Template  \n Object-oriented Design | 5  \nOperation:  \nName of the operation and parameters . Cross References:  \nUse cases this operation can occur with. Preconditions:  \nNoteworthy / non-trivial assumptions about the system or objects in the domain model before execution of the operation.  \nPostconditions:  \nThe state of the objects in the domain model after completion of the operation. Domain model changes include:  \n▶ instances created,  \n▶ associations formed or broken,▶ attributes changed.[Postconditions should be stated in the  \nHelpful when assigning  \nresponsibilities  \nto classes  \n(More details will follow).  \nOperation Contract for “enterItem()”  \n Object-oriented Design | 6  \nOperation:  \nenterItem(itemId: ItemId, quantity: Integer) Cross References:  \nUse Cases: Process Sale  \nPreconditions:  \nThere is a sale underway.  \nPostconditions:  \n▶ A SalesLineItem instance (SLI) was created.  \n(instance creation)  \n▶ SLI was associated with the current Sale.  \n(association formed)  \n▶ SLI was associated with a ProductDescription, based on itemId match.  \n(association formed)  \nExample of an SSD for the Process Sale Scenario  \n System Sequence Diagram | 7  \nUse Case: Process Sale Scenario-Main Success Story  \n1. Cashier starts new sale  \n2. Cashier enters item identiﬁer  \n3. System records sale line item and presents item description, price and running total  \nSteps 2 and 3 are repeated until all items are processed.  \n4. System presents total with taxes calculated  \n5. Cashier tells Customer the total and asks for payment  \n6. Customer pays and System handles payment  \nExample of an SSD for the Process Sale Scenario  \n System Sequence Diagram | 8  \nSSDs are drawn using UML’s sequence diagram notation. The name of each event should state the intention (e.g.“enterItem(itemId)” vs.“scan(itemId)”) .  \nMessage Order  \n:System  \n\n| makeNewSale\u003Cbr>enterItem(itemId, quantity)\u003Cbr>\u003Cbr>description, price, total |\n| --- |\n| endSale\u003Cbr>total with taxes |\n| makePayment (amount)\u003Cbr>change due, receipt |\n|  |\n\n:Cashier  \nCommunication Partners  \nProcess Sale Scenario  \nExample of an SSD for the Process Sale Scenario  \n System Sequence Diagram | 9  \nSSDs are drawn using UML’s sequence diagram notation. The name of each event should  \nstate the intention (e.g.“enterItem(itemId)” vs.“scan(itemId)”) .  \nProcess S","cbCain8kzogaDYto","https://ap.wps.com/l/cbCain8kzogaDYto","pdf",2584914,17,"English","# System Sequence Diagrams\n## What an SSD shows\n## System events and system operations\n## Operation contract template\n## Operation contract for enterItem()\n## Example SSD for Process Sale Scenario","[{\"question\":\"What does a system sequence diagram (SSD) show?\",\"answer\":\"An SSD shows, for one use-case scenario, the events external actors generate, their order, and inter-system events. The system is treated as a black-box.\"},{\"question\":\"How are SSDs derived and what are they used for?\",\"answer\":\"SSDs are derived from use cases and are often drawn for main success scenarios and frequent or complex alternative scenarios. They are used as input for object design.\"},{\"question\":\"What is included in an operation contract for a system operation?\",\"answer\":\"An operation contract includes the operation name and parameters, cross references to use cases, preconditions before execution, and postconditions describing domain model changes such as created instances and formed or broken associations.\"}]","System Sequence Diagrams - SSD - Applying UML and Patterns | PDF",1792967119,43]