{"id":4374,"date":"2026-01-19T11:43:13","date_gmt":"2026-01-19T03:43:13","guid":{"rendered":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/identifying-actors\/"},"modified":"2026-01-26T10:32:18","modified_gmt":"2026-01-26T02:32:18","slug":"identifying-actors","status":"publish","type":"docs","link":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/identifying-actors\/","title":{"rendered":"Identifying Actors"},"content":{"rendered":"<p dir=\"auto\">In the <strong>Use Case View<\/strong>, <strong>actors<\/strong> represent the external entities\u2014people, roles, systems, or devices\u2014that interact with your system to achieve goals. Identifying actors is a crucial first step in use case modeling because they define the <strong>boundaries of the system<\/strong> and help uncover the full range of functional requirements. Actors are not internal components; they are always <strong>outside the system boundary<\/strong>, initiating or responding to system behavior.<\/p>\n<p dir=\"auto\">Actors can be:<\/p>\n<ul dir=\"auto\">\n<li><strong>Primary Actors<\/strong>: Those who directly benefit from the system&#8217;s use cases (e.g., a customer placing an order).<\/li>\n<li><strong>Secondary Actors<\/strong>: Supporting roles that the system interacts with to fulfill a primary actor&#8217;s goal (e.g., a payment gateway processing a transaction).<\/li>\n<li><strong>Generalized Actors<\/strong>: Using inheritance to represent common behaviors (e.g., &#8220;User&#8221; as a base for &#8220;Admin&#8221; and &#8220;Regular User&#8221;).<\/li>\n<\/ul>\n<p dir=\"auto\">To identify actors effectively in an Agile context:<\/p>\n<ul dir=\"auto\">\n<li>Start with <strong>stakeholder brainstorming<\/strong>: Ask &#8220;Who uses the system? Who benefits? What external systems integrate?&#8221; Collaborate in workshops to list roles without assuming technology.<\/li>\n<li>Focus on <strong>roles, not individuals<\/strong>: An actor is a role (e.g., &#8220;Doctor&#8221;), even if multiple people play it.<\/li>\n<li>Consider <strong>time-based or conditional actors<\/strong>: E.g., &#8220;Auditor&#8221; for compliance checks.<\/li>\n<li>Validate by <strong>walking through scenarios<\/strong>: For each potential actor, ask &#8220;What goals do they achieve with the system?&#8221; If none, they might not be an actor.<\/li>\n<li>Iterate: Actors evolve as requirements refine\u2014add or refine them in sprints based on feedback.<\/li>\n<\/ul>\n<p dir=\"auto\">This process aligns with Agile by keeping modeling lightweight, collaborative, and focused on user value, avoiding over-analysis while ensuring no key interactions are missed.<\/p>\n<h4 dir=\"auto\">Practical Examples of Identifying Actors in Real-World Projects<\/h4>\n<p dir=\"auto\">Here are concrete examples across domains, illustrating how to spot actors and their roles:<\/p>\n<ul dir=\"auto\">\n<li><strong>Online Banking System<\/strong>:\n<ul dir=\"auto\">\n<li>Primary: Account Holder (views balance, transfers funds).<\/li>\n<li>Secondary: External Bank (for inter-bank transfers), Notification Service (sends alerts).<\/li>\n<li>Benefit: Identifying &#8220;Fraud Detection System&#8221; as a secondary actor early ensures security use cases like &#8220;Flag Suspicious Activity&#8221; are included, reducing risks in production.<\/li>\n<\/ul>\n<\/li>\n<li><strong>E-commerce Website<\/strong>:\n<ul dir=\"auto\">\n<li>Primary: Shopper (browses, purchases), Admin (manages inventory).<\/li>\n<li>Secondary: Shipping Provider (tracks deliveries), Payment Processor.<\/li>\n<li>Practical: Workshop reveals &#8220;Guest User&#8221; as a distinct actor from &#8220;Registered User&#8221; \u2192 adds anonymous checkout flow, boosting conversions.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Hospital Management System<\/strong>:\n<ul dir=\"auto\">\n<li>Primary: Patient (books appointments), Doctor (views records).<\/li>\n<li>Secondary: Insurance Company (verifies coverage), Lab System (processes tests).<\/li>\n<li>Outcome: Recognizing &#8220;Receptionist&#8221; as an actor uncovers administrative use cases, streamlining operations.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Ride-Sharing App<\/strong>:\n<ul dir=\"auto\">\n<li>Primary: Rider (requests ride), Driver (accepts requests).<\/li>\n<li>Secondary: GPS Service (provides navigation), Payment Gateway.<\/li>\n<li>Agile impact: Iteration adds &#8220;Support Agent&#8221; for dispute resolution, based on user feedback.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Smart Thermostat System<\/strong>:\n<ul dir=\"auto\">\n<li>Primary: Homeowner (sets temperature).<\/li>\n<li>Secondary: Weather API (adjusts based on forecast), Utility Company (reports usage).<\/li>\n<li>Example: Identifying &#8220;Mobile App&#8221; as an actor? No\u2014it&#8217;s the interface; the actor is the Homeowner using it.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Library Catalog System<\/strong>:\n<ul dir=\"auto\">\n<li>Primary: Patron (searches books), Librarian (adds items).<\/li>\n<li>Secondary: Inter-Library Loan System (borrows from others).<\/li>\n<li>Benefit: Actors help define boundaries\u2014e.g., excluding &#8220;Publisher&#8221; if no direct integration.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Fitness Wearable Device<\/strong>:\n<ul dir=\"auto\">\n<li>Primary: User (tracks activity).<\/li>\n<li>Secondary: Cloud Sync Service (stores data), Companion App (displays stats).<\/li>\n<li>Practical: Brainstorming adds &#8220;Healthcare Provider&#8221; for data sharing \u2192 enables integration features.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Inventory Tracking for Warehouse<\/strong>:\n<ul dir=\"auto\">\n<li>Primary: Warehouse Worker (scans items), Manager (generates reports).<\/li>\n<li>Secondary: Supplier System (notifies restocks).<\/li>\n<li>Outcome: Clear actors prevent scope creep by focusing only on direct interactions.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Event Management Platform<\/strong>:\n<ul dir=\"auto\">\n<li>Primary: Organizer (creates events), Attendee (registers).<\/li>\n<li>Secondary: Email Service (sends invites).<\/li>\n<li>Agile: Feedback loop refines &#8220;Sponsor&#8221; as an actor for promotional use cases.<\/li>\n<\/ul>\n<\/li>\n<li><strong>ATM Machine<\/strong>:\n<ul dir=\"auto\">\n<li>Primary: Customer (withdraws cash).<\/li>\n<li>Secondary: Bank Network (authorizes transactions).<\/li>\n<li>Classic: Ensures actors like &#8220;Maintenance Technician&#8221; are considered for non-customer use cases.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p dir=\"auto\">In Visual Paradigm, you&#8217;ll add actors to your use case diagram, connect them to use cases via associations, and use generalization for role hierarchies\u2014all while keeping the model agile and traceable to requirements.<\/p>\n<p dir=\"auto\">With actors identified, the next step is <a href=\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/use-case-relationships\/\">exploring <strong>use case relationships<\/strong><\/a> to organize and reuse behaviors efficiently.<\/p>\n","protected":false},"featured_media":0,"parent":4366,"menu_order":1,"comment_status":"open","ping_status":"closed","template":"","meta":{"_yoast_wpseo_title":"","_yoast_wpseo_metadesc":"","_eb_attr":"","neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":""},"doc_tag":[],"class_list":["post-4374","docs","type-docs","status-publish","hentry"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Identifying Actors - Visual Paradigm Guides Japanese<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/identifying-actors\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Identifying Actors - Visual Paradigm Guides Japanese\" \/>\n<meta property=\"og:description\" content=\"In the Use Case View, actors represent the external entities\u2014people, roles, systems, or devices\u2014that interact with your system to achieve goals. Identifying actors is a crucial first step in use case modeling because they define the boundaries of the system and help uncover the full range of functional requirements. Actors are not internal components; they are always outside the system boundary, initiating or responding to system behavior. Actors can be: Primary Actors: Those who directly benefit from the system&#8217;s use cases (e.g., a customer placing an order). Secondary Actors: Supporting roles that the system interacts with to fulfill a primary actor&#8217;s goal (e.g., a payment gateway processing a transaction). Generalized Actors: Using inheritance to represent common behaviors (e.g., &#8220;User&#8221; as a base for &#8220;Admin&#8221; and &#8220;Regular User&#8221;). To identify actors effectively in an Agile context: Start with stakeholder brainstorming: Ask &#8220;Who usIdentifying Actors\" \/>\n<meta property=\"og:url\" content=\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/identifying-actors\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Guides Japanese\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-26T02:32:18+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593\" \/>\n\t<meta name=\"twitter:data1\" content=\"3\u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/identifying-actors\/\",\"url\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/identifying-actors\/\",\"name\":\"Identifying Actors - Visual Paradigm Guides Japanese\",\"isPartOf\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-01-19T03:43:13+00:00\",\"dateModified\":\"2026-01-26T02:32:18+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/identifying-actors\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/identifying-actors\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/identifying-actors\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/guides.visual-paradigm.com\/ja\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Mastering UML 2.5: A Use Case Driven Approach to Agile Modeling\",\"item\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Module 2: The Driver \u2013 Use Case Driven Requirements\",\"item\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Identifying Actors\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/#website\",\"url\":\"https:\/\/guides.visual-paradigm.com\/ja\/\",\"name\":\"Visual Paradigm Guides Japanese\",\"description\":\"Smart guides for an AI-driven world\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/guides.visual-paradigm.com\/ja\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Identifying Actors - Visual Paradigm Guides Japanese","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/identifying-actors\/","og_locale":"ja_JP","og_type":"article","og_title":"Identifying Actors - Visual Paradigm Guides Japanese","og_description":"In the Use Case View, actors represent the external entities\u2014people, roles, systems, or devices\u2014that interact with your system to achieve goals. Identifying actors is a crucial first step in use case modeling because they define the boundaries of the system and help uncover the full range of functional requirements. Actors are not internal components; they are always outside the system boundary, initiating or responding to system behavior. Actors can be: Primary Actors: Those who directly benefit from the system&#8217;s use cases (e.g., a customer placing an order). Secondary Actors: Supporting roles that the system interacts with to fulfill a primary actor&#8217;s goal (e.g., a payment gateway processing a transaction). Generalized Actors: Using inheritance to represent common behaviors (e.g., &#8220;User&#8221; as a base for &#8220;Admin&#8221; and &#8220;Regular User&#8221;). To identify actors effectively in an Agile context: Start with stakeholder brainstorming: Ask &#8220;Who usIdentifying Actors","og_url":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/identifying-actors\/","og_site_name":"Visual Paradigm Guides Japanese","article_modified_time":"2026-01-26T02:32:18+00:00","twitter_card":"summary_large_image","twitter_misc":{"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"3\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/identifying-actors\/","url":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/identifying-actors\/","name":"Identifying Actors - Visual Paradigm Guides Japanese","isPartOf":{"@id":"https:\/\/guides.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-01-19T03:43:13+00:00","dateModified":"2026-01-26T02:32:18+00:00","breadcrumb":{"@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/identifying-actors\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/identifying-actors\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/identifying-actors\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/guides.visual-paradigm.com\/ja\/"},{"@type":"ListItem","position":2,"name":"Mastering UML 2.5: A Use Case Driven Approach to Agile Modeling","item":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/"},{"@type":"ListItem","position":3,"name":"Module 2: The Driver \u2013 Use Case Driven Requirements","item":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/"},{"@type":"ListItem","position":4,"name":"Identifying Actors"}]},{"@type":"WebSite","@id":"https:\/\/guides.visual-paradigm.com\/ja\/#website","url":"https:\/\/guides.visual-paradigm.com\/ja\/","name":"Visual Paradigm Guides Japanese","description":"Smart guides for an AI-driven world","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/guides.visual-paradigm.com\/ja\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"}]}},"comment_count":0,"_links":{"self":[{"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4374","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/comments?post=4374"}],"version-history":[{"count":7,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4374\/revisions"}],"predecessor-version":[{"id":5169,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4374\/revisions\/5169"}],"up":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4366"}],"next":[{"title":"Use Case Relationships","link":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/use-case-relationships\/","href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4375"}],"prev":[{"title":"Use Case View","link":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/use-case-view\/","href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4372"}],"wp:attachment":[{"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=4374"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=4374"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}