Claim Missing Document
Check
Articles

Found 4 Documents
Search
Journal : Journal of Information Systems Engineering and Business Intelligence

Penerapan Reverse Engineering Dalam Penentuan Pola Interaksi Sequence Diagram Pada Sampel Aplikasi Android Vierdy Sulfianto Rahmadani; Indra Kharisma Raharjana; Taufik Taufik
Journal of Information Systems Engineering and Business Intelligence Vol. 1 No. 1 (2015): April
Publisher : Universitas Airlangga

Show Abstract | Download Original | Original Source | Check in Google Scholar | Full PDF (544.862 KB) | DOI: 10.20473/jisebi.1.1.25-32

Abstract

Abstrak—Tujuan penelitian ini adalah penerapan reverse engineering untuk penentuan pola interaksi Sequence diagram yang bisa digunakan oleh sistem analis sebagai pola templateuntuk mendesain UML sequence diagram. Aplikasi yang digunakan sebagai data dasar berasal dari aplikasi contoh milik Android, aplikasi inilah yang mengalami proses reverse engineering dan teridentifikasi polanya. Tahap pertama yang dilakukan dalam penentuan pola interaksi ini adalah pengumpulan aplikasi dataset. Tahapan selanjutnya adalah identifikasi fitur dan aktifitas aplikasi, melakukan reverse engineeringsehingga didapatkan model sequence diagram,kemudian melakukan sistesis semua model tersebut menjadi pola interaksi sequence diagram. Langkah terakhir adalah menguji pola tersebut dengan menerapkannya dalam pembangunan aplikasi studi kasus. Berdasarkan hasil evaluasi, disimpulkan bahwa pola interaksi pada sequence diagram yang didapatkan dari penelitian ini dapat diterapkan pada perancangan perangkat lunak yang memiliki fitur-fitur yang sama dengan fitur-fitur yang terdapat pada penelitian ini. Kata Kunci— Reverse Engineering, Pola Interaksi, Sequence Diagram, AndroidAbstract—The purpose of this research is to apply the application of reverse engineering to determine interaction patterns of the Sequence diagram that can be used by system analysts as a template for designing UML sequence diagrams. Sample applications from android are used as dataset for reverse engineering and pattern identification. The first step is collecting application datasets. The next stage is identifying the features and applications activity, reverse engineering to obtain a sequence diagram model, and then synthesize all of the models into an interaction pattern of sequence diagram. The final step is to test the patterns by implementing it in an application development case stud. The evaluation results concludes that interaction patterns of sequence diagram designs obtained in reverse engineering steps is able to be implemented in software development that contained similar features with the obtained features in this research. Keywords— Reverse Engineering, Interaction Pattern, Sequence Diagram, Android
Visualisasi Data Menggunakan Sistem Informasi Geografis untuk Potensi Bank Sampah di Surabaya Muhammad Zaky Erdiansyah; Taufik Taufik; Indra Kharisma Raharjana
Journal of Information Systems Engineering and Business Intelligence Vol. 2 No. 1 (2016): April
Publisher : Universitas Airlangga

Show Abstract | Download Original | Original Source | Check in Google Scholar | Full PDF (1457.17 KB) | DOI: 10.20473/jisebi.2.1.40-49

Abstract

Abstrak—Bank sampah adalah tempat pemilahan dan pengumpulan sampah yang dapat didaur ulang dan digunakan ulang yang memiliki nilai ekonomi. Bank sampah memiliki potensi sampah yang bermanfaat, terdiri dari potensi sampah plastik, kertas, kaca dan besi. Potensi sampah tersebut dibutuhkan oleh perusahaan yang menggunakan bahan baku dari barang bekas pakai untuk di daur ulang menjadi produk yang memiliki harga di pasaran. Permasalahan bank sampah di Surabaya dapat dibagi menjadi dua masalah utama, yaitu pemantauan kegiatan bank sampah dan pencarian letak bank sampah beserta potensi yang dimiliki. Kedua permasalahan tersebut dapat diselesaikan dengan visualisasi data menggunakan sistem informasi geografis untuk potensi bank sampah di Surabaya. Sistem ini dibangun dengan langkah langkah sebagai berikut, yaitu pertama melakukan pengumpulan kebutuhan, analisis kebutuhan, perancangan sistem, pembangunan prototype, evaluasi dengan pengguna, pengembangan skala besar dan evaluasi sistem. Hasil evaluasi sistem menunjukkan bahwa 100% sistem berjalan dengan baik dan benar, 42.3% user sangat setuju, 51% user setuju, 6% user tidak setuju, dan 0.7 % user sangat tidak setuju bahwa visualisasi data menggunakan sistem informasi geografis untuk potensi bank sampah di Surabaya mempermudah pemantauan kegiatan penimbangan bank sampah dan mempermudah pencarian letak bank sampah beserta potensi yang dimiliki. Kata Kunci—bank sampah, visualisasi data, Sistem Informasi Geografis.Abstract—Trash bank was the place for sorting and collecting garbage that could be recycled and reused and had economic value. Trash bank had potential benefits, such as potential plastic, paper, glass and iron waste. This potential waste was needed by companies that use raw materials from used goods to be recycled into products that had market potential. Problems of trash bank in Surabaya could be divided into two main issues, first was the monitoring of the trash bank's activities, second was the search of trash bank location and its potential. Both of these problems could be solved by the data visualization using geographical information system for potential trash bank in Surabaya. This system was built with the following steps: requirements collection, requirements analysis, system design, prototype development, user evaluation, development of large-scale systems and evaluation. Results of the evaluation of the system showed that 100% of the system ran properly, 42.3% of users strongly agree, 51% of users agree, 6% of users did not agree, and 0.7% of users strongly did not agree that visualization of data using geographic information system for potential trash bank in Surabaya succeeded to facilitate the monitoring process of the of trash weighing activities in trash banks and helped the search of trash bank with its potential much easier. Keywords—Trash Bank, Data Visualization, Geographical Information System
Rancang Bangun Data Warehouse Untuk Pembuatan Laporan dan Analisis pada Data Kunjungan Pasien Rawat Jalan Rumah Sakit Universitas Airlangga Berbasis Online Analytical Processing (OLAP) Nur Ardista; Purbandini Purbandini; Taufik Taufik
Journal of Information Systems Engineering and Business Intelligence Vol. 3 No. 1 (2017): April
Publisher : Universitas Airlangga

Show Abstract | Download Original | Original Source | Check in Google Scholar | Full PDF (616.71 KB) | DOI: 10.20473/jisebi.3.1.40-51

Abstract

Abstrak— Rumah Sakit Universitas Airlangga (RSUA) merupakan sarana pelayanan kesehatan yang dikelola di bawah naungan Universitas Airlangga. Seiring berjalannya proses bisnis, jumlah pasien RSUA yang semakin bertambah menyebabkan data kunjungan pasien rawat jalan yang harus dikelola oleh bagian rekam medis semakin banyak. Data tersebut dikelola untuk digunakan dalam pembuatan laporan. Informasi dalam laporan dihasilkan melalui perhitungan secara manual atau menggunakan formula Microsoft Excel menjadi kendala dalam pembuatan laporan selain adanya kebutuhan laporan dengan format beragam dan analisis multidimensional. Data warehouse berbasis Online Analytical Processing (OLAP) dapat diterapkan untuk menangani masalah tersebut. Tujuan penelitian ini adalah merancang dan membangun data warehouse berbasis OLAP agar dapat digunakan oleh bagian rekam medis RSUA dalam pembuatan laporan. Data warehouse dibangun melalui tujuh tahap yaitu analisis, desain, proses ETL (Extraction, Transformation, and Loading), penerapan OLAP, uji coba, eksplorasi untuk hasil laporan dan analisis, serta evalusi. Perancangan data warehouse menggunakan Nine Step Methodology dengan pemodelan berupa fact constellation schema. Hasil implementasi data warehouse adalah aplikasi OLAP yang dapat digunakan untuk membantu kinerja bagian rekam medis RSUA dalam pembuatan laporan, baik berupa tabel pivot maupun grafik. Penilaian pengguna terhadap sistem data warehouse menunjukkan kategori baik dengan hasil penilaian sebesar 73.61 persen. Kata Kunci— Data Warehouse, Rawat Jalan, ETL, Nine Step Methodology, OLAPAbstract— Airlangga University Hospital is a health care facilities managed by the auspices of Airlangga University. Increasing number of patients in RSUA caused more outpatients’ visits data must be managed by the medical record unit. The data was used to report making. The information in the reports generated through manual calculation or used function of Microsoft Excel became a problem of report making in addition to their reporting needs with diverse formats and multidimensional analysis. Data warehouse based on Online Analytical Processing (OLAP) could implemented to solved the problem. The goal of this research were to designing and implementing the data warehouse based on OLAP so it could be used by medical record unit to making report. Data warehouse was implemented in seven process : analysis, design, ETL (Extraction, Transformation, and Loading), implementing OLAP, trial, explore the report and analysis, and evaluation. Design of data warehouse were using Nine Step Methodology and fact constellation schema model.The outcome of this research was an OLAP application that can used to help the task of RSUA medical record unit to making report using pivot table or chart. User ratings against the data warehouse system showed good category with the results of 73.61 percent in assessment. Keywords— Data Warehouse, Outpatient, ETL, Nine Step Methodology, OLAP
Analyzing Variances in User Story Characteristics: A Comparative Study of Stakeholders with Diverse Domain and Technical Knowledge in Software Requirements Elicitation Ersalina Trisnawati; Indra Kharisma Raharjana; Taufik Taufik; Ahmad Hoirul Basori; Nouf Atiahallah Alghanmi; Andi Besse Firdausiah Mansur
Journal of Information Systems Engineering and Business Intelligence Vol. 10 No. 1 (2024): February
Publisher : Universitas Airlangga

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.20473/jisebi.10.1.110-125

Abstract

Background: In Agile software development, an essential initial stage is eliciting software requirements. This process engages stakeholders to achieve comprehensive results. However, a common issue is the variance in domain and technical knowledge among stakeholders, potentially impacting the quality of software requirements elicitation. Objective: Understanding the characteristics of user stories produced by stakeholders becomes crucial, particularly considering the differences in domain and technical knowledge. This study aims to compare the characteristics of user stories generated by stakeholders with varying backgrounds in domain and technical expertise. Methods: The initial step involves categorizing respondents into distinct stakeholder groups. Three stakeholders are involved in this study, constituting a combination of those with high and low technical and domain knowledge. Subsequently, data collection of user stories is conducted across various case studies. Finally, the acquired user stories are analyzed for further insights. Results: The analysis reveals variations in user stories generated by the three stakeholder categories across the three case studies. Stakeholders with domain knowledge tend to focus on 'what' aspects with task elements and 'why' aspects with hard-goal elements. Meanwhile, technical knowledge crafts user stories with capability elements in the 'what' aspect. Utilizing the QUS framework, it is evident that technical knowledge consistently produces a higher number of high-quality user stories across all quality categories, Conclusion: The contribution offered by this study lies in determining the distinct characteristics of user stories produced by different types of stakeholders, focusing on disparities in domain and technical knowledge. The study highlights the comparison of various characteristics of user story elements, such as hard-goals, soft-goals, tasks, or capabilities, and assesses the quality of user stories based on the user story framework. Additionally, it endorse the importance of process innovation in shaping the requirements gathering process and subsequently influencing the quality of user stories.   Keywords: User story, Agile Software Development, Requirements Elicitation, Stakeholder, Domain Knowledge, Process Innovation