Deki Satria, Qilbaaini Effendi Muftikhali, Dea Wemona Rahma, Dimas Bayu Arkaan, Zain Ammar Falih

RE-DESIGNING JAKLINGKO APPS UI/UX USING AGILE REQUIREMENT ENGINEERING APPROACH

Introduction

Re-designing jaklingko apps ui/ux using agile requirement engineering approach. Redesigning Jakarta's Jaklingko public transport app UI/UX using an agile requirement engineering approach. Improves user experience, addressing pain points with prototyping & SUS.

Abstract

Public transportation has become a staple in a lot of countries, including Indonesia. As the largest city in Indonesia, is trying to accommodate the dense traffic in Jakarta by implementing various types of public transportation, one of which is the Bus Rapid Transit (BRT). BRT has its own application called Jaklingko, which the commuter uses to gain information about the BRT. Unfortunately, this application has bad reviews in the app store. This research tried to redesign the UI/UX of this application using prototyping and the System Usability Scale (SUS) as tools for agile requirement engineering tools. In Agile requirements usually conducted the same as traditional which is using interview or observation. But, using this method proved to be time consuming. Therefore this research tried to incorporate prototyping and SUS into the requirements gathering process. After the requirements are collected, the next phase is redesigning the application based on the gathered requirements. From the research conducted, the main pain point of the responses is how much information is given in the apps. This research also found that prototyping and SUS could be used to gather requirements, but they will depend heavily on the test case being used. Therefore, it is not suitable for stand alone gathering tools but good as a confirmation tool

Review

This paper addresses a highly relevant and practical problem: the need to improve the user experience of the Jaklingko public transportation application in Jakarta, Indonesia. Given the city's dense traffic and reliance on services like Bus Rapid Transit (BRT), an effective and user-friendly application is crucial for commuters. The authors clearly establish the motivation for their research by citing poor app store reviews, indicating significant usability challenges with the current Jaklingko application. The proposed solution involves a redesign of the UI/UX, which is a commendable and necessary step towards enhancing public transport accessibility and satisfaction. The research distinguishes itself by exploring an agile requirement engineering approach that incorporates prototyping and the System Usability Scale (SUS) as alternatives to traditional, time-consuming methods like interviews and observations. This is an interesting methodological choice, attempting to streamline the requirements gathering process. The study successfully identified a critical pain point for users: the overwhelming amount of information presented within the application. This finding provides a clear direction for the subsequent redesign efforts. However, the paper's most significant methodological insight comes from its critical evaluation of the chosen tools: while prototyping and SUS can contribute to requirements gathering, their effectiveness heavily depends on the test cases employed, suggesting they are better suited as confirmation tools rather than standalone methods. The paper offers a valuable dual contribution. Practically, it provides a data-driven basis for improving a vital public transportation application, directly addressing user frustrations. Methodologically, it contributes to the discourse on agile requirement engineering by empirically testing and critically assessing the utility of prototyping and SUS in requirements gathering. The conclusion that these tools are not suitable for standalone use but are effective as confirmation tools is a crucial finding, tempering the initial promise of a purely agile, time-saving approach. This nuanced result is important for practitioners considering similar methodologies. Future work might explore optimal ways to integrate these tools within a broader requirements gathering strategy or investigate specific test case characteristics that maximize their utility.

Full Text

Comments

You need to be logged in to post a comment.