{"id":3481,"date":"2022-02-09T17:13:56","date_gmt":"2022-02-09T09:13:56","guid":{"rendered":"https:\/\/blog.visual-paradigm.com\/id\/?p=3481"},"modified":"2022-11-24T18:03:27","modified_gmt":"2022-11-24T10:03:27","slug":"include-and-extend-use-cases","status":"publish","type":"post","link":"https:\/\/blog.visual-paradigm.com\/id\/include-and-extend-use-cases\/","title":{"rendered":"Kasus Penggunaan “Sertakan” Dan “Perpanjang”"},"content":{"rendered":"

Use\u00a0case<\/a>\u00a0menggambarkan bagaimana pengguna menggunakan sistem untuk mencapai tujuan tertentu.\u00a0Diagram use case terdiri dari sistem, use case terkait dan aktor dan menghubungkannya satu sama lain untuk memvisualisasikan: apa yang sedang dijelaskan?\u00a0(\u00a0sistem<\/strong>\u00a0), siapa yang menggunakan sistem?\u00a0(\u00a0aktor<\/strong>\u00a0) dan apa yang ingin dicapai para aktor?\u00a0(\u00a0use case<\/strong>\u00a0), dengan demikian, use case membantu memastikan bahwa sistem yang benar dikembangkan dengan menangkap persyaratan dari sudut pandang pengguna.<\/p>\n

\"\u7528\u4f8b\u5716\u6a21\u677f\uff1a\u5305\u542b\u548c\u64f4\u5c55\u7528\u4f8b\u5716\uff08\u7531<\/h3>\n

Menyusun Kasus Penggunaan<\/span><\/h2>\n

Use case model hubungan ketergantungan antara use case dalam model interaksi sistem.\u00a0Meskipun, kasus penggunaan independen dapat secara memadai mewakili sistem yang lebih sederhana.\u00a0Namun, untuk mewakili sistem yang kompleks atau besar, kita mungkin perlu membangun kasus penggunaan yang kompleks dengan bantuan ketergantungan antara kasus penggunaan.\u00a0Membangun hubungan antara kasus penggunaan memungkinkan penggunaan kembali kasus penggunaan yang perlu didefinisikan berulang kali, yang mengurangi upaya pengembang.<\/p>\n

UML mendefinisikan tiga stereotip untuk penataan asosiasi kasus penggunaan.<\/p>\n

Apa itu Kasus Penggunaan <<Sertakan>>?<\/span><\/h3>\n

Kasus penggunaan yang diperluas, secara efektif, merupakan jalur alternatif dari kasus penggunaan dasar.\u00a0Use case <<extend>> menyelesaikan ini dengan secara konseptual memasukkan urutan tindakan tambahan ke dalam urutan use-case dasar.<\/p>\n

Waktu untuk menggunakan hubungan <<include>> adalah setelah Anda menyelesaikan deskripsi potongan pertama dari semua Kasus Penggunaan utama Anda.\u00a0Anda sekarang dapat melihat Kasus Penggunaan dan mengidentifikasi urutan umum interaksi sistem pengguna.<\/p>\n

    \n
  • Ketika sebuah use case digambarkan menggunakan fungsionalitas dari use case lain, hubungan antara use case disebut sebagai hubungan include atau using.<\/li>\n
  • Sebuah use case mencakup fungsionalitas yang dijelaskan dalam use case lain sebagai bagian dari alur proses bisnisnya.<\/li>\n
  • Hubungan penggunaan dari kasus penggunaan dasar ke kasus penggunaan anak menunjukkan bahwa turunan dari kasus penggunaan dasar akan menyertakan perilaku seperti yang ditentukan dalam kasus penggunaan anak.<\/li>\n
  • Hubungan include digambarkan dengan panah berarah yang memiliki garis putus-putus.\u00a0Ujung panah menunjuk ke kasus penggunaan anak dan kasus penggunaan induk terhubung di dasar panah.<\/li>\n
  • Stereotip \u201c<<include>>\u201d mengidentifikasi hubungan sebagai hubungan include.<\/li>\n<\/ul>\n

    Contoh Kasus Penggunaan \u2013 Sertakan Hubungan<\/span><\/h3>\n

    Hubungan include menambahkan fungsionalitas tambahan yang tidak ditentukan dalam kasus penggunaan dasar.\u00a0Hubungan <<Sertakan>> digunakan untuk memasukkan perilaku umum dari kasus penggunaan yang disertakan ke dalam kasus penggunaan dasar untuk mendukung penggunaan kembali perilaku umum.<\/p>\n

    \"\u7528\u4f8b\u5716\u8868\u793a\u6cd5<\/p>\n

    Apa itu Use Case <<Extend>>?<\/strong><\/span><\/h4>\n
      \n
    • Menunjukkan bahwa\u00a0 kasus penggunaan\u00a0“Kata Sandi Tidak Valid”<\/strong>\u00a0\u00a0dapat mencakup (tunduk pada yang ditentukan dalam ekstensi) perilaku yang ditentukan oleh kasus penggunaan dasar\u00a0\u00a0“Akun Masuk”<\/strong>\u00a0.<\/li>\n
    • Gambarkan dengan panah terarah yang memiliki garis putus-putus.\u00a0Ujung panah menunjuk ke kasus penggunaan dasar dan kasus penggunaan anak terhubung di dasar panah.<\/li>\n
    • Stereotip \u201c<<extends>>\u201d diidentifikasi sebagai hubungan yang diperpanjang<\/li>\n<\/ul>\n

      Contoh Kasus Penggunaan \u2013 Perpanjang Hubungan<\/span><\/h3>\n

      Perluasan hubungan penting karena menunjukkan fungsionalitas opsional atau perilaku sistem.\u00a0Hubungan <<extend>> digunakan untuk menyertakan perilaku opsional dari kasus penggunaan yang diperluas dalam kasus penggunaan yang diperluas.\u00a0Perhatikan contoh use case diagram di bawah ini.\u00a0Ini menunjukkan konektor perpanjangan dan titik ekstensi “Cari”.<\/p>\n

       <\/p>\n

      \"\u7528\u4f8b\u5716\u8868\u793a\u6cd5<\/p>\n

      Kasus Penggunaan abstrak dan umum<\/span><\/h3>\n

      Kasus penggunaan umum adalah abstrak.\u00a0Itu tidak dapat dipakai, karena berisi informasi yang tidak lengkap.\u00a0Judul kasus penggunaan abstrak ditampilkan dalam huruf miring.<\/p>\n

      \"\u7528\u4f8b\u5716\u7b26\u865f<\/p>\n

      Contoh Diagram Kasus Penggunaan<\/span><\/h2>\n

      Contoh diagram kasus penggunaan ini menggambarkan model beberapa kasus penggunaan bisnis (tujuan) yang mewakili interaksi antara restoran (sistem bisnis) dan pemangku kepentingan utamanya (peserta bisnis dan pekerja bisnis).\u00a0Setelah mengidentifikasi kasus penggunaan dasar pada pemotongan putaran pertama, mungkin kita dapat membangun lebih lanjut kasus penggunaan ini dengan kasus penggunaan “memperluas” dan “menyertakan” di putaran kedua revisi.<\/p>\n

      \"\u7528\u4f8b\u5716\u7b26\u865f<\/p>\n

      Contoh Kasus Penggunaan \u2013 Sistem Dokumentasi<\/span><\/h3>\n

      Diagram kasus penggunaan Sistem Manajemen Dokumen (DMS) di bawah ini menunjukkan aktor dan kasus penggunaan sistem.\u00a0Secara khusus, ada hubungan <<include>> dan <<extend>> antara use case.<\/p>\n

       <\/p>\n

      \"\u7528\u4f8b\u5716\u3001UML<\/p>\n","protected":false},"excerpt":{"rendered":"

      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.<\/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":"\nKasus Penggunaan "Sertakan" Dan "Perpanjang" - Visual Paradigm Blog<\/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\/id\/include-and-extend-use-cases\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Kasus Penggunaan "Sertakan" Dan "Perpanjang" - Visual Paradigm Blog\" \/>\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\/id\/include-and-extend-use-cases\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Blog\" \/>\n<meta property=\"article:published_time\" content=\"2022-02-09T09:13:56+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-11-24T10:03:27+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=\"Ditulis oleh\" \/>\n\t<meta name=\"twitter:data1\" content=\"Admin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Estimasi waktu membaca\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 menit\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/id\/include-and-extend-use-cases\/\",\"url\":\"https:\/\/blog.visual-paradigm.com\/id\/include-and-extend-use-cases\/\",\"name\":\"Kasus Penggunaan \\\"Sertakan\\\" Dan \\\"Perpanjang\\\" - Visual Paradigm Blog\",\"isPartOf\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/id\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/id\/include-and-extend-use-cases\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/id\/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-24T10:03:27+00:00\",\"author\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/id\/#\/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\/id\/include-and-extend-use-cases\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.visual-paradigm.com\/id\/include-and-extend-use-cases\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/id\/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\":\"Kasus Penggunaan\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/id\/include-and-extend-use-cases\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Kasus Penggunaan “Sertakan” Dan “Perpanjang”\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/id\/#website\",\"url\":\"https:\/\/blog.visual-paradigm.com\/id\/\",\"name\":\"Visual Paradigm Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.visual-paradigm.com\/id\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"id\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/id\/#\/schema\/person\/a649c442f11a53040710ddec750926c6\",\"name\":\"Admin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/id\/#\/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\/id\/author\/vpadminuser\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Kasus Penggunaan \"Sertakan\" Dan \"Perpanjang\" - Visual Paradigm Blog","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\/id\/include-and-extend-use-cases\/","og_locale":"id_ID","og_type":"article","og_title":"Kasus Penggunaan \"Sertakan\" Dan \"Perpanjang\" - Visual Paradigm Blog","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\/id\/include-and-extend-use-cases\/","og_site_name":"Visual Paradigm Blog","article_published_time":"2022-02-09T09:13:56+00:00","article_modified_time":"2022-11-24T10:03:27+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":{"Ditulis oleh":"Admin","Estimasi waktu membaca":"5 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/blog.visual-paradigm.com\/id\/include-and-extend-use-cases\/","url":"https:\/\/blog.visual-paradigm.com\/id\/include-and-extend-use-cases\/","name":"Kasus Penggunaan \"Sertakan\" Dan \"Perpanjang\" - Visual Paradigm Blog","isPartOf":{"@id":"https:\/\/blog.visual-paradigm.com\/id\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blog.visual-paradigm.com\/id\/include-and-extend-use-cases\/#primaryimage"},"image":{"@id":"https:\/\/blog.visual-paradigm.com\/id\/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-24T10:03:27+00:00","author":{"@id":"https:\/\/blog.visual-paradigm.com\/id\/#\/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\/id\/include-and-extend-use-cases\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.visual-paradigm.com\/id\/include-and-extend-use-cases\/"]}]},{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/blog.visual-paradigm.com\/id\/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":"Kasus Penggunaan"},{"@type":"BreadcrumbList","@id":"https:\/\/blog.visual-paradigm.com\/id\/include-and-extend-use-cases\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"Kasus Penggunaan “Sertakan” Dan “Perpanjang”"}]},{"@type":"WebSite","@id":"https:\/\/blog.visual-paradigm.com\/id\/#website","url":"https:\/\/blog.visual-paradigm.com\/id\/","name":"Visual Paradigm Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.visual-paradigm.com\/id\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"id"},{"@type":"Person","@id":"https:\/\/blog.visual-paradigm.com\/id\/#\/schema\/person\/a649c442f11a53040710ddec750926c6","name":"Admin","image":{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/blog.visual-paradigm.com\/id\/#\/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\/id\/author\/vpadminuser\/"}]}},"modified_by":"vpmiku","_links":{"self":[{"href":"https:\/\/blog.visual-paradigm.com\/id\/wp-json\/wp\/v2\/posts\/3481","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.visual-paradigm.com\/id\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.visual-paradigm.com\/id\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/id\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/id\/wp-json\/wp\/v2\/comments?post=3481"}],"version-history":[{"count":6,"href":"https:\/\/blog.visual-paradigm.com\/id\/wp-json\/wp\/v2\/posts\/3481\/revisions"}],"predecessor-version":[{"id":10459,"href":"https:\/\/blog.visual-paradigm.com\/id\/wp-json\/wp\/v2\/posts\/3481\/revisions\/10459"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media\/3608"}],"wp:attachment":[{"href":"https:\/\/blog.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=3481"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/id\/wp-json\/wp\/v2\/categories?post=3481"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/id\/wp-json\/wp\/v2\/tags?post=3481"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}