Indra Kharisma Raharjana

Dr. Indra Kharisma Raharjana

orcid

Research Focus & Metrics

Academic Career Length

12Years (2015-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
2 April 2021 in IEEE Access
Verified
Journal Article
Open access
Indra Kharisma RaharjanaIndra Kharisma Raharjana
Indra Kharisma Raharjana
DSDaniel Siahaan
Daniel Siahaan
CFChastine Fatichah
Chastine Fatichah
Context: User stories have been widely accepted as artifacts to capture the user requirements in agile software development. They are short pieces of texts in a semi-structured format that express requirements. Natural language processing (NLP) techniques offer a potential advantage in user story applications. Objective: Conduct a systematic literature review to capture the current state-of-the-art of NLP research on user stories. Method: The search strategy is used to obtain relevant papers from SCOPUS, ScienceDirect, IEEE Xplore, ACM Digital Library, SpringerLink, and Google Scholar. Inclusion and exclusion criteria are applied to filter the search results. We also use the forward and backward snowballing techniques to obtain more comprehensive results. Results: The search results identified 718 papers published between January 2009 to December 2020. After applying the inclusion/exclusion criteria and the snowballing technique, we identified 38 primary studies that discuss NLP techniques in user stories. Most studies used NLP techniques to extract aspects of who, what, and why from user stories. The purpose of NLP studies in user stories is broad, ranging from discovering defects, generating software artifacts, identifying the key abstraction of user stories, and tracing links between model and user stories. Conclusion: NLP can help system analysts manage user stories. Implementing NLP in user stories has many opportunities and challenges. Considering the exploration of NLP techniques and rigorous evaluation methods is required to obtain quality research. As with NLP research in general, the ability to understand a sentence’s context continues to be a challenge.

1 July 2019
Verified
Conference Paper
Closed access
Indra Kharisma RaharjanaIndra Kharisma Raharjana
Indra Kharisma Raharjana
DSDaniel Siahaan
Daniel Siahaan
CFChastine Fatichah
Chastine Fatichah
To specify good requirements, system analysts need to understand the domain knowledge of the system. There are several techniques in requirements elicitation to improve domain knowledge understanding, such as user interviews, questioners, document analysis, and brainstorming. Most of these techniques require profound stakeholder involvement. However, not all software projects can do this task due to limited time or availability of stakeholders. In agile software development, the user story is the de facto standard used for capturing and writing functional requirements. The user story is an appropriate format and easy to understand for writing the results of requirements elicitation. This study purposes a conceptual model to extract user story from online news for improving domain knowledge understanding. The information in the online news contained lesson learned related to certain events. This information may improve the functionality of the software products. The user story consists of three aspects, namely: who, what, and why. Aspect of who represents the role or user, aspect of what shows the purpose or feature, while the aspect of why explains the reason. This format can summarize the lessons learned in the news. Our experimental results indicate that this conceptual model can extract user story from online news. The model manages to extract 105 user stories from 92 aspects of what/why candidate and 109 aspects of who candidate.

10 March 2023 in Information and Software Technology
Verified
Journal Article
Closed access
DSDaniel Siahaan
Daniel Siahaan
Indra Kharisma RaharjanaIndra Kharisma Raharjana
Indra Kharisma Raharjana
CFChastine Fatichah
Chastine Fatichah

1 July 2015 in JUTI: Jurnal Ilmiah Teknologi Informasi
Verified
Journal Article
Open access
PDF file
Indra Kharisma RaharjanaIndra Kharisma Raharjana
Indra Kharisma Raharjana
Army JustitiaArmy Justitia
Army Justitia
Konsistensi desain sequence diagram dengan implementasi sering menjadi masalah dalam pembangunan perangkat lunak, penelitian ini akan menerapkan hasil reverse engineering sequence diagram dari aplikasi yang telah ada sebagai model dasar untuk membangun perangkat lunak sehingga konsistensi desain sequence diagram bisa dijaga. Dalam penelitian ini model sequence diagram tersebut dibangun dengan cara mengklasifikasikan interaksi antara pengguna dengan perangkat lunak di aplikasi basis data pada smartphone. Untuk membuat model UML Sequence Diagram, langkah pertama adalah memilih dataset berupa source code aplikasi contoh di Blackberry 10 dan kemudian memahami fungsional aplikasi tersebut. Langkah selanjutnya adalah melakukan reverse engineering dari source code tersebut berdasarkan fitur yang telah didefinisikan sebelumnya. Lalu dilakukan pembangunan model UML sequence diagram berdasarkan kesamaan dan pengelompokan pola pada hasil reverse engineering. Langkah terakhir adalah melakukan evaluasi terhadap model UML sequence diagram dengan cara menggunakannya pada pembangunan aplikasi baru, mengukur tingkat konsistensi desain sequence diagram serta mengambil pengetahunan dari penerapan studi kasus. Berdasarkan hasil penelitian, model sequence diagram yang didapatkan dari proses reverse engineering bisa menjaga konsistensi antara desain sequence diagram dengan implementasi pada pembangunan perangkat lunak.

27 April 2020 in Journal of Information Systems Engineering and Business Intelligence
Verified
Journal Article
Open access
PDF file
Indra Kharisma RaharjanaIndra Kharisma Raharjana
Indra Kharisma Raharjana
FHFadel Harris
Fadel Harris
Army JustitiaArmy Justitia
Army Justitia
Background: Testing using Behavior-Driven Development (BDD) techniques is one of the practices of Agile software development. This technique composes a test-case based on a use case scenario, for web application acceptance tests.Objective: In this study, we developed a tool to generate test case codes from BDD scenario definitions to help and facilitate practitioners to conduct testing.Methods: The generated test case code is made according to the codeception framework format so that it can be directly executed by the tester. The procedure is performed as follows: map the correlation of the language used in BDD (gherkin language) and the code syntax of the test code in the codeception framework, designed the GUIs in such a way that users can easily transform the Use Case Scenario, built the tool so that it can generate test cases codes. Evaluation is done by gathering respondents; ask to run the application and gathering feedback from respondents.Results: This tool can generate a codeception test-case file based on the BDD scenario. Generated test cases can be directly used on codeception tools. The results of the evaluation show that the tools can help entry-level programmers in developing automated tests.Conclusion: The tool can help user especially entry-level programmers to generate BDD test-case and make easy for the users for testing the web applications.

28 April 2023 in Journal of Information Systems Engineering and Business Intelligence
Verified
Journal Article
Open access
PDF file
HAHalim Wildan Awalurahman
Halim Wildan Awalurahman
IWIbrahim Hafizhan Witsqa
Ibrahim Hafizhan Witsqa
Indra Kharisma RaharjanaIndra Kharisma Raharjana
Indra Kharisma Raharjana
ABAhmad Hoirul Basori
Ahmad Hoirul Basori
Background: Software testing and software security have become one of the most important parts of an application. Many studies have explored each of these topics but there is a gap wherein the relation of software security and software testing in general has not been explored. Objective: This study aims to conduct a systematic literature review to capture the current state-of-the-art in software testing related to security. Methods: The search strategy obtains relevant papers from IEEE Xplore and ScienceDirect. The results of the search are filtered by applying inclusion and exclusion criteria. Results: The search results identified 50 papers. After applying the inclusion/exclusion criteria, we identified 15 primary studies that discuss software security and software testing. We found approaches, aspects, references, and domains that are used in software security and software testing. Conclusion: We found certain approach, aspect, references, and domain are used more often in software security testing Keywords: Software security, Software testing, Security testing approach, Security threats, Systematic literature review