[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-655905-105":3,"detail-sidebar-cat-0-en-105":80,"doc-detail-655905-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","uml-2-tutorial-use-case-diagram","UML 2 Tutorial - Use Case Diagram","","UML 2 Use Case Diagram explains how to model system requirements through use cases and actors. It defines the notation for actors and use cases, describes system boundaries, and clarifies connections and optional arrowheads. The guide also covers key elements of use case definitions, including requirements, constraints with pre- and post-conditions plus invariants, and scenarios as event flows between external actors and the system.",{"@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/uml-2-tutorial-use-case-diagram/655905/",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/uml-2-tutorial-use-case-diagram/655905.png","ImageObject",300,407,{"name":42,"@type":43},"gewufjwa","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 does a UML 2 use case model capture?","Question",{"text":62,"@type":63},"It captures the requirements of a system, showing what the system is intended to do to users and other stakeholders.","Answer",{"name":65,"@type":60,"acceptedAnswer":66},"What is an actor in a use case diagram?",{"text":67,"@type":63},"An actor represents an external role, such as a human user, external hardware, or another system interacting with the system.",{"name":69,"@type":60,"acceptedAnswer":70},"How are requirements, constraints, and scenarios used in a use case definition?",{"text":71,"@type":63},"Requirements specify formal functional behavior, constraints describe pre-, post-, and invariant conditions, and scenarios define the event flow during execution of a use case instance.","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},655905,1792964717,{"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":30,"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":110},3985747882900,"https://ap-avatar.wpscdn.com/davatar_9964176cb1d06d4a9deccf72a44ae3dc","Products  Support  Resources  UML Tutorial Community  \nLogin  \nEnterprise Architect  \nCurrent Release  \nVersion 1313, Build 13101310 03-March-201703-March-2017  \n Enterprise Architect Trial  \nResources  \nMDG Technologies White paper Repository Demonstrations  \nUML Database modeling Mapping Use Cases RTF Documentation Image Library  \nMDA Resources  \nXML Schema Generation Extra UML Resources  \nWebinars  \nWebinar Registration  \nModel-Driven Use Case Analysis Preparing Visual Models Simulation and Prototyping Tools for Traceability  \nTeam Modeling Resources  \nDBMS Repository Scripts Cloud Services  \nUser Security Key  \nDevelopers  \nAutomation Interface Patterns  \nUML Profiles  \nMDA Style Transforms  \nBuilt-in Transformations Writing Transformations  \nUML Tutorials  \nUML Tutorial  \nUML Tutorial -Part 2 UML 2.0 Tutorial  \nEA Demonstrations UML Models  \nBusiness Process Model Custom Model Dynamic Model Logical Model  \nPhysical Models Use Case Model  \nEnterprise Architect Tutorials  \nNIEM 3 Guide Strategic Models Diagram Filters BPEL Guide  \nResource Management Testing Support Traceability  \nUse Case Metrics  \n\n| | | Resources | | UML 2 Tutorial | | Use Case Diagram |\n| --- | --- | --- | --- | --- | --- | --- |\n\n\n| \u003Cbr>UML 2 Use Case Diagram\u003Cbr>Use Case Model\u003Cbr>The use case model captures the requirements of a system . Use cases are a means of communicating with users and other stakeholders what the system is intended to do.\u003Cbr>Actors\u003Cbr>A use case diagram shows the interaction between the system and entities external to the system . These external entities are referred to as actors. Actors represent roles which may include human users, external hardware or other systems. An actor is usually drawn asa named stick figure, or alternatively as a class rectangle with the «actor» keyword. |  |\n| --- | --- |\n| | |\n| Actors can generalize other actors as detailed in the following diagram:\u003Cbr>Use Cases\u003Cbr>A use case is a single unit of meaningful work. It provides a high-level view of behavior observable to someone or something outside the system . The notation for a use case is an ellipse.\u003Cbr>The notation for using a use case is a connecting line with an optional arrowhead showing the direction of control. The following diagram indicates that the actor \"Customer\" uses the \"Withdraw\" use case.\u003Cbr>The uses connector can optionally have multiplicity values at each end, as in the following diagram, which shows a customer may only have one withdrawal session at a time, but a bank may have any number of customers making withdrawals concurrently.\u003Cbr>Use Case Definition\u003Cbr>A use case typically Includes:\u003Cbr> Name and description\u003Cbr>\u003Cbr>\u003Cbr>\u003Cbr>|  |\n\n Requirements  \n Constraints  \n Scenarios  \n Scenario diagrams  \n Additional information .  \nName and Description  \nA use case is normally named as a verb-phrase and given a brief informal textual description .  \nRequirements  \nThe requirements define the formal functional requirements that a use case must supply to the end user. They correspond to the functional specifications found in structured methodologies. A requirement is a contract or promise that the use case will perform an action or provide some value to the system .  \nConstraints  \nA constraint is a condition or restriction that a use case operates under and includes pre- , post-and invariant conditions. A precondition specifies the conditions that need to be met before the use case can proceed. A post-condition is used to document the change in conditions that must be true after the execution of the use case. An invariant condition specifies the conditions that are true throughout the execution of the use case.  \nScenarios  \nA Scenario is a formal description of the flow of events that occur during the execution of a use case instance. It defines the specific sequence of events between the system and the external actors. It is normally described in text and corresponds to the textual representation of the sequence diagram .  \nIncluding Use C","cbCaihJFkocqNkEl","https://ap.wps.com/l/cbCaihJFkocqNkEl","pdf",128743,"English","# UML 2 Use Case Diagram\n## Actors\n## Use Cases\n## Use Case Definition\n## Requirements\n## Constraints\n## Scenarios\n## Including Use Cases\n## Extending Use Cases\n## Extension Points\n## System Boundary","[{\"question\":\"What does a UML 2 use case model capture?\",\"answer\":\"It captures the requirements of a system, showing what the system is intended to do to users and other stakeholders.\"},{\"question\":\"What is an actor in a use case diagram?\",\"answer\":\"An actor represents an external role, such as a human user, external hardware, or another system interacting with the system.\"},{\"question\":\"How are requirements, constraints, and scenarios used in a use case definition?\",\"answer\":\"Requirements specify formal functional behavior, constraints describe pre-, post-, and invariant conditions, and scenarios define the event flow during execution of a use case instance.\"}]","UML 2 Tutorial - Use Case Diagram | PDF"]