Article Per Year (5 Year)
p-Index From 2021 - 2026
0.947
P-Index
This Author published in this journals
All Journal Seminar Nasional Aplikasi Teknologi Informasi (SNATI) Semantik Sinkron : Jurnal dan Penelitian Teknik Informatika Jurnal RESTI (Rekayasa Sistem dan Teknologi Informasi) Jurnal ULTIMATICS Jurnal Locus Penelitian dan Pengabdian Jurnal Sistem Informasi The Indonesian Journal of Computer Science
Eko K. Budiardjo
Fakultas Ilmu Komputer, Universitas Indonesia, Depok
Aerospace Engineering Automotive Engineering Computer Science & IT Control & Systems Engineering Decision Sciences, Operations Research & Management Electrical & Electronics Engineering Engineering Mathematics Other

Published : 10 Documents Claim Missing Document
Claim Missing Document
Check
Articles

Found 10 Documents
Search

 1 
ONTOLOGI PADA METODE REQUIREMENTS RECOVERY DALAM PROSES REVERSE ENGINEERING Elviawaty Muisa Zamzami; Eko Kuswardono Budiardjo
Semantik Vol 1, No 1 (2011): Prosiding Semantik 2011
Publisher : Semantik

Show Abstract | Download Original | Original Source | Check in Google Scholar | Full PDF (403.822 KB)

Abstract

Piranti lunak kerap mengalami perubahan, antara lain disebabkan perubahan bisnis organisasi. Akibatnya, peranti lunak tidak mampu lagi mendukung organisasi sehingga harus dilakukan reengineering terhadapnya. Software reengineering didukung antara lain oleh riset reverse engineering. Riset reverse engineering saat ini lebih terfokus pada pengembangan software tools dan perolehan kembali model fisik dan struktur lojik dalam bentuk model-model dari legacy system [1] . Namun, riset untuk requirements recovery melalui proses reverse engineering masih relatif minim. Disisi lain, requirements sangat penting bagi keberhasilan software reengineering. Dengan demikian, terdapat kepentingan melakukan riset reverse engineering untuk requirements recovery dari peranti lunak yang ada (existing software). Requirements recovery dari peranti lunak dapat memastikan pemahaman lebih baik dari apa yang redundan, apa yangharus dipertahankan, dan apa yang dapat digunakan kembali [1]. Requirements yang diperoleh dapat digunakan pada forward engineering sebagai bagian dari reengineering ataupun menyusun ulang dokumen existing requirements. Pada paper ini, requirements recovery bersumber dari end-to-end interaction antara user dan sistem komputer. Dari existing software, diidentifikasi user dan fitur peranti lunak. Selanjutnyadiobservasi end-to-end interaction yang terjadi antara user dan sistem komputer. Hasil identifikasi dan observasi tersebut digunakan untuk membangun ontologi. Ontologi dapat merepresentasikan pengetahuan tentang existing software yang menyiratkan requirements.Kata kunci : Software Reengineering, Reverse Engineering, Requirements Recovery, End-to-endInteraction, Ontologi
KLASIFIKASI METODE GOAL ORIENTED REQUIREMENT ENGINEERING (GORE) DAN KEMUNGKINANNYA UNTUK MENGEMBANGKAN APLIKASI KEPEMERINTAHAN Imam M. Shofi; Eko K. Budiardjo
Semantik Vol 1, No 1 (2011): Prosiding Semantik 2011
Publisher : Semantik

Show Abstract | Download Original | Original Source | Check in Google Scholar | Full PDF (797.238 KB)

Abstract

Ukuran keberhasilan suatu sistem software ditentukan seberapa besar sistem software itu memenuhi/sesuai dengan tujuannya. Requirement Engineering (RE) merupakan proses untuk menemukan tujuan tersebut. Salah satu pendekatan dalam RE yang saat ini berkembang sangat pesat adalah Goal OrientedRequirements Engineering (GORE), karena GORE melengkapi kekurangan pada pendekatan tradisional yang lebih menekankan pada pemodelan low-levelnya, dimana GORE pada high levelnya juga. Goal adalah kondisi/keadaan yang ingin dicapai oleh pemangku kepentingan (stakeholder) suatuperusahaan/organisasi/sistem. Terdapat 3 level/tingkatan dari goal, yaitu: highest level, high level, dan low level. Sedangkan cara/teknik mengidentifikasi goal ada beberapa, diantara yang disarankan adalah mengekstrak dari pernyataan-pernyataan resmi (intentional statements) berdasarkan: transkrip interview,kebijakan perusahaan (enterprise policies), visi dan misi perusahaan (enterprise mission statements), sasaran perusahaan (enterprise goals), diagram workflow, dan skenario yang ditulis stakeholder. Sedikitnya telah terdapat 17 metode dalam GORE, diantaranya juga ada metode yang merupakangabungan maupun pengembangan dari metode-metode yang lain. Dari hasil klasifikasi metode GORE yang telah dilakukan terhadap aktifitas REnya, terlihat bahwa masing-masing metode mempunyai kelebihan dan kekurangan serta titik berat tersendiri. Walaupun tidak dinyatakan secara implisitmendukung strategi e-Government, sebagian besar instansi pemerintah telah mempunyai dokumen resmi/peraturan baku (dalam bentuk peraturan pemerintah) yang berisi visi, misi, tugas pokok dan fungsi, maupun peraturan-peraturan lainnya yang lebih detil. Sehingga GORE sangat cocok untukmengembangkan Aplikasi Kemerintahan. Aplikasi kepemerintahan juga mempunyai karakteristik khususjika dibandingkan dengan aplikasi enterprise/bisnis pada umumnya, yaitu pada goal/sasaran/orientasinya. Kalau aplikasi bisnis lebih berorientasi pada profit/keuntungan sedangkan service/pelayanan merupakan pendukungnya, maka aplikasi kepemerintahan lebih berorientasi pada pelayanan sedangkan keuntungan hanya sebagai pendukung. Untuk itu, perlu dikembangkannya metode GORE untuk mengembangkanaplikasi kepemerintahan.Kata kunci : Requirement Engineering (RE), Goal Oriented Requirement Engineering (GORE), AplikasiKepemerintahan
Pemodelan Bisnis dalam Dunia Otomotif untuk Mengatasi Kesenjangan antara Pengguna dan Pengembang Aplikasi Supply Chain Management (SCM) Eko K. Budiardjo; Anton W. Pramono
Seminar Nasional Aplikasi Teknologi Informasi (SNATI) 2006
Publisher : Jurusan Teknik Informatika, Fakultas Teknologi Industri, Universitas Islam Indonesia

Show Abstract | Download Original | Original Source | Check in Google Scholar

Abstract

Aplikasi SCM melibatkan beragam pengguna, dengan tingkat literasi komputer yang sangat beragam, menyulitkan dalam menyusun prasyarat dan spesikasi perangkat lunak. Rekayasa aplikasi SCM dituntut untuk menghasilkan yang berkualitas, tepat waktu, tepat biaya, dan memenuhi harapan pengguna yang beragam. Terjadilah kesenjangan yang terlihat dari banyaknya kegagalan proyek pengembangan aplikasi SCM terlambat dan tidak sesuai dengan keinginan penggunanya yang disebabkan oleh kegagalan dalam menyusun prasyarat dan spesifikasinya. Pada makalah ini membahas pengentasan kesenjangan melalui pemodelan bisnis untuk menghindari kegagalan tersebut.Kata kunci: Supply Chain Management (SCM), Pemodelan Bisnis (Business Modeling), Unified Modeling Language (UML), Unified Process (UP).
Penerapan ZEF Framework untuk Aplikasi E-Government: Pendekatan Sinergi BPM (Business Process Model) dan SOA (Service Oriented Architecture) Ahmad Nurul Fajar; Eko K. Budiardjo; Zainal A. Hasibuan
Seminar Nasional Aplikasi Teknologi Informasi (SNATI) 2013
Publisher : Jurusan Teknik Informatika, Fakultas Teknologi Industri, Universitas Islam Indonesia

Show Abstract | Download Original | Original Source | Check in Google Scholar

Abstract

Perubahan regulasi seringkali perlu diikuti dengan mengubah sistem informasi / perangkat lunak aplikasi terpasang. Jika perubahan ini tidak didukung oleh environment perangkat lunak yang fleksibel, dapat berpengaruh terhadap biaya penyesuaian aplikasi. Kadangkala, hasil perubahan yang sudah diimplementasikan tidak sesuai dengan kebutuhan. Perubahan pada common application seringkali menyebabkan aplikasi spesifik tidak bisa digunakan. Sementara, jika ada perubahan pada aplikasi spesifik, seringkali tidak sesuai dengan common application. Hal ini disebabkan karena belum adanya pendekatan yang mensinergikan BPM dan SOA dengan memperhatikan aspek commonality dan variability pada level fitur. Untuk mengantisipasi perubahan regulasi, dapat difasilitasi oleh Zhuma’s E-Government Framework (ZEF Framework). ZEF dapat menjembatani bisnis dan IT karena dapat mengidentifikasi, mengklasifikasi dan mengelola commonality dan variability fitur berdasarkan regulasi. Penerapan ZEF Framework pada pemerintah pusat dan pemerintah daerah dapat mengurangi dampak biaya akibat perubahan regulasi terhadap aplikasi terpasang. Ujicoba penerapan ZEF Framework dilakukan pada domain sistem budgeting dan keuangan daerah.
E-Business Software Product Line Methodology Based on SMEs Characteristics Ni Made Satvika Iswari; Eko Kuswardono Budiardjo; Zainal Arifin Hasibuan
ULTIMATICS Vol 14 No 1 (2022): Ultimatics : Jurnal Teknik Informatika
Publisher : Faculty of Engineering and Informatics, Universitas Multimedia Nusantara

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.31937/ti.v14i1.2642

Abstract

The growth of Small and Medium Enterprises (SMEs) will certainly have a positive influence on economic development in a country. However, many SMEs struggle to survive, grow, and show limited productivity. It was recorded that there were around 63.9% of SMEs in Indonesia whose turnover had decreased by more than 30% during the COVID-19 pandemic. Among the factors that cause the low survival rate of SMEs, a factor that is considered critical is the lack of success in the use of e-business. The use of e-business by SMEs is not a one-size-fits-all solution, because SMEs have various characteristics. In this study, an E-Business Software Product Line Methodology based on SMEs characteristics was proposed using Software Product Line Engineering (SPLE) approach. In general, the proposed methodology was sufficient to describe the aspects needed in building a software development methodology. Aspects that had not been described were those related to software project management. The proposed methodology is useful for building an e-business application platform that can be customized based on SMEs characteristics.
BRIDGING GAP OF USER GOAL REQUIREMENTS AND IMPLEMENTED APPLICATIONS BASED ON FEATURE MODEL Ahmad Nurul Fajar; Eko K. Budiardjo; Zainal A. Hasibuan
Jurnal Sistem Informasi Vol. 8 No. 2 (2012): Jurnal Sistem Informasi (Journal of Information System)
Publisher : Faculty of Computer Science Universitas Indonesia

Show Abstract | Download Original | Original Source | Check in Google Scholar | Full PDF (636.263 KB) | DOI: 10.21609/jsi.v8i2.332

Abstract

Feature modeling is a conceptual thinking for identifying and classification feature in order for support software product lines. However, there are lack of the user goal requirements. It related with a technique for managing of features commonalities and variability. It has a hierarchy of features with variability and the purpose is to organize features. In practice of implemented applications, the feature model development lack of goal user requirement. The goal of user requirement in Indonesian government has described in document regulations. It should be a fundamental concern to develop e-government applications. However, In order to capture degree of software feature importance, some of features compared with implemented e-government applications. We have extracted some of features which can be compared with the implemented e-government applications. Our technique is extracted are derived from document regulations to business process model and feature model also. We Choose SIPKD and SIMDA applications which has implemented in Indonesian local government which has variation from one and another. We use extended AHP and S-AHP to find the prioritization of software features. The results are 80 features in SIPKD and 90 features in SIMDA. There are 65 features common and 25 variant features .This make un-optimization usage applications.
Problems in The Adoption of Agile-Scrum Software Development Process in Small Organization: A Systematic Literature Review Putrianasari, Rahmawati; Budiardjo, Eko Kuswardono; Mahatma, Kodrat; Raharjo, Teguh
Sinkron : jurnal dan penelitian teknik informatika Vol. 8 No. 1 (2024): Articles Research Volume 8 Issue 1, January 2024
Publisher : Politeknik Ganesha Medan

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.33395/sinkron.v9i1.13271

Abstract

Agile methods are becoming increasingly popular in modern corporate strategies, which represents a paradigm change in project management techniques. The concept of pragmatic agility has become essential for enterprises to manage the complexities of ever-changing contexts. However, some organizations—especially small ones with limited resources—face unforeseen difficulties while implementing Agile-Scrum software development. In order to clarify the challenges small businesses, encounter throughout this adoption process, this study combines ideas from fifteen studies into a thorough and systematic analysis of the literature. The issues that have been discovered may be categorized into four primary areas: technology, people, process, and organization, and agile techniques. Organizations are able to anticipate obstacles by using a comprehensive understanding provided by the methodical examination and classification of situations. This proactive approach is essential to preventing unfavorable outcomes, as those seen in the past when implementation errors were made worse by culture problems, insufficient support from upper management, and waning consumer cooperation. This research provides small firms with a navigational aid by synthesizing lessons from the literature, enabling them to plan an Agile-Scrum adoption process that is more smoothly executed. Organizations may enhance their preparation, protect themselves from frequent traps, and ultimately maximize the transformative potential of Agile techniques in their developmental undertakings by adopting these insights.
Recommendation for Scrum-Based Software Development Process with Scrum at Scale: A Case Study of Software House XYZ Ahmad Jalaluddin; Eko K. Budiardjo; Kodrat Mahatma
Jurnal RESTI (Rekayasa Sistem dan Teknologi Informasi) Vol 8 No 3 (2024): June 2024
Publisher : Ikatan Ahli Informatika Indonesia (IAII)

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.29207/resti.v8i3.5646

Abstract

Software House XYZ employs Scrum as one of its software development processes. However, the company faces several challenges in the implementation of Scrum, leading to delays in its product releases. Two specific problems are the control of a large-scale Scrum team and the management of team commitments. To address these issues, the Scrum at Scale framework has been chosen as a solution. Before implementing Scrum at Scale, an assessment of the current Scrum maturity level at Software House XYZ is deemed necessary. The Scrum Maturity Model, adapted to the Scrum Guide 2020, is selected as the method to evaluate how effectively the company is implementing Scrum. A questionnaire comprising 81 practices was distributed to development teams, with 10 valid responses collected. Based on the assessment using the Scrum Maturity Model, the current Scrum implementation maturity at Software House XYZ is rated at level 1, Initial. A total of 61 practices are proposed for improvement in the Scrum process. Scrum at Scale can be implemented once the suggested Scrum process improvements have been made. These recommendations are structured following the framework outlined in the Scrum at Scale Guide 2022. The validation of the Scrum-at-Scale recommendations was conducted by us through interviews with representatives from Software House XYZ. From the validation results, the company expresses interest in trying to implement Scrum at Scale. However, the company agrees to enhance the existing Scrum process within the organization before fully adopting Scrum at Scale.
Transforming Public Sector Auditing from Tradition to Agility with Scrum: A Case for the Indonesian Public Sector Triasmoro, Benidiktus Bambang; Mahatma, Kodrat; Budiardjo, Eko K.
Jurnal Locus Penelitian dan Pengabdian Vol. 4 No. 9 (2025): : JURNAL LOCUS: Penelitian dan Pengabdian
Publisher : Riviera Publishing

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.58344/locus.v4i9.4769

Abstract

The conventional audit methodology in the public sector faces escalating challenges in addressing the increasing complexity of governmental functions and the demand for prompt, relevant audit results. This study addresses the critical research problem of enhancing audit efficiency and stakeholder engagement in public sector auditing while maintaining professional standards and regulatory compliance. The research objective is to develop a novel framework for implementing Agile methodology, specifically Scrum, in BPK’s public sector audit process. The study employs a qualitative research methodology, including a comprehensive literature review, document analysis, interviews with thirteen key stakeholders—comprising senior auditors and Agile practitioners—and a limited pilot implementation. The research identifies eight critical areas for framework development and establishes Quality Control Integration Points (QCIP) to ensure continuous quality monitoring while preserving agile flexibility. The findings demonstrate that Agile principles can be successfully adapted to public sector auditing through a modified Scrum framework that incorporates iterative planning, daily coordination, and consistent stakeholder feedback. The study provides a structured implementation roadmap spanning 3 to 18 months and addresses varying levels of stakeholder impact. The developed framework enhances audit efficiency and effectiveness while upholding essential compliance standards. This research contributes both to the theoretical understanding and practical application of Agile methodology in public sector auditing, establishing a foundation for future adoption in similar institutions.
Feature Model for Pet Health Application Domain using Feature Oriented Domain Analysis Satoh, Ajeng Nurhidayati A Darsan; Budiardjo, Eko K.; Mahatma, Kodrat
The Indonesian Journal of Computer Science Vol. 13 No. 4 (2024): The Indonesian Journal of Computer Science
Publisher : AI Society & STMIK Indonesia

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.33022/ijcs.v13i4.4296

Abstract

According to a survey of Indonesian pet healthcare service users, only 19% of pet health applications are used since the functions offered by the applications are insufficient to meet the needs of the users. Developing feature model for the pet health application domain is the goal of this research. Using a mixed-methods approach, this research examined nine pet health apps which are available on Google Play and the App Store, observed 30 pet health service consumers through surveys using purposive sampling, and conducted document analyses. The Feature Oriented Domain Analysis (FODA) approach is applied within the Software Product Line Engineering (SPLE) framework. The result of this research is a pet health application domain feature model consisting of five non-functional requirements and 45 functional requirements. With an average assessment score of 96%, domain experts have determined that the feature model implementation in this study is in line with user needs.
Co-Authors Ahmad Jalaluddin Ahmad Nurul Fajar Ahmad Nurul Fajar Anton W. Pramono Elviawaty Muisa Zamzami Imam M. Shofi Kodrat Mahatma Mahatma, Kodrat Ni Made Satvika Iswari Putrianasari, Rahmawati Raharjo, Teguh Satoh, Ajeng Nurhidayati A Darsan Triasmoro, Benidiktus Bambang Zainal A. Hasibuan Zainal A. Hasibuan Zainal Arifin Hasibuan