[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-665496-105":59,"doc-detail-665496-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","uml-use-case-diagrams-introduction-to-use-cases-and-relationships","UML Use Case Diagrams - Introduction to Use Cases and Relationships","","An overview of UML use case diagrams explains how use cases support the analysis phase by partitioning a system into actors and use cases. Actors are external roles that supply stimuli and receive outputs. Use cases are described as text behaviors triggered by specific stimuli, including input/output details and error handling. A point-of-sale example illustrates step-by-step execution, manual entry on database misses, and barcode scanning reuse via «uses» relationships, plus «extends» for underage liquor checkout.",{"@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/uml-use-case-diagrams-introduction-to-use-cases-and-relationships/665496/",{"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/uml-use-case-diagrams-introduction-to-use-cases-and-relationships/665496.png","ImageObject",300,407,{"name":92,"@type":93},"Mimi","Person",{"url":74,"name":95,"@type":96},"DocShare","Organization","application/pdf","2026-10-30","2026-10-29",true,{"@type":102,"interactionType":103,"userInteractionCount":81},"InteractionCounter",{"@type":104},"ViewAction",{"@type":106,"mainEntity":107},"FAQPage",[108,114,118],{"name":109,"@type":110,"acceptedAnswer":111},"What is the purpose of UML use case diagrams in project analysis?","Question",{"text":112,"@type":113},"They help identify and partition system functionality by separating the system into actors and use cases during the analysis phase.","Answer",{"name":115,"@type":110,"acceptedAnswer":116},"How are actors defined in UML use case diagrams?",{"text":117,"@type":113},"Actors represent roles played by humans, other computers, hardware, or even other software systems, and they must be external to the system part being partitioned.",{"name":119,"@type":110,"acceptedAnswer":120},"How does the «uses» relationship work between use cases?",{"text":121,"@type":113},"It allows one use case to include shared behavior described elsewhere, like reusing the Swipe UPC Reader behavior in both Check Out Item and Inventory Item.","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},665496,1793304504,{"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":81,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":24,"language":139,"language_code":63,"site_id":62,"html_lang":63,"table_of_contents":140,"faqs":141,"seo_title":142,"seo_description":67,"update_tm":129,"read_time":143},2336477974920,"https://ap-avatar.wpscdn.com/davatar_155a257f0dc6eb9ab79c44ca47cae57d","UML Use Case Diagrams  \nEngineering Notebook  \nC++ Report  \nNov-Dec 98  \nAn important part of the Unified Modeling Language (UML) is the facilities for drawing use case diagrams. Use cases are used during the analysis phase of a project to identify and partition system functionality. They separate the system into actors and use cases.  \nActors represent roles that can are played by users of the system. Those users can be humans, other computers, pieces of hardware, or even other software systems. The only criterion is that they must be external to the part of the system being partitioned into use cases. They must supply stimuli to that part of the system, and the must receive outputs from it.  \nUse cases describe the behavior of the system when one of these actors sends one particular stimulus. This behavior is described textually. It describes the nature of the stimulus that triggers the use case; the inputs from and outputs to other actors, and the behaviors that convert the inputs to the outputs. The text of the use case also usually describes everything that can go wrong during the course of the specified behavior, and what remedial action the system will take.  \nFor example, consider a point of sale system. One of the actors is the customer and another is the salesclerk. Here is just one use case from this system:  \nUse Case 1: Sales Clerk checks out an item  \n1. Customer sets item on counter.  \n2. Sales clerk swipes UPC reader across UPC code on item  \n3. System looks up UPC code in database procuring item description and price  \n4. System emits audible beep.  \n5. System announces item description and price over voice output.  \n6. System adds price and item type to current invoice.  \n7. System adds price to correct tax subtotal Error case 1 : UPC code unreadable  \nIf after step 2, the UPC code was invalid or was not properly read, emit an audible ‘bonk’ sound. Error case 2: No item in database  \nIf after step 3 no database entry is found for the UPC flash the ‘manual entry’ button on the terminal. Accept key entry of price and tax code from Sales Clerk. Set Item description to“Unknown item”. Go to step 4.  \nClearly a point of sale system has many more use cases than this. Indeed, for a complex system, the number can reach into the thousands. The complete functionality of the system can be described in use cases like this. This makes use cases a powerful analysis tool.  \nDrawing Use Case Diagrams.  \nFigure 1 shows what the above use case might look like in UML schematic form. The use case itself is draws as an oval. The actors are drawns as little stick figures. The actors are connected to the use case with lines.  \nSales Clerk  \nCustomer  \nFigure 1  \nClearly this is a pretty simple notation; but there is more to it. Use and actor icons can be assembled into large “system boundary diagrams”. Such diagrams show all the use cases in a system surrounded by a rectangle. Outside the rectangle are all the actors of the system, and they are tied to their use cases with lines. The box represents the system boundary; [i.e. it](i.e. it) shows all the use cases that are inside a particular system. Everything inside the box is part of the system. Everything outside is external to the system. See Figure 2.  \nSales Clerk  \nCustomer  \nManager  \nInventory Clerk  \nFigure 2  \nAside from showing the system boundary, a few more actors, and a few more use cases; this diagram shows some relationships between the use cases. These relationships are «uses» and «contains» . The uses relationship is the simplest of the two. Note that it appears twice in Figure 2, once from Check Out Item to Swipe UPC Reader. The other is from Inventory Item to Swipe UPC Reader. The Swipe UPC Reader use case describes the behavior of the actor and the system when the actor swipes the UPC reader across the barcodes on a product.  \nAs we saw in our first use case, the Swipe UPC Reader behavior needs to occur within the Check Out Item description. However, since invent","cbCaioB8KVAl1Tsq","https://ap.wps.com/l/cbCaioB8KVAl1Tsq","pdf",13428,"English","# UML Use Case Diagrams\n## Use cases in analysis and system partitioning\n## Actors and external roles\n## Use case behavior description and error cases\n## Example: point of sale checkout workflow\n## System boundary diagrams and notation\n## Relationships: «uses» and «extends»","[{\"question\":\"What is the purpose of UML use case diagrams in project analysis?\",\"answer\":\"They help identify and partition system functionality by separating the system into actors and use cases during the analysis phase.\"},{\"question\":\"How are actors defined in UML use case diagrams?\",\"answer\":\"Actors represent roles played by humans, other computers, hardware, or even other software systems, and they must be external to the system part being partitioned.\"},{\"question\":\"How does the «uses» relationship work between use cases?\",\"answer\":\"It allows one use case to include shared behavior described elsewhere, like reusing the Swipe UPC Reader behavior in both Check Out Item and Inventory Item.\"}]","UML Use Case Diagrams - Introduction to Use Cases and Relationships | PDF",13]