{"id":3481,"date":"2022-02-09T17:13:56","date_gmt":"2022-02-09T09:13:56","guid":{"rendered":"https:\/\/blog.visual-paradigm.com\/fr\/?p=3481"},"modified":"2022-11-25T17:26:44","modified_gmt":"2022-11-25T09:26:44","slug":"include-and-extend-use-cases","status":"publish","type":"post","link":"https:\/\/blog.visual-paradigm.com\/fr\/include-and-extend-use-cases\/","title":{"rendered":"Cas D&#8217;utilisation &#8220;Inclure&#8221; Et &#8220;\u00c9tendre&#8221;"},"content":{"rendered":"<p><span>Un\u00a0<\/span><a href=\"http:\/\/the%20document%20management%20system%20%28dms%29%20use%20case%20diagram%20below%20shows%20the%20actors%20and%20use%20cases%20of%20the%20system.%20in%20particular%2C%20there%20are%20containment%20and%20extension%20relationships%20between%20use%20cases.\/\"><span>cas d&#8217;utilisation<\/span><\/a><span>\u00a0d\u00e9crit comment un utilisateur utilise un syst\u00e8me pour atteindre un objectif particulier.\u00a0Un diagramme de cas d&#8217;utilisation comprend le syst\u00e8me, les cas d&#8217;utilisation et les acteurs associ\u00e9s et les relie les uns aux autres pour visualiser\u00a0: qu&#8217;est-ce qui est d\u00e9crit\u00a0?\u00a0(\u00a0<\/span><strong><span>syst\u00e8me<\/span><\/strong><span>\u00a0), qui utilise le syst\u00e8me\u00a0?\u00a0(\u00a0<\/span><strong><span>acteurs<\/span><\/strong><span>\u00a0) et qu&#8217;est-ce que les acteurs veulent r\u00e9aliser\u00a0?\u00a0(\u00a0<\/span><strong><span>cas d&#8217;utilisation<\/span><\/strong><span>\u00a0), ainsi, les cas d&#8217;utilisation aident \u00e0 garantir que le bon syst\u00e8me est d\u00e9velopp\u00e9 en capturant les exigences du point de vue de l&#8217;utilisateur.<\/span><\/p>\n<h3><img decoding=\"async\" id=\"thepasted-1\" class=\"center-img template-thumbnail\" src=\"https:\/\/blog.visual-paradigm.com\/wp-content\/uploads\/2022\/10\/include-and-extend-use-case-diagram.png\" alt=\"Mod\u00e8le de diagramme de cas d'utilisation\u00a0: inclure et \u00e9tendre le diagramme de cas d'utilisation (cr\u00e9\u00e9 par le cr\u00e9ateur de diagrammes de cas d'utilisation de Visual Paradigm Online)\" \/><\/h3>\n<h2 id=\"structuring-use-cases\"><span id=\"Structuring_Use_Cases\"><span>Structuration des cas d&#8217;utilisation<\/span><\/span><\/h2>\n<p><span>Les relations de cas d&#8217;utilisation mod\u00e9lisent les d\u00e9pendances entre les cas d&#8217;utilisation dans le mod\u00e8le d&#8217;interaction du syst\u00e8me.\u00a0Cependant, des cas d&#8217;utilisation ind\u00e9pendants peuvent repr\u00e9senter de mani\u00e8re ad\u00e9quate des syst\u00e8mes plus simples.\u00a0Cependant, afin de repr\u00e9senter des syst\u00e8mes complexes ou de grande taille, nous pouvons avoir besoin de construire des cas d&#8217;utilisation complexes \u00e0 l&#8217;aide de d\u00e9pendances entre les cas d&#8217;utilisation.\u00a0L&#8217;\u00e9tablissement de relations entre les cas d&#8217;utilisation permet de r\u00e9utiliser les cas d&#8217;utilisation qui doivent \u00eatre d\u00e9finis encore et encore, ce qui r\u00e9duit les efforts des d\u00e9veloppeurs.<\/span><\/p>\n<p><span>UML d\u00e9finit trois st\u00e9r\u00e9otypes pour structurer les associations de cas d&#8217;utilisation.<\/span><\/p>\n<h3><span id=\"What_is_a_Include_Use_Case\"><span>Qu&#8217;est-ce qu&#8217;un cas d&#8217;utilisation &lt;&lt;Inclure&gt;&gt;\u00a0?<\/span><\/span><\/h3>\n<p><span>Un cas d&#8217;utilisation \u00e9tendu est, en fait, un cours alternatif du cas d&#8217;utilisation de base.\u00a0Le cas d&#8217;utilisation &lt;&lt;extend&gt;&gt; accomplit cela en ins\u00e9rant conceptuellement des s\u00e9quences d&#8217;action suppl\u00e9mentaires dans la s\u00e9quence de cas d&#8217;utilisation de base.<\/span><\/p>\n<p><span>Le moment d&#8217;utiliser la relation &lt;&lt;include&gt;&gt; est une fois que vous avez termin\u00e9 la premi\u00e8re description de tous vos principaux cas d&#8217;utilisation.\u00a0Vous pouvez maintenant consulter les cas d&#8217;utilisation et identifier les s\u00e9quences courantes d&#8217;interaction utilisateur-syst\u00e8me.<\/span><\/p>\n<ul>\n<li><span>Lorsqu&#8217;un cas d&#8217;utilisation est d\u00e9crit comme utilisant la fonctionnalit\u00e9 d&#8217;un autre cas d&#8217;utilisation, la relation entre les cas d&#8217;utilisation est nomm\u00e9e relation d&#8217;inclusion ou d&#8217;utilisation.<\/span><\/li>\n<li><span>Un cas d&#8217;utilisation inclut la fonctionnalit\u00e9 d\u00e9crite dans un autre cas d&#8217;utilisation dans le cadre de son flux de processus m\u00e9tier.<\/span><\/li>\n<li><span>Une relation d&#8217;utilisation entre le cas d&#8217;utilisation de base et le cas d&#8217;utilisation enfant indique qu&#8217;une instance du cas d&#8217;utilisation de base inclura le comportement sp\u00e9cifi\u00e9 dans le cas d&#8217;utilisation enfant.<\/span><\/li>\n<li><span>Une relation d&#8217;inclusion est illustr\u00e9e par une fl\u00e8che dirig\u00e9e ayant une ligne pointill\u00e9e.\u00a0La pointe de la fl\u00e8che pointe vers le cas d&#8217;utilisation enfant et le cas d&#8217;utilisation parent connect\u00e9s \u00e0 la base de la fl\u00e8che.<\/span><\/li>\n<li><span>Le st\u00e9r\u00e9otype &#8220;&lt;&lt;include&gt;&gt;&#8221; identifie la relation comme une relation d&#8217;inclusion.<\/span><\/li>\n<\/ul>\n<h3><span id=\"Use_Case_Example_-_Include_Relationship\"><span>Exemple de cas d&#8217;utilisation &#8211; Inclure la relation<\/span><\/span><\/h3>\n<p><span>La relation include ajoute des fonctionnalit\u00e9s suppl\u00e9mentaires non sp\u00e9cifi\u00e9es dans le cas d&#8217;utilisation de base.\u00a0La relation &lt;&lt;Include&gt;&gt; est utilis\u00e9e pour inclure le comportement commun d&#8217;un cas d&#8217;utilisation inclus dans un cas d&#8217;utilisation de base afin de prendre en charge la r\u00e9utilisation du comportement commun.<\/span><\/p>\n<p><img decoding=\"async\" id=\"thepasted-2\" src=\"https:\/\/blog.visual-paradigm.com\/wp-content\/uploads\/2022\/10\/08-use-case-diagram-notation-include.png\" alt=\"Notation de diagramme de cas d'utilisation - Inclure\" \/><\/p>\n<h3><span id=\"What_is_a_Extend_Use_Case\"><strong><span>Qu&#8217;est-ce qu&#8217;un cas d&#8217;utilisation &lt;&lt;Extend&gt;&gt;\u00a0?<\/span><\/strong><\/span><\/h3>\n<p><img decoding=\"async\" id=\"thepasted-4\" src=\"https:\/\/blog.visual-paradigm.com\/wp-content\/uploads\/2022\/10\/07-use-case-diagram-notation-extend.png\" alt=\"Notation de diagramme de cas d'utilisation - \u00c9tendre\" \/><\/p>\n<ul>\n<li><span>Indique qu&#8217;un cas d&#8217;\u00a0 utilisation\u00a0<\/span><strong><span>\u00ab Mot de passe invalide \u00bb<\/span><\/strong><span>\u00a0\u00a0peut inclure (sous r\u00e9serve de ce qui est sp\u00e9cifi\u00e9 dans l&#8217;extension) le comportement sp\u00e9cifi\u00e9 par le cas d&#8217;utilisation de base\u00a0\u00a0<\/span><strong><span>\u00ab Compte de connexion \u00bb<\/span><\/strong><span>\u00a0.<\/span><\/li>\n<li><span>Repr\u00e9sentez avec une fl\u00e8che dirig\u00e9e ayant une ligne pointill\u00e9e.\u00a0La pointe de la fl\u00e8che pointe vers le cas d&#8217;utilisation de base et le cas d&#8217;utilisation enfant est connect\u00e9 \u00e0 la base de la fl\u00e8che.<\/span><\/li>\n<li><span>Le st\u00e9r\u00e9otype &#8220;&lt;&lt;extends&gt;&gt;&#8221; s&#8217;identifie comme une relation d&#8217;extension<\/span><\/li>\n<\/ul>\n<h4><span id=\"Extend_Relationship\"><span>\u00c9tendre la relation<\/span><\/span><\/h4>\n<p><span>Les relations d&#8217;extension sont importantes car elles affichent des fonctionnalit\u00e9s facultatives ou le comportement du syst\u00e8me.\u00a0La relation &lt;&lt;extend&gt;&gt; est utilis\u00e9e pour inclure le comportement facultatif d&#8217;un cas d&#8217;utilisation \u00e9tendu dans un cas d&#8217;utilisation \u00e9tendu.\u00a0Dans l&#8217;exemple ci-dessus, il existe un connecteur d&#8217;extension avec un point d&#8217;extension &#8220;Mot de passe invalide&#8221;.<\/span><\/p>\n<h3><span id=\"Abstract_and_generalized_Use_Case\"><span>Cas d&#8217;utilisation abstrait et g\u00e9n\u00e9ralis\u00e9<\/span><\/span><\/h3>\n<p><span>Le cas d&#8217;utilisation g\u00e9n\u00e9ral est abstrait.\u00a0Il ne peut pas \u00eatre instanci\u00e9, car il contient des informations incompl\u00e8tes.\u00a0Le titre d&#8217;un cas d&#8217;utilisation abstrait est affich\u00e9 en italique.<\/span><\/p>\n<p><img decoding=\"async\" id=\"thepasted-5\" src=\"https:\/\/blog.visual-paradigm.com\/wp-content\/uploads\/2022\/10\/08-use-case-diagram-notation-generalization.png\" alt=\"Notation des diagrammes de cas d'utilisation - G\u00e9n\u00e9ralisation\" \/><\/p>\n<h2><span id=\"Use_Case_Diagram_Example\"><span>Exemple de diagramme de cas d&#8217;utilisation<\/span><\/span><\/h2>\n<p><span>Cet exemple de diagramme de cas d&#8217;utilisation repr\u00e9sente un mod\u00e8le de plusieurs cas d&#8217;utilisation m\u00e9tier (objectifs) qui repr\u00e9sentent l&#8217;interaction entre un restaurant (syst\u00e8me m\u00e9tier) et ses principales parties prenantes (participants m\u00e9tier et travailleurs m\u00e9tier).\u00a0Apr\u00e8s avoir identifi\u00e9 les cas d&#8217;utilisation de base lors de la premi\u00e8re s\u00e9rie de r\u00e9ductions, nous pouvons peut-\u00eatre d\u00e9velopper davantage ces cas d&#8217;utilisation avec des cas d&#8217;utilisation \u00ab\u00e9tendre\u00bb et \u00abinclure\u00bb lors de la deuxi\u00e8me s\u00e9rie de r\u00e9visions.<\/span><\/p>\n<p><img decoding=\"async\" id=\"thepasted-6\" class=\"n3VNCb KAlRDb\" src=\"https:\/\/blog.visual-paradigm.com\/wp-content\/uploads\/2022\/10\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png\" alt=\"Diagramme de cas d'utilisation, exemple de diagrammes UML\u00a0: cas d'utilisation &quot;inclure&quot; et &quot;\u00e9tendre&quot; - Visual Paradigm Community Circle\" \/><\/p>\n<div class=\"addtoany_share_save_container addtoany_content addtoany_content_bottom\">\n<div class=\"a2a_kit a2a_kit_size_32 addtoany_list\" data-a2a-url=\"https:\/\/blog.visual-paradigm.com\/include-and-extend-use-cases\/\" data-a2a-title=\"\u201cInclude\u201d and \u201cExtend\u201d Use Cases\"><a class=\"a2a_button_facebook\" title=\"Facebook\" href=\"https:\/\/blog.visual-paradigm.com\/#facebook\" target=\"_blank\" rel=\"nofollow noopener\"><span class=\"a2a_label\"><span>Facebook<\/span><\/span><\/a><a class=\"a2a_button_pinterest\" title=\"Pinterest\" href=\"https:\/\/blog.visual-paradigm.com\/#pinterest\" target=\"_blank\" rel=\"nofollow noopener\"><span class=\"a2a_label\"><span>Pinterest<\/span><\/span><\/a><a class=\"a2a_button_twitter\" title=\"Twitter\" href=\"https:\/\/blog.visual-paradigm.com\/#twitter\" target=\"_blank\" rel=\"nofollow noopener\"><span class=\"a2a_label\"><span>Twitter<\/span><\/span><\/a><a class=\"a2a_button_linkedin\" title=\"LinkedIn\" href=\"https:\/\/blog.visual-paradigm.com\/#linkedin\" target=\"_blank\" rel=\"nofollow noopener\"><span class=\"a2a_label\"><span>LinkedIn<\/span><\/span><\/a><a class=\"a2a_button_whatsapp\" title=\"Whatsapp\" href=\"https:\/\/blog.visual-paradigm.com\/#whatsapp\" target=\"_blank\" rel=\"nofollow noopener\"><span class=\"a2a_label\"><span>Whatsapp<\/span><\/span><\/a><a class=\"a2a_button_email\" title=\"E-mail\" href=\"https:\/\/blog.visual-paradigm.com\/#email\" target=\"_blank\" rel=\"nofollow noopener\"><span class=\"a2a_label\"><span>E-mail<\/span><\/span><\/a><a class=\"a2a_dd addtoany_share_save addtoany_share\" href=\"https:\/\/www.addtoany.com\/share#url=https%3A%2F%2Fblog.visual-paradigm.com%2Finclude-and-extend-use-cases%2F&amp;title=%E2%80%9CInclude%E2%80%9D%20and%20%E2%80%9CExtend%E2%80%9D%20Use%20Cases\"><span class=\"a2a_label a2a_localize\" data-a2a-localize=\"inner,Share\"><span>Partager<\/span><\/span><\/a><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Les relations entre les cas d&#8217;utilisation mod\u00e9lisent les d\u00e9pendances entre les cas d&#8217;utilisation dans le mod\u00e8le d&#8217;interaction du syst\u00e8me. Bien que les cas d&#8217;utilisation ind\u00e9pendants puissent repr\u00e9senter ad\u00e9quatement des syst\u00e8mes plus simples. Cependant, afin de repr\u00e9senter des syst\u00e8mes complexes ou de grande taille, nous pouvons avoir besoin de construire des cas d&#8217;utilisation complexes \u00e0 l&#8217;aide de d\u00e9pendances entre les cas d&#8217;utilisation. L&#8217;\u00e9tablissement de relations entre les cas d&#8217;utilisation permet de r\u00e9utiliser les cas d&#8217;utilisation qui doivent \u00eatre d\u00e9finis encore et encore, ce qui r\u00e9duit l&#8217;effort du d\u00e9veloppeur.<\/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":"<!-- This site is optimized with the Yoast SEO plugin v24.3 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Cas D&#039;utilisation &quot;Inclure&quot; Et &quot;\u00c9tendre&quot; - Visual Paradigm Blog Fran\u00e7ais<\/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\/fr\/include-and-extend-use-cases\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Cas D&#039;utilisation &quot;Inclure&quot; Et &quot;\u00c9tendre&quot; - Visual Paradigm Blog Fran\u00e7ais\" \/>\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\/fr\/include-and-extend-use-cases\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Blog Fran\u00e7ais\" \/>\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:44+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=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"Admin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/fr\/include-and-extend-use-cases\/\",\"url\":\"https:\/\/blog.visual-paradigm.com\/fr\/include-and-extend-use-cases\/\",\"name\":\"Cas D'utilisation \\\"Inclure\\\" Et \\\"\u00c9tendre\\\" - Visual Paradigm Blog Fran\u00e7ais\",\"isPartOf\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/fr\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/fr\/include-and-extend-use-cases\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/fr\/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:44+00:00\",\"author\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/fr\/#\/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\/fr\/include-and-extend-use-cases\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.visual-paradigm.com\/fr\/include-and-extend-use-cases\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/fr\/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\":\"Cas D'utilisation\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/fr\/include-and-extend-use-cases\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.visual-paradigm.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Cas D&#8217;utilisation &#8220;Inclure&#8221; Et &#8220;\u00c9tendre&#8221;\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/fr\/#website\",\"url\":\"https:\/\/blog.visual-paradigm.com\/fr\/\",\"name\":\"Visual Paradigm Blog Fran\u00e7ais\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.visual-paradigm.com\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/fr\/#\/schema\/person\/a649c442f11a53040710ddec750926c6\",\"name\":\"Admin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/fr\/#\/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\/fr\/author\/vpadminuser\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Cas D'utilisation \"Inclure\" Et \"\u00c9tendre\" - Visual Paradigm Blog Fran\u00e7ais","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\/fr\/include-and-extend-use-cases\/","og_locale":"fr_FR","og_type":"article","og_title":"Cas D'utilisation \"Inclure\" Et \"\u00c9tendre\" - Visual Paradigm Blog Fran\u00e7ais","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\/fr\/include-and-extend-use-cases\/","og_site_name":"Visual Paradigm Blog Fran\u00e7ais","article_published_time":"2022-02-09T09:13:56+00:00","article_modified_time":"2022-11-25T09:26:44+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":{"\u00c9crit par":"Admin","Dur\u00e9e de lecture estim\u00e9e":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/blog.visual-paradigm.com\/fr\/include-and-extend-use-cases\/","url":"https:\/\/blog.visual-paradigm.com\/fr\/include-and-extend-use-cases\/","name":"Cas D'utilisation \"Inclure\" Et \"\u00c9tendre\" - Visual Paradigm Blog Fran\u00e7ais","isPartOf":{"@id":"https:\/\/blog.visual-paradigm.com\/fr\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blog.visual-paradigm.com\/fr\/include-and-extend-use-cases\/#primaryimage"},"image":{"@id":"https:\/\/blog.visual-paradigm.com\/fr\/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:44+00:00","author":{"@id":"https:\/\/blog.visual-paradigm.com\/fr\/#\/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\/fr\/include-and-extend-use-cases\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.visual-paradigm.com\/fr\/include-and-extend-use-cases\/"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/blog.visual-paradigm.com\/fr\/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":"Cas D'utilisation"},{"@type":"BreadcrumbList","@id":"https:\/\/blog.visual-paradigm.com\/fr\/include-and-extend-use-cases\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.visual-paradigm.com\/fr\/"},{"@type":"ListItem","position":2,"name":"Cas D&#8217;utilisation &#8220;Inclure&#8221; Et &#8220;\u00c9tendre&#8221;"}]},{"@type":"WebSite","@id":"https:\/\/blog.visual-paradigm.com\/fr\/#website","url":"https:\/\/blog.visual-paradigm.com\/fr\/","name":"Visual Paradigm Blog Fran\u00e7ais","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.visual-paradigm.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Person","@id":"https:\/\/blog.visual-paradigm.com\/fr\/#\/schema\/person\/a649c442f11a53040710ddec750926c6","name":"Admin","image":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/blog.visual-paradigm.com\/fr\/#\/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\/fr\/author\/vpadminuser\/"}]}},"modified_by":"vpmiku","_links":{"self":[{"href":"https:\/\/blog.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/posts\/3481","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/comments?post=3481"}],"version-history":[{"count":7,"href":"https:\/\/blog.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/posts\/3481\/revisions"}],"predecessor-version":[{"id":8458,"href":"https:\/\/blog.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/posts\/3481\/revisions\/8458"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media\/3608"}],"wp:attachment":[{"href":"https:\/\/blog.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=3481"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/categories?post=3481"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/tags?post=3481"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}