{"id":3481,"date":"2022-02-09T17:13:56","date_gmt":"2022-02-09T09:13:56","guid":{"rendered":"https:\/\/blog.visual-paradigm.com\/es\/?p=3481"},"modified":"2022-11-25T17:26:20","modified_gmt":"2022-11-25T09:26:20","slug":"include-and-extend-use-cases","status":"publish","type":"post","link":"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/","title":{"rendered":"Casos De Uso “Incluir” Y “Extender”"},"content":{"rendered":"

Un caso de\u00a0<\/span>uso<\/span><\/a>\u00a0describe c\u00f3mo un usuario usa un sistema para lograr un objetivo particular.\u00a0Un diagrama de casos de uso consta del sistema, los casos de uso relacionados y los actores, y los relaciona entre s\u00ed para visualizar: \u00bfqu\u00e9 se est\u00e1 describiendo?\u00a0(\u00a0<\/span>sistema<\/span><\/strong>\u00a0), \u00bfqui\u00e9n est\u00e1 usando el sistema?\u00a0(\u00a0<\/span>actores<\/span><\/strong>\u00a0) y \u00bfqu\u00e9 quieren lograr los actores?\u00a0(\u00a0<\/span>casos de uso<\/span><\/strong>\u00a0), por lo tanto, los casos de uso ayudan a garantizar que se desarrolle el sistema correcto al capturar los requisitos desde el punto de vista del usuario.<\/span><\/p>\n

\"Plantilla<\/h3>\n

Estructuraci\u00f3n de casos de uso<\/span><\/span><\/h2>\n

Las relaciones de casos de uso modelan las dependencias entre casos de uso en el modelo de interacci\u00f3n del sistema.\u00a0Aunque, los casos de uso independientes pueden representar adecuadamente sistemas m\u00e1s simples.\u00a0Sin embargo, para representar sistemas complejos o grandes, es posible que necesitemos construir casos de uso complejos con la ayuda de dependencias entre casos de uso.\u00a0Establecer relaciones entre casos de uso permite reutilizar aquellos casos de uso que deben definirse una y otra vez, lo que reduce el esfuerzo del desarrollador.<\/span><\/p>\n

UML define tres estereotipos para estructurar las asociaciones de casos de uso.<\/span><\/p>\n

\u00bfQu\u00e9 es un caso de uso <<Incluir>>?<\/span><\/span><\/h3>\n

Un caso de uso extendido es, efectivamente, un curso alternativo del caso de uso base.\u00a0El caso de uso <<extender>> logra esto mediante la inserci\u00f3n conceptual de secuencias de acci\u00f3n adicionales en la secuencia base del caso de uso.<\/span><\/p>\n

El momento de usar la relaci\u00f3n <<include>> es despu\u00e9s de haber completado la descripci\u00f3n del primer corte de todos sus casos de uso principales.\u00a0Ahora puede ver los casos de uso e identificar secuencias comunes de interacci\u00f3n usuario-sistema.<\/span><\/p>\n

    \n
  • Cuando un caso de uso se representa usando la funcionalidad de otro caso de uso, la relaci\u00f3n entre los casos de uso se denomina relaci\u00f3n de inclusi\u00f3n o uso.<\/span><\/li>\n
  • Un caso de uso incluye la funcionalidad descrita en otro caso de uso como parte de su flujo de proceso comercial.<\/span><\/li>\n
  • Una relaci\u00f3n de usos del caso de uso base al caso de uso secundario indica que una instancia del caso de uso base incluir\u00e1 el comportamiento como se especifica en el caso de uso secundario.<\/span><\/li>\n
  • Una relaci\u00f3n de inclusi\u00f3n se representa con una flecha dirigida que tiene una l\u00ednea de puntos.\u00a0La punta de la punta de flecha apunta al caso de uso secundario y al caso de uso principal conectado en la base de la flecha.<\/span><\/li>\n
  • El estereotipo \u201c<<include>>\u201d identifica la relaci\u00f3n como una relaci\u00f3n de inclusi\u00f3n.<\/span><\/li>\n<\/ul>\n

    Ejemplo de caso de uso: incluir relaci\u00f3n<\/span><\/span><\/h3>\n

    La relaci\u00f3n de inclusi\u00f3n agrega funcionalidad adicional no especificada en el caso de uso base.\u00a0La relaci\u00f3n <<Include>> se utiliza para incluir el comportamiento com\u00fan de un caso de uso incluido en un caso de uso base para admitir la reutilizaci\u00f3n del comportamiento com\u00fan.<\/span><\/p>\n

    \"Notaci\u00f3n<\/p>\n

    \u00bfQu\u00e9 es un caso de uso <<extender>>?<\/span><\/strong><\/span><\/h3>\n

    \"Notaci\u00f3n<\/p>\n

      \n
    • Indica que un\u00a0 caso de uso de\u00a0<\/span>“Contrase\u00f1a no v\u00e1lida”<\/span><\/strong>\u00a0\u00a0puede incluir (sujeto a lo especificado en la extensi\u00f3n) el comportamiento especificado por el caso de uso base\u00a0\u00a0<\/span>“Cuenta de inicio de sesi\u00f3n”<\/span><\/strong>\u00a0.<\/span><\/li>\n
    • Representar con una flecha dirigida que tiene una l\u00ednea de puntos.\u00a0La punta de la punta de flecha apunta al caso de uso base y el caso de uso secundario est\u00e1 conectado en la base de la flecha.<\/span><\/li>\n
    • El estereotipo \u201c<<extiende>>\u201d se identifica como una relaci\u00f3n extendida<\/span><\/li>\n<\/ul>\n

      Ampliar relaci\u00f3n<\/span><\/span><\/h4>\n

      Las relaciones extendidas son importantes porque muestran funcionalidad opcional o comportamiento del sistema.\u00a0La relaci\u00f3n <<extender>> se utiliza para incluir el comportamiento opcional de un caso de uso extendido en un caso de uso extendido.\u00a0En el ejemplo anterior, hay un conector de extensi\u00f3n con un punto de extensi\u00f3n “Contrase\u00f1a no v\u00e1lida”.<\/span><\/p>\n

      Caso de uso abstracto y generalizado<\/span><\/span><\/h3>\n

      El caso de uso general es abstracto.\u00a0No se puede instanciar, ya que contiene informaci\u00f3n incompleta.\u00a0El t\u00edtulo de un caso de uso abstracto se muestra en cursiva.<\/span><\/p>\n

      \"Notaci\u00f3n<\/p>\n

      Ejemplo de diagrama de caso de uso<\/span><\/span><\/h2>\n

      Este ejemplo de un diagrama de caso de uso muestra un modelo de varios casos de uso comercial (objetivos) que representan la interacci\u00f3n entre un restaurante (sistema comercial) y sus partes interesadas clave (participantes comerciales y trabajadores comerciales).\u00a0Habiendo identificado los casos de uso b\u00e1sicos en la primera ronda de cortes, tal vez podamos construir m\u00e1s estos casos de uso con casos de uso “extender” e “incluir” en la segunda ronda de revisiones.<\/span><\/p>\n

      \"Diagrama<\/p>\n","protected":false},"excerpt":{"rendered":"

      Uzkazrilatoj modeligas la dependecojn inter uzkazoj en la interagadmodelo de la sistemo. Kvankam, sendependaj uzkazoj povas adekvate reprezenti pli simplajn sistemojn. Tamen, por reprezenti kompleksajn a\u016d grandajn sistemojn, ni eble bezonos konstrui kompleksajn uzkazojn helpe de dependecoj inter uzkazoj. Establi rilatojn inter uzkazoj permesas reuzon de tiuj uzkazoj, kiuj devas esti difinitaj ree kaj denove, kio reduktas programistajn penadojn.<\/p>\n","protected":false},"author":1,"featured_media":3608,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[36],"tags":[],"class_list":["post-3481","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uml","loop-entry","clr"],"yoast_head":"\nCasos De Uso "Incluir" Y "Extender" - Visual Paradigm Blog Espa\u00f1ol<\/title>\n<meta name=\"description\" content=\"Use case relationships model the dependencies between use cases in the interaction model of the system. Although, independent use cases can adequately represent simpler systems. However, in order to represent complex or large systems, we may need to construct complex use cases with the help of dependencies between use cases. Establishing relationships between use cases allows reuse of those use cases that need to be defined over and over again, which reduces developer effort.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Casos De Uso "Incluir" Y "Extender" - Visual Paradigm Blog Espa\u00f1ol\" \/>\n<meta property=\"og:description\" content=\"Use case relationships model the dependencies between use cases in the interaction model of the system. Although, independent use cases can adequately represent simpler systems. However, in order to represent complex or large systems, we may need to construct complex use cases with the help of dependencies between use cases. Establishing relationships between use cases allows reuse of those use cases that need to be defined over and over again, which reduces developer effort.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Blog Espa\u00f1ol\" \/>\n<meta property=\"article:published_time\" content=\"2022-02-09T09:13:56+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-11-25T09:26:20+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png\" \/>\n<meta name=\"author\" content=\"Admin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png\" \/>\n<meta name=\"twitter:label1\" content=\"Escrito por\" \/>\n\t<meta name=\"twitter:data1\" content=\"Admin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tiempo de lectura\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/\",\"url\":\"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/\",\"name\":\"Casos De Uso \\\"Incluir\\\" Y \\\"Extender\\\" - Visual Paradigm Blog Espa\u00f1ol\",\"isPartOf\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/es\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png\",\"datePublished\":\"2022-02-09T09:13:56+00:00\",\"dateModified\":\"2022-11-25T09:26:20+00:00\",\"author\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/es\/#\/schema\/person\/a649c442f11a53040710ddec750926c6\"},\"description\":\"Use case relationships model the dependencies between use cases in the interaction model of the system. Although, independent use cases can adequately represent simpler systems. However, in order to represent complex or large systems, we may need to construct complex use cases with the help of dependencies between use cases. Establishing relationships between use cases allows reuse of those use cases that need to be defined over and over again, which reduces developer effort.\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/#primaryimage\",\"url\":\"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png\",\"contentUrl\":\"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png\",\"width\":\"733\",\"height\":\"656\",\"caption\":\"Casos De Uso\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.visual-paradigm.com\/es\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Casos De Uso “Incluir” Y “Extender”\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/es\/#website\",\"url\":\"https:\/\/blog.visual-paradigm.com\/es\/\",\"name\":\"Visual Paradigm Blog Espa\u00f1ol\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.visual-paradigm.com\/es\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/es\/#\/schema\/person\/a649c442f11a53040710ddec750926c6\",\"name\":\"Admin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/es\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/6b756c36f5e9132f6067fb4d22bef2e3?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/6b756c36f5e9132f6067fb4d22bef2e3?s=96&d=mm&r=g\",\"caption\":\"Admin\"},\"url\":\"https:\/\/blog.visual-paradigm.com\/es\/author\/vpadminuser\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Casos De Uso \"Incluir\" Y \"Extender\" - Visual Paradigm Blog Espa\u00f1ol","description":"Use case relationships model the dependencies between use cases in the interaction model of the system. Although, independent use cases can adequately represent simpler systems. However, in order to represent complex or large systems, we may need to construct complex use cases with the help of dependencies between use cases. Establishing relationships between use cases allows reuse of those use cases that need to be defined over and over again, which reduces developer effort.","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:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/","og_locale":"es_ES","og_type":"article","og_title":"Casos De Uso \"Incluir\" Y \"Extender\" - Visual Paradigm Blog Espa\u00f1ol","og_description":"Use case relationships model the dependencies between use cases in the interaction model of the system. Although, independent use cases can adequately represent simpler systems. However, in order to represent complex or large systems, we may need to construct complex use cases with the help of dependencies between use cases. Establishing relationships between use cases allows reuse of those use cases that need to be defined over and over again, which reduces developer effort.","og_url":"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/","og_site_name":"Visual Paradigm Blog Espa\u00f1ol","article_published_time":"2022-02-09T09:13:56+00:00","article_modified_time":"2022-11-25T09:26:20+00:00","og_image":[{"url":"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png","type":"","width":"","height":""}],"author":"Admin","twitter_card":"summary_large_image","twitter_image":"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png","twitter_misc":{"Escrito por":"Admin","Tiempo de lectura":"5 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/","url":"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/","name":"Casos De Uso \"Incluir\" Y \"Extender\" - Visual Paradigm Blog Espa\u00f1ol","isPartOf":{"@id":"https:\/\/blog.visual-paradigm.com\/es\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/#primaryimage"},"image":{"@id":"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/#primaryimage"},"thumbnailUrl":"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png","datePublished":"2022-02-09T09:13:56+00:00","dateModified":"2022-11-25T09:26:20+00:00","author":{"@id":"https:\/\/blog.visual-paradigm.com\/es\/#\/schema\/person\/a649c442f11a53040710ddec750926c6"},"description":"Use case relationships model the dependencies between use cases in the interaction model of the system. Although, independent use cases can adequately represent simpler systems. However, in order to represent complex or large systems, we may need to construct complex use cases with the help of dependencies between use cases. Establishing relationships between use cases allows reuse of those use cases that need to be defined over and over again, which reduces developer effort.","breadcrumb":{"@id":"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/"]}]},{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/#primaryimage","url":"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png","contentUrl":"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png","width":"733","height":"656","caption":"Casos De Uso"},{"@type":"BreadcrumbList","@id":"https:\/\/blog.visual-paradigm.com\/es\/include-and-extend-use-cases\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.visual-paradigm.com\/es\/"},{"@type":"ListItem","position":2,"name":"Casos De Uso “Incluir” Y “Extender”"}]},{"@type":"WebSite","@id":"https:\/\/blog.visual-paradigm.com\/es\/#website","url":"https:\/\/blog.visual-paradigm.com\/es\/","name":"Visual Paradigm Blog Espa\u00f1ol","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.visual-paradigm.com\/es\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es"},{"@type":"Person","@id":"https:\/\/blog.visual-paradigm.com\/es\/#\/schema\/person\/a649c442f11a53040710ddec750926c6","name":"Admin","image":{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/blog.visual-paradigm.com\/es\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/6b756c36f5e9132f6067fb4d22bef2e3?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/6b756c36f5e9132f6067fb4d22bef2e3?s=96&d=mm&r=g","caption":"Admin"},"url":"https:\/\/blog.visual-paradigm.com\/es\/author\/vpadminuser\/"}]}},"modified_by":"vpmiku","_links":{"self":[{"href":"https:\/\/blog.visual-paradigm.com\/es\/wp-json\/wp\/v2\/posts\/3481","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.visual-paradigm.com\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.visual-paradigm.com\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/es\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/es\/wp-json\/wp\/v2\/comments?post=3481"}],"version-history":[{"count":6,"href":"https:\/\/blog.visual-paradigm.com\/es\/wp-json\/wp\/v2\/posts\/3481\/revisions"}],"predecessor-version":[{"id":8480,"href":"https:\/\/blog.visual-paradigm.com\/es\/wp-json\/wp\/v2\/posts\/3481\/revisions\/8480"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media\/3608"}],"wp:attachment":[{"href":"https:\/\/blog.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media?parent=3481"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/es\/wp-json\/wp\/v2\/categories?post=3481"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/es\/wp-json\/wp\/v2\/tags?post=3481"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}