Hasil Pencarian  ::  Simpan CSV :: Kembali

"Fokus utama penelitian ini adalah merancang dan mengembangkan prototipe sistem registrasi IRS berbasisevent-driven architecture serta mengevaluasi sistem tersebut dengan eksperimen chaos engineering.Implementasi sistem menggunakan Spring Boot framework, Apache Kafka sebagai event broker, dan AmazonWeb Service (AWS) untuk infrastruktur. Pengujian dilakukan dengan melakukan API testing untuk mengujifungsionalitas sistem dan load testing untuk menguji reliability sistem. Terakhir, eksperimen chaos engineeringdengan metode chaos monkey dilakukan untuk menguji resilience sistem. Hasil pengujian menunjukkan bahwafungsionalitas sistem sebagai layanan IRS bekerja dengan baik. Sistem dapat tetap bekerja di bawah tekanan40.000 mahasiswa yang disimulasikan mengakses sistem bersamaan. Pada kondisi chaos di mana beberapaserver dimatikan, sistem masih dapat berfungsi dengan baik dan mahasiswa masih dapat menggunakan layananregistrasi IRS tanpa masalah.

---

The main focus of this research is to design and develop a prototype of an event-driven architecture based course

registration service, and to evaluate the system with chaos engineering. The system was implemented using

Spring Boot as its framework, Apache Kafka as the event broker, and Amazon Web Service (AWS) for

infrastructure. The testing was done by implementing API testing for evaluating the system’s functionality and

load testing to evaluate system’s reliability. Finally, a chaos engineering experiment was carried out to evaluate

the resilience of the system. The result shows that the system can deliver its functionality as a course plan

registry pretty well. The system was able to work under the pressure of 40.000 student simulated to access the

system simultaneously. In the chaos condition where several server were taken down, the system still performs

well and able to provide the service without any problem for the students."

"Fokus utama penelitian ini adalah merancang dan mengembangkan prototipe sistem registrasi IRS berbasis event-driven architecture serta mengevaluasi sistem tersebut dengan eksperimen chaos engineering. Implementasi sistem menggunakan Spring Boot framework, Apache Kafka sebagai event broker, dan Amazon Web Service (AWS) untuk infrastruktur. Pengujian dilakukan dengan melakukan API testing untuk menguji fungsionalitas sistem dan load testing untuk menguji reliability sistem. Terakhir, eksperimen chaos engineering dengan metode chaos monkey dilakukan untuk menguji resilience sistem. Hasil pengujian menunjukkan bahwa fungsionalitas sistem sebagai layanan IRS bekerja dengan baik. Sistem dapat tetap bekerja di bawah tekanan 40.000 mahasiswa yang disimulasikan mengakses sistem bersamaan. Pada kondisi chaos di mana beberapa server dimatikan, sistem masih dapat berfungsi dengan baik dan mahasiswa masih dapat menggunakan layanan registrasi IRS tanpa masalah.

---

The main focus of this research is to design and develop a prototype of an event-driven architecture based course registration service, and to evaluate the system with chaos engineering. The system was implemented using Spring Boot as its framework, Apache Kafka as the event broker, and Amazon Web Service (AWS) for infrastructure. The testing was done by implementing API testing for evaluating the system’s functionality and load testing to evaluate system’s reliability. Finally, a chaos engineering experiment was carried out to evaluate the resilience of the system. The result shows that the system can deliver its functionality as a course plan registry pretty well. The system was able to work under the pressure of 40.000 student simulated to access the system simultaneously. In the chaos condition where several server were taken down, the system still performs well and able to provide the service without any problem for the students."

"Sekarang ini komputer merupakan sebuah alat yang tidak asing lagi terhadap kita dalam berkehidupan, yang dimana dapat terlihat dari segi kita beraktivitas, seperti berkerja maupun berkomunikasi. Dapat dipastikan dalam kehidupan kita sehari-hari ada saja interaksi, antara kita dengan komputer. Bisa dikatakan kehadiran komputer mampu merubah acuan persepsi kita terhadap realita dan akan selalu mempengaruhi pola kehidpuan. Dalam pemrosesan perancangan Arsitektur pun tidak dapat dipisahkannya peran sebuah komputer, kerap digunakanya sebuah perangkat-lunak yang dijalankan oleh komputer untuk dapat membantu memberikan penggambaran pengalaman sebuah realita yang akan ataupun yang telah selesai dirancang oleh seorang arsitek. Revit arsitektur, Lumion3d dan LayAR ialah sebuah perangkat lunak yang mengikuti perkembangan teknologi komputer, walaupun kajian ketiga perangkat-lunak ini sama yaitu untuk hal yang informatif, namun ketiga perangkat-lunak ini menggunakan teknologi komputer yang berbeda. Skripsi ini akan membahas sampai sejauh mana kemampuan ketiga perangkat-lunak yang dijalankan oleh komputer tersebut mampu memberikan kita kepada sebuah sensasi dalam merasakan arsitektur.

---

Computer is a device that no longer odd in our daily life. It's shown in our activities such as communicating, working, socializing, and entertaining ourselves. It can assured that there are interactions between us and computer every day. Therefore, the presence of computer can change the matter of our perspective on reality and lifestyle. Computer has a big part in the process of architectural design. Some software in computer that has made for architect can be used to given an experienced drawings of reality that has been designed by an architect. Revit architecture, Lumion3d and LayAr are the software's that followed the ongoing technological developments, even though the contents of the software's are all the same, for informative purpose. However, this three software are using a different technology. This thesis will discuss how far the software's abilities can get us through to a sensation of the architectural world."

"Software engineering : architecture-driven software development is the first comprehensive guide to the underlying skills embodied in the IEEE's Software Engineering Body of Knowledge (SWEBOK) standard. Standards expert Richard Schmidt explains the traditional software engineering practices recognized for developing projects for government or corporate systems.Software engineering education often lacks standardization, with many institutions focusing on implementation rather than design as it impacts product architecture. Many graduates join the workforce with incomplete skills, leading to software projects that either fail outright or run woefully over budget and behind schedule.Additionally, software engineers need to understand system engineering and architecture—the hardware and peripherals their programs will run on. This issue will only grow in importance as more programs leverage parallel computing, requiring an understanding of the parallel capabilities of processors and hardware. This book gives both software developers and system engineers key insights into how their skillsets support and complement each other. With a focus on these key knowledge areas, software engineering offers a set of best practices that can be applied to any industry or domain involved in developing software products."

"Dalam pengembangan suatu aplikasi, sangat penting untuk memperhatikan beberapa metrik utama yang menunjang keberlangsungan aplikasi tersebut. Metrik yang dimaksud dalam pembahasan ini adalah Performance, Scalability, Availability, dan Maintenance. Pada umumnya pembuatan sebuah aplikasi dimulai dengan arsitektur monolitik untuk menghindari kompleksitas dan mempercepat proses pengembangan dengan jumlah developer yang terbatas. Seiring dengan dilakukannya continuous development akan menyebabkan codebase dari aplikasi tersebut membesar dan akan sangat sulit untuk melakukan perawatan maupun penambahan sebuah fitur baru. Hal tersebut dikarenakan setiap perubahan yang dilakukan dapat mempengaruhi keseluruhan aplikasi karena pada dasarnya setiap servis ditempatkan dalam sebuah instance yang sama. Dengan melakukan migrasi dari arsitektur monolitik menuju microservice terdapat beberapa keuntungan yang diperoleh seperti pengembangan secara paralel, melakukan scaling hanya pada layanan tertentu, memungkinkan penerapan pipeline, dan meningkatkan fleksibilitas aplikasi . Keuntungan tersebut dapat diperoleh dikarenakan setiap servis akan terpisah antara satu dengan yang lainnya. Namun, pelaksanaan migrasi tentunya bukan hal yang mudah untuk dilakukan karena diperlukan perancangan terlebih dahulu yang didasarkan pada kebutuhan masing-masing aplikasi. Dari penerapan migrasi yang dilakukan pada aplikasi Automation Messaging System, diperoleh bahwa terdapat peningkatan performa sebesar 68.10% dalam response time dan 36.02% lebih ringan dalam CPU Utilization. Perbandingan pada metrik lainnya juga mampu memberikan keunggulan dibandingkan arsitektur monolitik, seperti kemampuan scaling yang lebih efektif, kemudahan dalam melakukan perawatan, dan penurunan biaya bulanan infrastruktur sebesar 16.26%.

---

There are several important metrics needs to be considered when developing an application such as Performance, Scalability, Availability, and Maintenance aspects. In general, an application started developed using monolithic architecture to simplify and shorten the development process with limited amount of engineers. However, as we implemented the continuous development process, the source code of the application will expand as the time goes on and it will be very hard to maintain or add a new feature into it. This can happen because every code changes in monolithic application will affect the entire application as all the service registered inside are placed inside the same instance. Hence, the migration from Monolithic to Microservices is important because it provides numerous benefits, such as the separation of each service from one another, which enables parallel development possibilities. The other advantage are allowing pipeline implementation, increase technology stack flexibility, and improve scalability. These advantages can be obtained because each service is loosely-coupled or separated from one another. However, the implementation of the migration itself is not an easy task as it requires prior planning based on the specific needs of each application. Through the performed migration on the Automation Messaging System application, it was found that there was a 68.10% improvement in response time and a 36.02% less usage in CPU utilization. Furthermore, the comparison with other metrics also showed the superiority of the microservices architecture over the monolithic architecture, such as more effective scaling capabilities, ease of maintenance, and a monthly infrastructure cost reduction of 16.26%."

"Agile software development approaches have had significant impact on industrial software development practices. Today, agile software development has penetrated to most IT companies across the globe, with an intention to increase quality, productivity, and profitability. Comprehensive knowledge is needed to understand the architectural challenges involved in adopting and using agile approaches and industrial practices to deal with the development of large, architecturally challenging systems in an agile way.Agile software architecture focuses on gaps in the requirements of applying architecture-centric approaches and principles of agile software development and demystifies the agile architecture paradox. Readers will learn how agile and architectural cultures can co-exist and support each other according to the context. Moreover, this book will also provide useful leads for future research in architecture and agile to bridge such gaps by developing appropriate approaches that incorporate architecturally sound practices in agile methods."

"This volume conveniently brings together updated versions of 30 articles that originally appeared in SIAM News from 1990 to 1995. The objective of the column from which the articles are taken is to present applications that have been successfully treated on advanced architecture computers. Astfalk edits this popular series of articles in SIAM's flagship publication, SIAM News. Algorithmic issues addressed are those which have found general use in building parallel codes for solving problems. In addition to updates that reflect advances and changes in the field of applications on advanced architecture computers, Astfalk has added an index and introductory comments to each article, making this book cohesive and interesting to practitioners and researchers alike. Although some of the computers used in older articles are no longer available and some of the languages are rarely used, what is valuable in these articles is the diversity of areas to which advanced computing can be applied. Perhaps more valuable than the diversity are the successful methods used to achieve parallelism. This may be used by others for similar applications. The applications and technology discussed cover many disciplines, with significant overlap. Articles deal with molecular dynamics, optimization/math programming, finance/economics, geometry, and partial differential equations."

"[The approach described in this book focuses on the notion of a service as a piece of functionality that offers value to its customers. Instead of solely looking at agility in the context of system or software development, agility is approached in a broader context. The authors illustrate three kinds of agility that can be found in an agile enterprise: business, process and system agility. These three types of agility reinforce each other and establish the foundation for the agile enterprise. Architecture, patterns, models, and all of the best practices in system development contribute to agile service development and building agile applications.This book addresses two audiences. On the one hand, it aims at agile and architecture practitioners who are looking for more agile ways of working in designing and building business services or who are interested in extending and improving their agile methods by using models and model-based architectures. On the other hand, it addresses students of (enterprise) architecture and software development or service science courses, both in computer science and in business administration., The approach described in this book focuses on the notion of a service as a piece of functionality that offers value to its customers. Instead of solely looking at agility in the context of system or software development, agility is approached in a broader context. The authors illustrate three kinds of agility that can be found in an agile enterprise: business, process and system agility. These three types of agility reinforce each other and establish the foundation for the agile enterprise. Architecture, patterns, models, and all of the best practices in system development contribute to agile service development and building agile applications.This book addresses two audiences. On the one hand, it aims at agile and architecture practitioners who are looking for more agile ways of working in designing and building business services or who are interested in extending and improving their agile methods by using models and model-based architectures. On the other hand, it addresses students of (enterprise) architecture and software development or service science courses, both in computer science and in business administration.]"

"Personal health record (PHR) membentuk tren dari informasi yang dikendalikan oleh sistem kesehatan ke individu. Di negara-negara maju, PHR sudah digunakan secara luas, tetapi sistem ini belum diadopsi luas di negara-negara berkembang. Penelitian ini dilakukan di Indonesia karena mencerminkan karakteristik negara berkembang dengan jumlah penduduk terbesar di kawasan Asia Tenggara. Meningkatnya jumlah penyakit kronis dan adanya pandemi COVID-19 mendorong inovasi teknologi informasi yang mendukung perawatan dan pencegahan penyakit. Penelitian ini bertujuan membahas faktor-faktor penghambat dan pendorong adopsi sistem PHR di Indonesia serta merancang arsitektur sistem PHR terintegrasi dan prototipe aplikasi mobile PHR (mPHR) dengan pendekatan design science research. Faktor-faktor penghambat dan pendorong adopsi sistem PHR di Indonesia diperoleh melalui pengambilan data kualitatif dengan wawancara kepada Kementerian kesehatan (2 responden), BPJS kesehatan (1 responden), pusat kesehatan masyarakat (puskesmas) (6 responden), klinik (4 responden), rumah sakit umum atau pemerintah (13 responden), dan rumah sakit swasta (8 responden) dengan teknik analisis data menggunakan thematic analysis. Hasil analisis menghasilkan penghambat dan pendorong adopsi sistem PHR yang terdiri dari faktor teknologi, organisasi, lingkungan, dan individu. Kemudian, untuk mengetahui kebutuhan sistem PHR terintegrasi, pengumpulan data kualitatif dengan wawancara dilakukan kepada Kementerian kesehatan (2 responden), BPJS kesehatan (1 responden), puskesmas (6 responden), klinik (4 responden), rumah sakit umum atau pemerintah (13 responden), rumah sakit swasta (8 responden), dan vendor aplikasi kesehatan (3 responden) serta secara kuantitatif dengan penyebaran kuesioner kepada warga negara Indonesia yang berusia 17 tahun ke atas. Pada tahapan ini, data kualitatif dianalisis dengan content analysis, sedangkan data kuantatif dianalisis dengan descriptive statistics. Arsitektur sistem PHR terintegrasi yang dirancang mengacu pada The Open Group Architecture Framework (TOGAF) 9.2 yang terdiri dari visi arsitektur, arsitektur bisnis, arsitektur aplikasi, arsitektur data, dan arsitektur teknologi. Selanjutnya, hasil rancangan arsitektur menjadi masukan untuk merancang prototipe high fidelity aplikasi mPHR. Fungsionalitas yang dikembangkan pada rancangan prototipe mPHR yaitu fungsi prioritas yang didefinisikan pada rancangan arsitektur. Evaluasi arsitektur dan prototipe dilakukan dengan wawancara kepada 6 responden IT atau e-health expert yang berasal dari Kementerian kesehatan, akademisi, fasilitas kesehatan, dan vendor aplikasi kesehatan. Penelitian ini diharapkan dapat memberikan kontribusi teoritis mengenai kajian adopsi PHR di negara berkembang dan menjadi panduan kepada fasilitas kesehatan, regulator kesehatan, dan vendor aplikasi kesehatan untuk mewujudkan PHR yang terintegrasi di Indonesia.

---

Personal health records (PHR) transform the trend from information controlled by the health system to information controlled by individuals. In developed countries, PHR has been widely used, but this system has not been widely adopted in developing countries. This research was conducted in Indonesia which reflects the characteristics of a developing country with the largest population in Southeast Asia. The increasing number of chronic diseases and the COVID-19 pandemic encourage information technology innovation that supports disease treatment and prevention. This study aims to discuss the barriers and facilitators for the adoption of the PHR system in Indonesia and to design an integrated PHR system architecture and a prototype of the PHR mobile application (mPHR) with a design science research approach. The barriers and facilitators of PHR system adoption in Indonesia were explored through qualitative data collection by interviewing the Ministry of Health (2 respondents), BPJS Health (1 respondent), community health centers (puskesmas) (6 respondents), clinics (4 respondents), public or government hospitals (13 respondents), and private hospitals (8 respondents) with data analysis techniques using thematic analysis. The results of the analysis result in barriers and facilitators for the adoption of the PHR system consisting of technological, organizational, environmental, and individual factors. Then, to find requirements for an integrated PHR system, qualitative data collection with interviews was conducted with the Ministry of Health (2 respondents), BPJS Health (1 respondent), puskesmas (6 respondents), clinics (4 respondents), public or government hospitals (13 respondents), private hospitals (8 respondents), and health application vendors (3 respondents) as well as quantitatively by distributing questionnaires to Indonesian citizens aged 17 years and over. At this stage, qualitative data were analyzed by content analysis, while quantitative data were analyzed by descriptive statistics. The design of integrated PHR system architecture refers to The Open Group Architecture Framework (TOGAF) 9.2 which consists of architectural vision, business architecture, application architecture, data architecture, and technology architecture. Furthermore, the results of the architectural design become input for designing a high-fidelity prototype of mPHR. The functionalities developed in the mPHR prototype are priority functions defined in the architectural design. The evaluation of the architecture and prototype was carried out by interviewing 6 IT respondents or e-health experts from the Ministry of Health, academicians, health facilities, and health application vendors. This research is expected to provide a theoretical contribution to the study of PHR adoption in developing countries and to be a guide for health facilities, health regulators, and health application vendors to realize an integrated PHR in Indonesia."

"Perangkat lunak Enterprise University Information System (Euis) merupakan salah satu produk yang dimiliki oleh Pusat Ilmu Komputer Univesitas Indonesia yang disingkat Pusilkom UI. EUIS telah dikembangkan sejak tahun 2011 yang pada proses pengembangan awalnya menggunakan metodologi Pusilkom Agile Unified Process dan pada dua tahun terakhir ini dikembangkan dengan menngunakan kerangka kerja scrum, namun dalam proses pengembangannya terdapat masalah yaitu sprint goal tidak tercapai dan pengerjaan task melebihi dari estimasi waktu yang diberikan. Dengan adanya permasalahan tersebut yang secara tidak langsung dapat mempengaruhi jadwal pengerjaan produk EUIS secara keseluruhan sehingga dibutuhkan evaluasi yang diharapkan dapat mengatasi permasalahan yang ada dengan mengukur tingkat kematangan proses pengembangan. Dalam mengukur tingkat kematangan, data dikumpulkan melalui pelaksanaan Focus Group Discussion, studi dokumen, dan observasi. Data yang diperoleh kemudian dianalisis menggunakan perhitungan KPA Rating untuk mendapatkan tingkat kematangan. Hasil analisis tingkat kematangan akan didiskusikan dengan organisasi untuk menentukan tingkat kematangan yang ingin dicapai. Sasaran perbaikan dapat diidentifikasi dari praktik- praktik Scrum Maturity Model yang belum dicapai organisasi. Usulan perbaikan nantinya akan dihasilkan dari pemetaan sasaran perbaikan dengan best practices Scrum. Pada hasil penelitian menunjukkan bahwa tingkat kematangan scrum pada organisasi saat ini telah mencapai scrum maturity level 2 dan ingin mencapai scrum maturity leve 3.

---

Enterprise University Information System (Euis) software is a product owned by the Pusat Ilmu Komputer Univesitas Indonesia, abbreviated as Pusilkom UI. EUIS has been developed since 2011, which in the initial development used the methodology of the Pusilkom Agile Unified Process and in the last two years it was generated using the Scrum framework. Still, in the development process there were problems namely the sprint goal was not achieved and the task execution exceeded the estimated time given. With these problems which can indirectly affect the overall work schedule of EUIS products, an evaluation is expected to be able to overcome the existing challenges by measuring the level of maturity of the development process. In measuring the level of maturity, data is collected through the implementation of Focus Group Discussions, document studies, and observations. The data obtained is then analyzed using the KPA Rating calculation to get the level of maturity. The results of the maturity level analysis will be discussed with the organization to determine the level of maturity to be achieved. The improvement target can be identified from the Scrum Maturity Model practices that the organization has not yet reached. The proposed improvements will later be generated from mapping improvement targets with Scrum best practices. The results showed that the Scrum Maturity level in the organization has now reached Scrum Maturity Level 2 and wants to reach Scrum Maturity Level 3."