{"id":11007,"date":"2026-03-06T07:24:21","date_gmt":"2026-03-05T23:24:21","guid":{"rendered":"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/"},"modified":"2026-03-06T07:24:21","modified_gmt":"2026-03-05T23:24:21","slug":"writing-testing-procedure-use-case-flow-events","status":"publish","type":"post","link":"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/","title":{"rendered":"Menulis Prosedur Pengujian dalam Alur Kejadian Kasus Penggunaan"},"content":{"rendered":"<p>Di bidang <a href=\"https:\/\/www.visual-paradigm.com\/tw\/tutorials\/testingprocedure.jsp\">pengujian perangkat lunak<\/a>, \u201ckasus penggunaan\u201d dan \u201ckasus pengujian\u201d adalah istilah yang paling kritis dan saling terkait erat, tetapi sangat berbeda.<\/p>\n<ul>\n<li>Sebuah <strong>kasus penggunaan<\/strong>memberi tahu kita bagaimana sistem akan berperilaku atau melakukan tugas tertentu dalam kondisi tertentu.<\/li>\n<li>Sebuah <strong>kasus pengujian<\/strong>berisi data pengujian sebenarnya, set instruksi sistem, dan hasil yang diharapkan dari interaksi dengan sistem.<\/li>\n<\/ul>\n<p>Desain kasus pengujian mencakup prasyarat, nama kasus, kondisi input, dan hasil yang diharapkan. Dengan kata lain, kasus pengujian dapat diperoleh dari skenario kasus penggunaan berdasarkan serangkaian aktivitas pengujian yang berbeda, seperti input pengujian, kondisi eksekusi, dan hasil yang diharapkan, serta secara tambahan mengarah pada perkembangan tujuan pengujian tertentu.<\/p>\n<h3>Contoh Kasus Pengujian \u2013 ATM<\/h3>\n<p>Setelah mengembangkan skenario kasus penggunaan dengan alur kejadian, kasus pengujian juga dapat dikembangkan. Di sini akan ada skenario sukses dan langkah-langkah yang harus diselesaikan pengguna. Contoh langkah-langkah tersebut bisa seperti.<\/p>\n<ul>\n<li>Masukkan kartu.<\/li>\n<li>Memvalidasi kartu dan meminta PIN.<\/li>\n<li>Masukkan PIN.<\/li>\n<li>Memverifikasi PIN, lalu<\/li>\n<li>Izinkan akses ke akun.<\/li>\n<\/ul>\n<p>Setelah ini, terdapat daftar lanjutan dalam formulir. Misalnya, saat memverifikasi kartu, sistem dapat menentukan bahwa sesuatu tidak benar. Daftar lanjutan dapat dilihat di bawah ini.<\/p>\n<p>2a) Kartu tidak valid (pesan ditampilkan dan kartu ditolak).<br \/>\n3a) Kata sandi tidak valid (pesan ditampilkan dan permintaan ulang dilakukan\u2014dua kali), dan<br \/>\n4a) Kata sandi salah tiga kali (kartu dimakan dan keluar).<\/p>\n<h3>Kembangkan Kasus Pengujian di Visual Paradigm<\/h3>\n<p><iframe allow=\"fullscreen; accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" allowfullscreen=\"\" class=\"__youtube_prefs__ epyt-is-override no-lazyload\" data-no-lazy=\"1\" data-origheight=\"456\" data-origwidth=\"810\" data-skipgform_ajax_framebjll=\"\" height=\"456\" id=\"_ytid_60047\" loading=\"lazy\" referrerpolicy=\"strict-origin-when-cross-origin\" src=\"https:\/\/www.youtube.com\/embed\/THYp_mo4_6w?enablejsapi=1&amp;autoplay=0&amp;cc_load_policy=0&amp;cc_lang_pref=&amp;iv_load_policy=1&amp;loop=0&amp;rel=1&amp;fs=1&amp;playsinline=0&amp;autohide=2&amp;theme=dark&amp;color=red&amp;controls=1&amp;disablekb=0&amp;\" title=\"YouTube player\" width=\"810\"><\/iframe><\/p>\n<p>Seperti yang disebutkan dalam contoh di atas, Anda dapat menentukan langkah-langkah yang diperlukan untuk menyelesaikan sebuah kasus penggunaan. Selain itu, Anda dapat membuat kasus pengujian di sekitar langkah-langkah tersebut, untuk memastikan bahwa kasus penggunaan akan diselesaikan dengan benar dalam berbagai situasi. Dalam tutorial ini, kita akan membuat kasus pengujian untuk kasus penggunaan bernama Login.<\/p>\n<hr\/>\n<ul>\n<li class=\"row medium-12 large-12 columns\">\n<div class=\"tut-page-content\">\n<article>\n<div class=\"tour\">\n<ol class=\"contentList\">\n<li>Unduh <a href=\"https:\/\/d1dlalugb0z2hd.cloudfront.net\/ag\/tutorials\/flowofeventstestcase_screenshots\/resources\/Webmail%20System.vpp\">Webmail System.vpp<\/a>. Anda juga dapat menemukan file ini di bagian bawah tutorial ini.<\/li>\n<li>Buka file .vpp yang diunduh di Visual Paradigm. Untuk membuka proyek, pilih <b>Proyek &gt; Buka<\/b> dari bilah alat aplikasi.<\/li>\n<li>Buka diagram kasus penggunaan<i>Model Kasus Penggunaan Sistem Webmail<\/i>. Anda harus melihat ini:<br \/>\n<img alt=\"use case diagram\" decoding=\"async\" height=\"330\" loading=\"lazy\" src=\"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/01_use_case_diagram.png\" width=\"440\"\/><\/li>\n<li>Kita perlu mengedit kasus uji dari sebuah kasus penggunaan. Untuk melakukannya, buka<b>Rincian Kasus Penggunaan<\/b> pada kasus penggunaan<i>Masuk<\/i> dengan mengklik kanan pada itu dan memilih<b>Rincian Kasus Penggunaan<\/b> dari menu pop-up.<br \/>\n<img alt=\"open use case details\" decoding=\"async\" height=\"188\" loading=\"lazy\" src=\"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/02_open_use_case_details.png\" width=\"348\"\/><\/li>\n<li>Buka halaman dari<b>Alur Kejadian<\/b>. Kasus penggunaan<i>Masuk<\/i>dibentuk oleh sejumlah langkah sederhana \u2013 masukkan nama pengguna dan kata sandi, lalu klik Kirim. Yang perlu kita lakukan adalah menulis kasus uji untuk memastikan ketiga langkah ini akan berfungsi sesuai harapan pada produk akhir.<br \/>\n<img alt=\"open flow of events\" decoding=\"async\" height=\"179\" loading=\"lazy\" src=\"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/03_open_flow_of_events.png\" width=\"563\"\/><\/li>\n<li>Pindahkan pointer mouse ke sisi kanan alur kejadian, klik pada menu turun<b>(Menu)<\/b> dan pilih<b>Utama<\/b>. Menu turun ini digunakan untuk pemilihan kasus uji.<b>Utama<\/b>Ini adalah yang bawaan.<br \/>\n<img alt=\"select main\" decoding=\"async\" height=\"165\" loading=\"lazy\" src=\"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/04_select_main.png\" width=\"242\"\/><br \/>\nSekarang, halaman alur kejadian dibagi menjadi tiga kolom \u2013<b>Langkah, Prosedur<\/b> dan<b>Hasil yang Diharapkan<\/b>. Dengan menelusuri langkah-langkahnya, kasus penggunaan dikatakan selesai. Prosedur dan hasil yang diharapkan dibuat untuk keperluan pengujian. Prosedur adalah langkah-langkah yang dibutuhkan untuk menguji suatu langkah, sedangkan hasil yang diharapkan adalah hasil yang diharapkan setelah melakukan prosedur pengujian.<br \/>\n<img alt=\"three cols\" decoding=\"async\" height=\"186\" loading=\"lazy\" src=\"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/05_three_cols.png\" width=\"720\"\/><\/li>\n<li>Kami ingin mulai dengan menulis kasus uji yang valid. Pada langkah pertama, kami akan menguji pemasukan nama pengguna dengan memasukkan peter, dengan mengasumsikan bahwa peter adalah pengguna yang valid dan ada, serta mengharapkan nama peter muncul di bidang nama pengguna. Masukkan<i>Isi peter sebagai nama pengguna<\/i> di sel Prosedur langkah 1. Tidak diragukan lagi bahwa memasukkan teks ke dalam bidang akan membuat teks muncul di bidang tersebut, sehingga kami hanya mengabaikan hasil yang diharapkan di sini. Jika Anda ingin, Anda masih bisa memasukkan<i>Teks &#8220;peter&#8221; ditampilkan di bidang nama pengguna<\/i>, tetapi terlihat sedikit rumit.<br \/>\n<img alt=\"enter proc step1\" decoding=\"async\" height=\"181\" loading=\"lazy\" src=\"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/06_enter_proc_step1.png\" width=\"720\"\/><\/li>\n<li>Untuk langkah kedua<i>Masukkan kata sandi<\/i>, tentukan<i>Isi mypwd sebagai kata sandi<\/i> di <b>Prosedur<\/b> sel. Untuk memastikan bidang kata sandi yang benar digunakan, kita perlu menentukan hasil yang diharapkan dengan memasukkan<i>Lima karakter bintang (yaitu *) ditampilkan<\/i> di <b>Hasil yang Diharapkan<\/b> sel.<br \/>\n<img alt=\"enter proc step2\" decoding=\"async\" height=\"186\" loading=\"lazy\" src=\"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/07_enter_proc_step2.png\" width=\"720\"\/><\/li>\n<li>Untuk langkah ketiga, tentukan<i>Klik [Kirim]<\/i> di <b>Prosedur<\/b> sel. Masukkan<i>Kotak masuk Peter ditampilkan<\/i> dalam hasil yang diharapkan.<br \/>\n<img alt=\"enter proc step3\" decoding=\"async\" height=\"198\" loading=\"lazy\" src=\"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/08_enter_proc_step3.png\" width=\"720\"\/><\/li>\n<li>Penamaan kasus uji<b>Utama<\/b> tidak cukup deskriptif. Mari kita ubah. Klik pada tombol<b>\u2026<\/b> di sebelah menu tarik-turun<b>Utama<\/b>.<br \/>\n<img alt=\"edit test case\" decoding=\"async\" height=\"124\" loading=\"lazy\" src=\"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/09_edit_test_case.png\" width=\"190\"\/><\/li>\n<li>Di dalam kotak dialog<b>Prosedur Pengujian<\/b> kotak dialog, klik kanan<b>Utama<\/b> dan pilih <b>Ubah Nama<\/b> dari menu pop-up. Masukkan <i>Masuk dengan nama pengguna dan kata sandi yang valid<\/i> sebagai nama.<br \/>\n<img alt=\"rename main\" decoding=\"async\" height=\"300\" loading=\"lazy\" src=\"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/10_rename_main.png\" width=\"300\"\/><\/li>\n<li>Mari kita tambahkan kasus uji lain untuk menguji penggunaan yang tidak valid. Di dalam <b>Kotak Dialog Prosedur Pengujian<\/b> kotak dialog, klik tombol +, masukkan <i>Masuk tanpa nama pengguna dan kata sandi<\/i> sebagai nama. Konfirmasi perubahan dan kembali ke halaman alur kejadian.<br \/>\n<img alt=\"new testing procedures\" decoding=\"async\" height=\"300\" loading=\"lazy\" src=\"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/11_new_testing_procedures.png\" width=\"300\"\/><\/li>\n<li>Kasus uji sekarang adalah <i>Masuk tanpa nama pengguna dan kata sandi<\/i>. Mari kita isi prosedur dan hasil yang diharapkan seperti yang ditunjukkan di bawah ini:<br \/>\n<table border=\"1\">\n<tbody>\n<tr>\n<th>Langkah<\/th>\n<th>Prosedur<\/th>\n<th>Hasil yang Diharapkan<\/th>\n<\/tr>\n<tr>\n<td>Masukkan nama pengguna<\/td>\n<td>Jangan masukkan apa pun<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>Masukkan kata sandi<\/td>\n<td>Jangan masukkan apa pun<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>Klik [Kirim] untuk membuka halaman Kotak Masuk<\/td>\n<td>Klik [Kirim]<\/td>\n<td>Peringatan: \u201cHarap tentukan nama pengguna dan kata sandi\u201d muncul. Masuk dibatalkan.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/li>\n<li>Simpan proyek. Ini mengakhiri tutorial.<\/li>\n<\/ol>\n<\/div>\n<\/article>\n<h3><strong>Referensi:<\/strong><\/h3>\n<ul>\n<li><a href=\"https:\/\/www.visual-paradigm.com\/guide\/uml-unified-modeling-language\/what-is-use-case-diagram\/\">Apa itu Diagram Kasus Penggunaan?<\/a><\/li>\n<li><a href=\"https:\/\/www.visual-paradigm.com\/guide\/uml-unified-modeling-language\/types-of-actor-in-use-case-model\/\">Jenis-Jenis Aktor dalam Model Kasus Penggunaan<\/a><\/li>\n<li><a href=\"https:\/\/www.visual-paradigm.com\/guide\/sysml\/identify-user-requirements-with-use-case-diagrams\/\">Identifikasi Kebutuhan Pengguna dengan Diagram Kasus Penggunaan<\/a><\/li>\n<li><a href=\"https:\/\/www.visual-paradigm.com\/guide\/use-case\/what-is-use-case-specification\/\">Apa itu Spesifikasi Kasus Penggunaan?<\/a><\/li>\n<li><a href=\"https:\/\/www.visual-paradigm.com\/guide\/uml-unified-modeling-language\/robustness-analysis-tutorial\/\">Tutorial Praktis tentang Analisis Ketahanan<\/a><\/li>\n<li><a href=\"https:\/\/www.visual-paradigm.com\/guide\/agile-software-development\/user-story-vs-use-case\/\">Cerita Pengguna vs Kasus Penggunaan untuk Pengembangan Perangkat Lunak Agile<\/a><\/li>\n<li><a href=\"https:\/\/www.visual-paradigm.com\/guide\/agile-software-development\/what-is-use-case-driven-approach-for-agile\/\">Pendekatan Berbasis Kasus Penggunaan untuk Pengembangan Agile<\/a><\/li>\n<\/ul>\n<\/div>\n<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>In the area of software testing, &#8220;use case&#8221; and &#8220;test case&#8221; are the most critical and closely interrelated terms, but they are quite different. A use case tells us how a system will behave or perform a given task under given conditions. A test case contains the actual test data, the instruction set of the system, and the expected results of the interaction with the system.<\/p>\n","protected":false},"author":3479,"featured_media":11008,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_yoast_wpseo_title":"","_yoast_wpseo_metadesc":"","fifu_image_url":"https:\/\/cdn-images.visual-paradigm.com\/ag\/tutorials\/flowofeventstestcase_screenshots\/08_enter_proc_step3.png","fifu_image_alt":"","footnotes":""},"categories":[127],"tags":[],"class_list":["post-11007","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-unified-modeling-language"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.0 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Menulis Prosedur Pengujian dalam Alur Kejadian Kasus Penggunaan - ArchiMetric Indonesian<\/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:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Menulis Prosedur Pengujian dalam Alur Kejadian Kasus Penggunaan - ArchiMetric Indonesian\" \/>\n<meta property=\"og:description\" content=\"In the area of software testing, &quot;use case&quot; and &quot;test case&quot; are the most critical and closely interrelated terms, but they are quite different. A use case tells us how a system will behave or perform a given task under given conditions. A test case contains the actual test data, the instruction set of the system, and the expected results of the interaction with the system.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/\" \/>\n<meta property=\"og:site_name\" content=\"ArchiMetric Indonesian\" \/>\n<meta property=\"article:published_time\" content=\"2026-03-05T23:24:21+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/cdn-images.visual-paradigm.com\/ag\/tutorials\/flowofeventstestcase_screenshots\/08_enter_proc_step3.png\" \/><meta property=\"og:image\" content=\"https:\/\/cdn-images.visual-paradigm.com\/ag\/tutorials\/flowofeventstestcase_screenshots\/08_enter_proc_step3.png\" \/>\n\t<meta property=\"og:image:width\" content=\"720\" \/>\n\t<meta property=\"og:image:height\" content=\"198\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"archimetric@visual-paradigm.com\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/cdn-images.visual-paradigm.com\/ag\/tutorials\/flowofeventstestcase_screenshots\/08_enter_proc_step3.png\" \/>\n<meta name=\"twitter:label1\" content=\"Ditulis oleh\" \/>\n\t<meta name=\"twitter:data1\" content=\"archimetric@visual-paradigm.com\" \/>\n\t<meta name=\"twitter:label2\" content=\"Estimasi waktu membaca\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 menit\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/\"},\"author\":{\"name\":\"archimetric@visual-paradigm.com\",\"@id\":\"https:\/\/www.archimetric.com\/id\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28\"},\"headline\":\"Menulis Prosedur Pengujian dalam Alur Kejadian Kasus Penggunaan\",\"datePublished\":\"2026-03-05T23:24:21+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/\"},\"wordCount\":814,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.archimetric.com\/id\/wp-content\/uploads\/sites\/15\/2026\/03\/08_enter_proc_step3.png\",\"articleSection\":[\"Unified Modeling Language\"],\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/\",\"url\":\"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/\",\"name\":\"Menulis Prosedur Pengujian dalam Alur Kejadian Kasus Penggunaan - ArchiMetric Indonesian\",\"isPartOf\":{\"@id\":\"https:\/\/www.archimetric.com\/id\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.archimetric.com\/id\/wp-content\/uploads\/sites\/15\/2026\/03\/08_enter_proc_step3.png\",\"datePublished\":\"2026-03-05T23:24:21+00:00\",\"author\":{\"@id\":\"https:\/\/www.archimetric.com\/id\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/#primaryimage\",\"url\":\"https:\/\/www.archimetric.com\/id\/wp-content\/uploads\/sites\/15\/2026\/03\/08_enter_proc_step3.png\",\"contentUrl\":\"https:\/\/www.archimetric.com\/id\/wp-content\/uploads\/sites\/15\/2026\/03\/08_enter_proc_step3.png\",\"width\":720,\"height\":198},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.archimetric.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Menulis Prosedur Pengujian dalam Alur Kejadian Kasus Penggunaan\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.archimetric.com\/id\/#website\",\"url\":\"https:\/\/www.archimetric.com\/id\/\",\"name\":\"ArchiMetric Indonesian\",\"description\":\"EA, Dev Ops, Scrum, Agile and More\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.archimetric.com\/id\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"id\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.archimetric.com\/id\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28\",\"name\":\"archimetric@visual-paradigm.com\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/www.archimetric.com\/id\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/de58c1924d83d002dbce0b79f74ba4b70e2f85238332df6cabc0227effdf470d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/de58c1924d83d002dbce0b79f74ba4b70e2f85238332df6cabc0227effdf470d?s=96&d=mm&r=g\",\"caption\":\"archimetric@visual-paradigm.com\"},\"url\":\"https:\/\/www.archimetric.com\/id\/author\/archimetricvisual-paradigm-com\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Menulis Prosedur Pengujian dalam Alur Kejadian Kasus Penggunaan - ArchiMetric Indonesian","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:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/","og_locale":"id_ID","og_type":"article","og_title":"Menulis Prosedur Pengujian dalam Alur Kejadian Kasus Penggunaan - ArchiMetric Indonesian","og_description":"In the area of software testing, \"use case\" and \"test case\" are the most critical and closely interrelated terms, but they are quite different. A use case tells us how a system will behave or perform a given task under given conditions. A test case contains the actual test data, the instruction set of the system, and the expected results of the interaction with the system.","og_url":"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/","og_site_name":"ArchiMetric Indonesian","article_published_time":"2026-03-05T23:24:21+00:00","og_image":[{"url":"https:\/\/cdn-images.visual-paradigm.com\/ag\/tutorials\/flowofeventstestcase_screenshots\/08_enter_proc_step3.png","type":"","width":"","height":""},{"width":720,"height":198,"url":"https:\/\/cdn-images.visual-paradigm.com\/ag\/tutorials\/flowofeventstestcase_screenshots\/08_enter_proc_step3.png","type":"image\/png"}],"author":"archimetric@visual-paradigm.com","twitter_card":"summary_large_image","twitter_image":"https:\/\/cdn-images.visual-paradigm.com\/ag\/tutorials\/flowofeventstestcase_screenshots\/08_enter_proc_step3.png","twitter_misc":{"Ditulis oleh":"archimetric@visual-paradigm.com","Estimasi waktu membaca":"7 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/#article","isPartOf":{"@id":"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/"},"author":{"name":"archimetric@visual-paradigm.com","@id":"https:\/\/www.archimetric.com\/id\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28"},"headline":"Menulis Prosedur Pengujian dalam Alur Kejadian Kasus Penggunaan","datePublished":"2026-03-05T23:24:21+00:00","mainEntityOfPage":{"@id":"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/"},"wordCount":814,"commentCount":0,"image":{"@id":"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/#primaryimage"},"thumbnailUrl":"https:\/\/www.archimetric.com\/id\/wp-content\/uploads\/sites\/15\/2026\/03\/08_enter_proc_step3.png","articleSection":["Unified Modeling Language"],"inLanguage":"id","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/","url":"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/","name":"Menulis Prosedur Pengujian dalam Alur Kejadian Kasus Penggunaan - ArchiMetric Indonesian","isPartOf":{"@id":"https:\/\/www.archimetric.com\/id\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/#primaryimage"},"image":{"@id":"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/#primaryimage"},"thumbnailUrl":"https:\/\/www.archimetric.com\/id\/wp-content\/uploads\/sites\/15\/2026\/03\/08_enter_proc_step3.png","datePublished":"2026-03-05T23:24:21+00:00","author":{"@id":"https:\/\/www.archimetric.com\/id\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28"},"breadcrumb":{"@id":"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/"]}]},{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/#primaryimage","url":"https:\/\/www.archimetric.com\/id\/wp-content\/uploads\/sites\/15\/2026\/03\/08_enter_proc_step3.png","contentUrl":"https:\/\/www.archimetric.com\/id\/wp-content\/uploads\/sites\/15\/2026\/03\/08_enter_proc_step3.png","width":720,"height":198},{"@type":"BreadcrumbList","@id":"https:\/\/www.archimetric.com\/id\/writing-testing-procedure-use-case-flow-events\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.archimetric.com\/id\/"},{"@type":"ListItem","position":2,"name":"Menulis Prosedur Pengujian dalam Alur Kejadian Kasus Penggunaan"}]},{"@type":"WebSite","@id":"https:\/\/www.archimetric.com\/id\/#website","url":"https:\/\/www.archimetric.com\/id\/","name":"ArchiMetric Indonesian","description":"EA, Dev Ops, Scrum, Agile and More","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.archimetric.com\/id\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"id"},{"@type":"Person","@id":"https:\/\/www.archimetric.com\/id\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28","name":"archimetric@visual-paradigm.com","image":{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/www.archimetric.com\/id\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/de58c1924d83d002dbce0b79f74ba4b70e2f85238332df6cabc0227effdf470d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/de58c1924d83d002dbce0b79f74ba4b70e2f85238332df6cabc0227effdf470d?s=96&d=mm&r=g","caption":"archimetric@visual-paradigm.com"},"url":"https:\/\/www.archimetric.com\/id\/author\/archimetricvisual-paradigm-com\/"}]}},"_links":{"self":[{"href":"https:\/\/www.archimetric.com\/id\/wp-json\/wp\/v2\/posts\/11007","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.archimetric.com\/id\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.archimetric.com\/id\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.archimetric.com\/id\/wp-json\/wp\/v2\/users\/3479"}],"replies":[{"embeddable":true,"href":"https:\/\/www.archimetric.com\/id\/wp-json\/wp\/v2\/comments?post=11007"}],"version-history":[{"count":0,"href":"https:\/\/www.archimetric.com\/id\/wp-json\/wp\/v2\/posts\/11007\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.archimetric.com\/id\/wp-json\/wp\/v2\/media\/11008"}],"wp:attachment":[{"href":"https:\/\/www.archimetric.com\/id\/wp-json\/wp\/v2\/media?parent=11007"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.archimetric.com\/id\/wp-json\/wp\/v2\/categories?post=11007"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.archimetric.com\/id\/wp-json\/wp\/v2\/tags?post=11007"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}