{"id":4061,"date":"2026-01-15T10:53:35","date_gmt":"2026-01-15T02:53:35","guid":{"rendered":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/"},"modified":"2026-01-22T11:34:02","modified_gmt":"2026-01-22T03:34:02","slug":"iterative-use-case-refinement","status":"publish","type":"docs","link":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/","title":{"rendered":"Iterative Use Case Refinement"},"content":{"rendered":"<p dir=\"auto\"><strong>Iterative Use Case Refinement: Using AI to Intelligently Add &#8220;extend&#8221; and &#8220;include&#8221; Relationships Based on UML Best Practices<\/strong><\/p>\n<p dir=\"auto\">With a clean <a href=\"https:\/\/www.visual-paradigm.com\/guide\/uml-unified-modeling-language\/what-is-use-case-diagram\/\">Use Case Diagram<\/a> and detailed Activity flows in place, the functional model is already far more mature than most projects achieve in the early stages. However, real-world systems rarely consist of completely independent use cases. Many behaviors are shared, conditional, or variations of a base flow\u2014exactly the scenarios where UML\u2019s <strong>\u00abinclude\u00bb<\/strong> and <strong>\u00abextend\u00bb<\/strong> relationships provide powerful modularity, reusability, and clarity.<\/p>\n<p dir=\"auto\">Manually deciding where and how to apply these relationships is notoriously error-prone:<\/p>\n<ul dir=\"auto\">\n<li>Teams overuse \u00abinclude\u00bb for every common step, creating overly fragmented models.<\/li>\n<li>\u00abextend\u00bb is frequently confused with generalization or alternative flows.<\/li>\n<li>Relationships are added inconsistently across diagrams.<\/li>\n<li>Adding or changing one relationship often requires tedious manual repositioning of ovals, rerouting of dashed lines, and layout cleanup.<\/li>\n<\/ul>\n<p dir=\"auto\"><a href=\"https:\/\/www.visual-paradigm.com\/\">Visual Paradigm<\/a>\u2019s AI ecosystem solves this through <strong>iterative, intelligence-driven refinement<\/strong>. Using the <a href=\"https:\/\/chat.visual-paradigm.com\/\"><strong>AI Chatbot<\/strong><\/a> in conversational mode or dedicated <strong>Step-Based Apps<\/strong> (such as the Use Case Diagram Refinement Tool or Use Case Relationship Suggester), the AI analyzes your existing use cases, scenarios, and domain context\u2014then proposes precise, UML 2.5-compliant \u00abinclude\u00bb and \u00abextend\u00bb relationships following established best practices.<\/p>\n<h3 dir=\"auto\">How Iterative Refinement Works<\/h3>\n<ol dir=\"auto\">\n<li>\n<p dir=\"auto\"><strong>Start with Your Base Diagram<\/strong> Assume you already have a generated Use Case Diagram (from plain English prompts or textual analysis) showing primary use cases and actors.<\/p>\n<p id=\"cKKscOR\"><img fetchpriority=\"high\" decoding=\"async\" width=\"842\" height=\"574\" class=\"alignnone size-full wp-image-4970 \" src=\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a4e16567.png\" alt=\"\" srcset=\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a4e16567.png 842w, https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a4e16567-300x205.png 300w, https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a4e16567-768x524.png 768w, https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a4e16567-150x102.png 150w\" sizes=\"(max-width: 842px) 100vw, 842px\" \/><\/p>\n<\/li>\n<li>\n<p dir=\"auto\"><strong>Invoke Refinement in Natural Language<\/strong> In the AI Chatbot, simply describe the desired behavior or ask for suggestions:<\/p>\n<ul dir=\"auto\">\n<li>\u201cRefine this use case diagram by adding appropriate include and extend relationships.\u201d<\/li>\n<li>\u201cShow that \u2018Authenticate User\u2019 is included by \u2018Place Order\u2019, \u2018Track Shipment\u2019, and \u2018Write Review\u2019.\u201d<\/li>\n<li>\u201cSuggest extend relationships: for example, \u2018Apply Coupon\u2019 should extend \u2018Checkout\u2019 only for eligible orders.\u201d<\/li>\n<li>\u201cMake \u2018Handle International Shipping\u2019 an optional extension of \u2018Process Order\u2019 when the destination is outside the country.\u201d<\/li>\n<li>\u201cSuggest include relationships: for example, &#8216;Track Shipment&#8217; and &#8216;Place Order&#8217; both include a common use case &#8216;Manage Account&#8217;\u201d\n<p id=\"NgFvgZT\"><img decoding=\"async\" width=\"926\" height=\"728\" class=\"alignnone size-full wp-image-4969 \" src=\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a3900e89.png\" alt=\"\" srcset=\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a3900e89.png 926w, https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a3900e89-300x236.png 300w, https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a3900e89-768x604.png 768w, https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a3900e89-150x118.png 150w\" sizes=\"(max-width: 926px) 100vw, 926px\" \/><\/p>\n<\/li>\n<\/ul>\n<\/li>\n<li>\n<p dir=\"auto\"><strong>AI Analyzes and Proposes<\/strong> The AI evaluates:<\/p>\n<ul dir=\"auto\">\n<li>Reusability \u2014 Common sub-goals that appear in multiple use cases \u2192 strong candidate for \u00abinclude\u00bb.<\/li>\n<li>Conditional\/optional behavior \u2014 Variations or add-ons that occur only under certain conditions \u2192 candidate for \u00abextend\u00bb.<\/li>\n<li>Semantic fit \u2014 Uses linguistic patterns, scenario text, and UML metamodel rules to avoid misuse (e.g., no \u00abinclude\u00bb for optional steps).<\/li>\n<li>Best practices \u2014 Follows guidelines such as:\n<ul dir=\"auto\">\n<li>\u00abinclude\u00bb for mandatory, reusable fragments (base use case is incomplete without it).<\/li>\n<li>\u00abextend\u00bb for optional or conditional extensions (base use case is complete on its own).<\/li>\n<li>Clear extension points named when appropriate.<\/li>\n<li>Avoidance of over-fragmentation or circular dependencies.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p dir=\"auto\">It then suggests additions with rationale, e.g.:<\/p>\n<ul dir=\"auto\">\n<li>\u00abinclude\u00bb \u2192 \u201cAuthenticate User\u201d included by \u201cPlace Order\u201d, \u201cTrack Shipment\u201d, \u201cManage Account\u201d <em>Rationale<\/em>: Authentication is a mandatory prerequisite shared across multiple user goals.<\/li>\n<li>\u00abextend\u00bb \u2192 \u201cApply Loyalty Discount\u201d extends \u201cCheckout\u201d at extension point \u201cBefore Payment Summary\u201d <em>Rationale<\/em>: Discount is optional and only applies if the customer has loyalty points.<\/li>\n<\/ul>\n<\/li>\n<li>\n<p dir=\"auto\"><strong>One-Click or Conversational Application<\/strong><\/p>\n<ul dir=\"auto\">\n<li>Accept all suggestions \u2192 AI adds dashed arrows with \u00abinclude\u00bb \/ \u00abextend\u00bb keywords, correctly orients extension points (if named), and auto-adjusts layout.<\/li>\n<li>Selective application \u2192 \u201cAdd only the authentication include relationships for now.\u201d<\/li>\n<li>Further refinement \u2192 \u201cRename the extension point to \u2018During Order Summary\u2019 and move the \u2018Apply Coupon\u2019 oval closer to \u2018Checkout\u2019.\u201d<\/li>\n<\/ul>\n<p dir=\"auto\"><strong>Diagram Touch-Up<\/strong> technology ensures:<\/p>\n<ul dir=\"auto\">\n<li>No overlapping lines<\/li>\n<li>Consistent arrow styles (dashed with open arrowhead for \u00abextend\u00bb, dashed with \u00abinclude\u00bb label)<\/li>\n<li>Logical grouping of related use cases<\/li>\n<li>Preserved readability even after multiple iterations<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<h3 dir=\"auto\">UML Best-Practice Guidance Built In<\/h3>\n<p dir=\"auto\">The AI embeds key rules to prevent common mistakes:<\/p>\n<ul dir=\"auto\">\n<li>Use \u00abinclude\u00bb when the included behavior is <strong>always required<\/strong> and represents a <strong>reusable fragment<\/strong> (not optional).<\/li>\n<li>Use \u00abextend\u00bb when the extending behavior is <strong>conditional<\/strong>, <strong>optional<\/strong>, or <strong>adds variation<\/strong> without altering the base flow\u2019s completion.<\/li>\n<li>Name extension points explicitly for clarity in complex cases.<\/li>\n<li>Avoid chaining too many includes\/extends\u2014keep use cases high-level and goal-focused.<\/li>\n<li>Prefer generalization over \u00abextend\u00bb when use cases represent true subtypes (e.g., \u201cProcess Credit Card Payment\u201d generalizes \u201cProcess Payment\u201d).<\/li>\n<\/ul>\n<h3 dir=\"auto\">Practical Benefits in Real Projects<\/h3>\n<ul dir=\"auto\">\n<li><strong>Modularity &amp; Maintainability<\/strong> \u2014 Shared behaviors (login, validation, notification) modeled once and reused.<\/li>\n<li><strong>Reduced Diagram Clutter<\/strong> \u2014 Base use cases remain concise; details factored out cleanly.<\/li>\n<li><strong>Improved Traceability<\/strong> \u2014 Stakeholders see exactly where optional or shared logic lives.<\/li>\n<li><strong>Faster Evolution<\/strong> \u2014 New requirements (e.g., \u201cAdd gift wrapping option\u201d) become simple extensions instead of rewriting core flows.<\/li>\n<li><strong>Team Consistency<\/strong> \u2014 AI enforces the same best-practice heuristics across all modelers.<\/li>\n<\/ul>\n<h3 dir=\"auto\">Example Before &amp; After Refinement (Conceptual)<\/h3>\n<p dir=\"auto\"><strong>Before<\/strong> (flat list of use cases): Place Order \u2013 Checkout \u2013 Apply Coupon \u2013 Process Payment \u2013 Track Shipment \u2013 Authenticate User<\/p>\n<p dir=\"auto\"><strong>After AI Refinement<\/strong>:<\/p>\n<ul dir=\"auto\">\n<li>Authenticate User \u00abinclude\u00bb by Place Order, Track Shipment, Manage Account<\/li>\n<li>Apply Coupon \u00abextend\u00bb Checkout (extension point: Before Payment Summary)<\/li>\n<li>Process International Shipping \u00abextend\u00bb Process Order (condition: destination \u2260 domestic)<\/li>\n<\/ul>\n<p dir=\"auto\">This refinement turns a simple list into a modular, expressive functional model\u2014automatically and correctly.<\/p>\n<p dir=\"auto\">By mastering iterative refinement, you ensure your use case model is not just complete but elegant, reusable, and maintainable\u2014qualities that pay dividends when the model informs detailed sequence diagrams, test planning, UI flows, and implementation.<\/p>\n<p dir=\"auto\">With boundaries defined, flows visualized, and relationships intelligently applied, the functional view is now robust and ready to serve as the foundation for dynamic behavioral modeling in <a href=\"https:\/\/guides.visual-paradigm.com\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-5-modeling-behavioral-dynamics-and-interactions\/\">Module 5<\/a>.<\/p>\n","protected":false},"featured_media":0,"parent":4058,"menu_order":2,"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-4061","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>Iterative Use Case Refinement - Visual Paradigm Guides Spanish<\/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\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Iterative Use Case Refinement - Visual Paradigm Guides Spanish\" \/>\n<meta property=\"og:description\" content=\"Iterative Use Case Refinement: Using AI to Intelligently Add &#8220;extend&#8221; and &#8220;include&#8221; Relationships Based on UML Best Practices With a clean Use Case Diagram and detailed Activity flows in place, the functional model is already far more mature than most projects achieve in the early stages. However, real-world systems rarely consist of completely independent use cases. Many behaviors are shared, conditional, or variations of a base flow\u2014exactly the scenarios where UML\u2019s \u00abinclude\u00bb and \u00abextend\u00bb relationships provide powerful modularity, reusability, and clarity. Manually deciding where and how to apply these relationships is notoriously error-prone: Teams overuse \u00abinclude\u00bb for every common step, creating overly fragmented models. \u00abextend\u00bb is frequently confused with generalization or alternative flows. Relationships are added inconsistently across diagrams. Adding or changing one relationship often requires tedious manual repositioning of ovals, rerouting of dashed lines, and layout cleanup. Visual Paradigm\u2019s AI ecosystem solves this through iterative, intelligence-driven refinement. Using the AI Chatbot in conversational mode or dedicated Step-Based Apps (such as the Use Case Diagram Refinement Tool or Use Case Relationship Suggester), the AI analyzes your existing use cases, scenarios, and domain context\u2014then proposes precise, UML 2.5-compliant \u00abinclude\u00bb and \u00abextend\u00bb relationships following established best practices. How Iterative Refinement Works Start with Your Base Diagram Assume you already have a generated Use Case Diagram (from plain English prompts or textual analysis) showing primary use cases and actors. Invoke Refinement in Natural Language In the AI Chatbot, simply describe the desired behavior or ask for suggestions: \u201cRefine this use case diagram by adding appropriate include and extend relationships.\u201d \u201cShow that \u2018Authenticate User\u2019 is included by \u2018Place Order\u2019, \u2018Track Shipment\u2019, and \u2018Write Review\u2019.\u201d \u201cSuggest extend relationships: for example, \u2018Apply Coupon\u2019 should extend \u2018Checkout\u2019 only for eligible orders.\u201d \u201cMake \u2018Handle International Shipping\u2019 an optional extension of \u2018Process Order\u2019 when the destination is outside the country.\u201d \u201cSuggest include relationships: for example, &#8216;Track Shipment&#8217; and &#8216;Place Order&#8217; both include a common use case &#8216;Manage Account&#8217;\u201d AI Analyzes and Proposes The AI evaluates: Reusability \u2014 Common sub-goals that appear in multiple use cases \u2192 strong candidate for \u00abinclude\u00bb. Conditional\/optional behavior \u2014 Variations or add-ons that occur only under certain conditions \u2192 candidate for \u00abextend\u00bb. Semantic fit \u2014 Uses linguistic patterns, scenario text, and UML metamodel rules to avoid misuse (e.g., no \u00abinclude\u00bb for optional steps). Best practices \u2014 Follows guidelines such as: \u00abinclude\u00bb for mandatory, reusable fragments (base use case is incomplete without it). \u00abextend\u00bb for optional or conditional extensions (base use case is complete on its own). Clear extension points named when appropriate. Avoidance of over-fragmentation or circular dependencies. It then suggests additions with rationale, e.g.: \u00abinclude\u00bb \u2192 \u201cAuthenticate User\u201d included by \u201cPlace Order\u201d, \u201cTrack Shipment\u201d, \u201cManage Account\u201d Rationale: Authentication is a mandatory prerequisite shared across multiple user goals. \u00abextend\u00bb \u2192 \u201cApply Loyalty Discount\u201d extends \u201cCheckout\u201d at extension point \u201cBefore Payment Summary\u201d Rationale: Discount is optional and only applies if the customer has loyalty points. One-Click or Conversational Application Accept all suggestions \u2192 AI adds dashed arrows with \u00abinclude\u00bb \/ \u00abextend\u00bb keywords, correctly orients extension points (if named), and auto-adjusts layout. Selective application \u2192 \u201cAdd only the authentication include relationships for now.\u201d Further refinement \u2192 \u201cRename the extension point to \u2018During Order Summary\u2019 and move the \u2018Apply Coupon\u2019 oval closer to \u2018Checkout\u2019.\u201d Diagram Touch-Up technology ensures: No overlapping lines Consistent arrow styles (dashed with open arrowhead for \u00abextend\u00bb, dashed with \u00abinclude\u00bb label) Logical grouping of related use cases Preserved readability even after multiple iterations UML Best-Practice Guidance Built In The AI embeds key rules to prevent common mistakes: Use \u00abinclude\u00bb when the included behavior is always required and represents a reusable fragment (not optional). Use \u00abextend\u00bb when the extending behavior is conditional, optional, or adds variation without altering the base flow\u2019s completion. Name extension points explicitly for clarity in complex cases. Avoid chaining too many includes\/extends\u2014keep use cases high-level and goal-focused. Prefer generalization over \u00abextend\u00bb when use cases represent true subtypes (e.g., \u201cProcess Credit Card Payment\u201d generalizes \u201cProcess Payment\u201d). Practical Benefits in Real Projects Modularity &amp; Maintainability \u2014 Shared behaviors (login, validation, notification) modeled once and reused. Reduced Diagram Clutter \u2014 Base use cases remain concise; details factored out cleanly. Improved Traceability \u2014 Stakeholders see exactly where optional or shared logic lives. Faster Evolution \u2014 New requirements (e.g., \u201cAdd gift wrapping option\u201d) become simple extensions instead of rewriting core flows. Team Consistency \u2014 AI enforces the same best-practice heuristics across all modelers. Example Before &amp; After Refinement (Conceptual) Before (flat list of use cases): Place Order \u2013 Checkout \u2013 Apply Coupon \u2013 Process Payment \u2013 Track Shipment \u2013 Authenticate User After AI Refinement: Authenticate User \u00abinclude\u00bb by Place Order, Track Shipment, Manage Account Apply Coupon \u00abextend\u00bb Checkout (extension point: Before Payment Summary) Process International Shipping \u00abextend\u00bb Process Order (condition: destination \u2260 domestic) This refinement turns a simple list into a modular, expressive functional model\u2014automatically and correctly. By mastering iterative refinement, you ensure your use case model is not just complete but elegant, reusable, and maintainable\u2014qualities that pay dividends when the model informs detailed sequence diagrams, test planning, UI flows, and implementation. With boundaries defined, flows visualized, and relationships intelligently applied, the functional view is now robust and ready to serve as the foundation for dynamic behavioral modeling in Module 5.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Guides Spanish\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-22T03:34:02+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a4e16567.png\" \/>\n\t<meta property=\"og:image:width\" content=\"842\" \/>\n\t<meta property=\"og:image:height\" content=\"574\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tiempo de lectura\" \/>\n\t<meta name=\"twitter:data1\" content=\"5 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/\",\"url\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/\",\"name\":\"Iterative Use Case Refinement - Visual Paradigm Guides Spanish\",\"isPartOf\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a4e16567.png\",\"datePublished\":\"2026-01-15T02:53:35+00:00\",\"dateModified\":\"2026-01-22T03:34:02+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/#primaryimage\",\"url\":\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a4e16567.png\",\"contentUrl\":\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a4e16567.png\",\"width\":842,\"height\":574},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/guides.visual-paradigm.com\/es\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Mastering UML Visual Modeling in the Visual Paradigm AI Ecosystem\",\"item\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Module 3: Functional Modeling and Use Case Elaboration\",\"item\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Iterative Use Case Refinement\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/#website\",\"url\":\"https:\/\/guides.visual-paradigm.com\/es\/\",\"name\":\"Visual Paradigm Guides Spanish\",\"description\":\"Smart guides for an AI-driven world\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/guides.visual-paradigm.com\/es\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Iterative Use Case Refinement - Visual Paradigm Guides Spanish","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\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/","og_locale":"es_ES","og_type":"article","og_title":"Iterative Use Case Refinement - Visual Paradigm Guides Spanish","og_description":"Iterative Use Case Refinement: Using AI to Intelligently Add &#8220;extend&#8221; and &#8220;include&#8221; Relationships Based on UML Best Practices With a clean Use Case Diagram and detailed Activity flows in place, the functional model is already far more mature than most projects achieve in the early stages. However, real-world systems rarely consist of completely independent use cases. Many behaviors are shared, conditional, or variations of a base flow\u2014exactly the scenarios where UML\u2019s \u00abinclude\u00bb and \u00abextend\u00bb relationships provide powerful modularity, reusability, and clarity. Manually deciding where and how to apply these relationships is notoriously error-prone: Teams overuse \u00abinclude\u00bb for every common step, creating overly fragmented models. \u00abextend\u00bb is frequently confused with generalization or alternative flows. Relationships are added inconsistently across diagrams. Adding or changing one relationship often requires tedious manual repositioning of ovals, rerouting of dashed lines, and layout cleanup. Visual Paradigm\u2019s AI ecosystem solves this through iterative, intelligence-driven refinement. Using the AI Chatbot in conversational mode or dedicated Step-Based Apps (such as the Use Case Diagram Refinement Tool or Use Case Relationship Suggester), the AI analyzes your existing use cases, scenarios, and domain context\u2014then proposes precise, UML 2.5-compliant \u00abinclude\u00bb and \u00abextend\u00bb relationships following established best practices. How Iterative Refinement Works Start with Your Base Diagram Assume you already have a generated Use Case Diagram (from plain English prompts or textual analysis) showing primary use cases and actors. Invoke Refinement in Natural Language In the AI Chatbot, simply describe the desired behavior or ask for suggestions: \u201cRefine this use case diagram by adding appropriate include and extend relationships.\u201d \u201cShow that \u2018Authenticate User\u2019 is included by \u2018Place Order\u2019, \u2018Track Shipment\u2019, and \u2018Write Review\u2019.\u201d \u201cSuggest extend relationships: for example, \u2018Apply Coupon\u2019 should extend \u2018Checkout\u2019 only for eligible orders.\u201d \u201cMake \u2018Handle International Shipping\u2019 an optional extension of \u2018Process Order\u2019 when the destination is outside the country.\u201d \u201cSuggest include relationships: for example, &#8216;Track Shipment&#8217; and &#8216;Place Order&#8217; both include a common use case &#8216;Manage Account&#8217;\u201d AI Analyzes and Proposes The AI evaluates: Reusability \u2014 Common sub-goals that appear in multiple use cases \u2192 strong candidate for \u00abinclude\u00bb. Conditional\/optional behavior \u2014 Variations or add-ons that occur only under certain conditions \u2192 candidate for \u00abextend\u00bb. Semantic fit \u2014 Uses linguistic patterns, scenario text, and UML metamodel rules to avoid misuse (e.g., no \u00abinclude\u00bb for optional steps). Best practices \u2014 Follows guidelines such as: \u00abinclude\u00bb for mandatory, reusable fragments (base use case is incomplete without it). \u00abextend\u00bb for optional or conditional extensions (base use case is complete on its own). Clear extension points named when appropriate. Avoidance of over-fragmentation or circular dependencies. It then suggests additions with rationale, e.g.: \u00abinclude\u00bb \u2192 \u201cAuthenticate User\u201d included by \u201cPlace Order\u201d, \u201cTrack Shipment\u201d, \u201cManage Account\u201d Rationale: Authentication is a mandatory prerequisite shared across multiple user goals. \u00abextend\u00bb \u2192 \u201cApply Loyalty Discount\u201d extends \u201cCheckout\u201d at extension point \u201cBefore Payment Summary\u201d Rationale: Discount is optional and only applies if the customer has loyalty points. One-Click or Conversational Application Accept all suggestions \u2192 AI adds dashed arrows with \u00abinclude\u00bb \/ \u00abextend\u00bb keywords, correctly orients extension points (if named), and auto-adjusts layout. Selective application \u2192 \u201cAdd only the authentication include relationships for now.\u201d Further refinement \u2192 \u201cRename the extension point to \u2018During Order Summary\u2019 and move the \u2018Apply Coupon\u2019 oval closer to \u2018Checkout\u2019.\u201d Diagram Touch-Up technology ensures: No overlapping lines Consistent arrow styles (dashed with open arrowhead for \u00abextend\u00bb, dashed with \u00abinclude\u00bb label) Logical grouping of related use cases Preserved readability even after multiple iterations UML Best-Practice Guidance Built In The AI embeds key rules to prevent common mistakes: Use \u00abinclude\u00bb when the included behavior is always required and represents a reusable fragment (not optional). Use \u00abextend\u00bb when the extending behavior is conditional, optional, or adds variation without altering the base flow\u2019s completion. Name extension points explicitly for clarity in complex cases. Avoid chaining too many includes\/extends\u2014keep use cases high-level and goal-focused. Prefer generalization over \u00abextend\u00bb when use cases represent true subtypes (e.g., \u201cProcess Credit Card Payment\u201d generalizes \u201cProcess Payment\u201d). Practical Benefits in Real Projects Modularity &amp; Maintainability \u2014 Shared behaviors (login, validation, notification) modeled once and reused. Reduced Diagram Clutter \u2014 Base use cases remain concise; details factored out cleanly. Improved Traceability \u2014 Stakeholders see exactly where optional or shared logic lives. Faster Evolution \u2014 New requirements (e.g., \u201cAdd gift wrapping option\u201d) become simple extensions instead of rewriting core flows. Team Consistency \u2014 AI enforces the same best-practice heuristics across all modelers. Example Before &amp; After Refinement (Conceptual) Before (flat list of use cases): Place Order \u2013 Checkout \u2013 Apply Coupon \u2013 Process Payment \u2013 Track Shipment \u2013 Authenticate User After AI Refinement: Authenticate User \u00abinclude\u00bb by Place Order, Track Shipment, Manage Account Apply Coupon \u00abextend\u00bb Checkout (extension point: Before Payment Summary) Process International Shipping \u00abextend\u00bb Process Order (condition: destination \u2260 domestic) This refinement turns a simple list into a modular, expressive functional model\u2014automatically and correctly. By mastering iterative refinement, you ensure your use case model is not just complete but elegant, reusable, and maintainable\u2014qualities that pay dividends when the model informs detailed sequence diagrams, test planning, UI flows, and implementation. With boundaries defined, flows visualized, and relationships intelligently applied, the functional view is now robust and ready to serve as the foundation for dynamic behavioral modeling in Module 5.","og_url":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/","og_site_name":"Visual Paradigm Guides Spanish","article_modified_time":"2026-01-22T03:34:02+00:00","og_image":[{"width":842,"height":574,"url":"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a4e16567.png","type":"image\/png"}],"twitter_card":"summary_large_image","twitter_misc":{"Tiempo de lectura":"5 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/","url":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/","name":"Iterative Use Case Refinement - Visual Paradigm Guides Spanish","isPartOf":{"@id":"https:\/\/guides.visual-paradigm.com\/es\/#website"},"primaryImageOfPage":{"@id":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/#primaryimage"},"image":{"@id":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/#primaryimage"},"thumbnailUrl":"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a4e16567.png","datePublished":"2026-01-15T02:53:35+00:00","dateModified":"2026-01-22T03:34:02+00:00","breadcrumb":{"@id":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/"]}]},{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/#primaryimage","url":"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a4e16567.png","contentUrl":"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_69719a4e16567.png","width":842,"height":574},{"@type":"BreadcrumbList","@id":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/iterative-use-case-refinement\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/guides.visual-paradigm.com\/es\/"},{"@type":"ListItem","position":2,"name":"Mastering UML Visual Modeling in the Visual Paradigm AI Ecosystem","item":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/"},{"@type":"ListItem","position":3,"name":"Module 3: Functional Modeling and Use Case Elaboration","item":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/"},{"@type":"ListItem","position":4,"name":"Iterative Use Case Refinement"}]},{"@type":"WebSite","@id":"https:\/\/guides.visual-paradigm.com\/es\/#website","url":"https:\/\/guides.visual-paradigm.com\/es\/","name":"Visual Paradigm Guides Spanish","description":"Smart guides for an AI-driven world","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/guides.visual-paradigm.com\/es\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es"}]}},"comment_count":0,"_links":{"self":[{"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4061","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/comments?post=4061"}],"version-history":[{"count":4,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4061\/revisions"}],"predecessor-version":[{"id":4971,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4061\/revisions\/4971"}],"up":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4058"}],"prev":[{"title":"Narrative to Activity Diagram Transformation","link":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-visual-modeling-in-the-visual-paradigm-ai-ecosystem\/module-3-functional-modeling-and-use-case-elaboration\/narrative-to-activity-diagram-transformation\/","href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4060"}],"wp:attachment":[{"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media?parent=4061"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/doc_tag?post=4061"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}