Design and Development of the Hello Engineer Android and Web-Based Construction Consultation Application

Ahmad Yudi; Siti Rahma; Arief Ichwani; Ahmad Arif Apriadi

doi:10.15408/jti.v19i2.53883

Authors

Ahmad Yudi Teknik Sipil, Fakultas Teknik, Institut Teknologi Sumatera, Indonesia
Siti Rahma Teknik Sipil, Fakultas Teknik, Institut Teknologi Sumatera, Indonesia
Arief Ichwani Teknik Informatika, Fakultas Teknik, Institut Teknologi Sumatera, Indonesia
Ahmad Arif Apriadi Department of Civil Engineering, Faculty of Engineering, Chulalongkorn University, Bangkok, Thailand

DOI:

https://doi.org/10.15408/jti.v19i2.53883

Keywords:

API, civil engineering consultant, android application, website

Abstract

Access to qualified construction experts is often constrained by location, scheduling, and fragmented service channels. This study designed and developed Hello Engineer, an integrated construction-consultation platform consisting of a web-based administrative application and two Android client applications for clients and consultants. The system supports consultant registration and verification, expertise-based discovery, chat consultation, appointment scheduling, laboratory-test ordering, location-based services, ratings, and payment processing. Development followed the Dynamic Systems Development Method because the project required iterative prototyping, continuous product-owner involvement, and priority-based adjustment of features within fixed time and resource constraints. Functional black-box testing covered nine scenarios across authentication, account management, consultant selection, appointment booking, chat consultation, laboratory-test ordering, and logout. All nine scenarios passed, producing a functional-test success rate of 100%. The result demonstrates the technical feasibility of integrating previously fragmented construction advisory services in one role-based mobile and web architecture. The evaluation is limited to functional verification; standardized user-based usability, performance, security, and scalability tests remain necessary before production deployment.

References

[1] Oesterreich TD, Teuteberg F. Understanding the implications of digitisation and automation in the context of Industry 4.0: A triangulation approach and elements of a research agenda for the construction industry. Computers in Industry. 2016;83:121–139.

[2] Alaloul WS, Liew MS, Zawawi NAWA, et al. Industrial Revolution 4.0 in the construction industry: Challenges and opportunities for stakeholders. Ain Shams Engineering Journal. 2020;11(1):225–230.

[3] Maskuriy R, Selamat A, Ali KN, et al. Industry 4.0 for the construction industry: Review of management perspective. Economies. 2019;7(3):68.

[4] Turk Z. Ten questions concerning building information modelling. Building and Environment. 2016;107:274–284.

[5] Oraee M, Hossein Rezazadeh Azar E, Golparvar-Fard M, et al. Collaboration in BIM-based construction networks: A bibliometric-qualitative literature review. International Journal of Project Management. 2017;35(7):1288–1301.

[6] Succar B. Building information modelling framework: A research and delivery foundation for industry stakeholders. Automation in Construction. 2009;18(3):357–375.

[7] Sacks R, Eastman C, Lee G, et al. BIM Handbook: A Guide to Building Information Modeling for Owners, Designers, Engineers, Contractors, and Facility Managers. 3rd ed. Wiley; 2018.

[8] Sawhney A, Riley M, Irizarry J, editors. Construction 4.0: An Innovation Platform for the Built Environment. Routledge; 2020.

[9] Zulfikar RA, Supianto AA. Rancang Bangun Aplikasi Antrian Poliklinik Berbasis Mobile. J Teknol Inf dan Ilmu Komputer. 2018;5(3).

[10] DSDM Consortium. The DSDM Agile Project Framework. DSDM Consortium; 2014.

[11] Beck K, Beedle M, van Bennekum A, et al. Manifesto for Agile Software Development [Internet]. 2001. Available from: https://agilemanifesto.org/.

[12] Conboy K. Agility from first principles: Reconstructing the concept of agility in information systems development. Information Systems Research. 2009;20(3):329–354.

[13] Highsmith J, Cockburn A. Agile software development: The business of innovation. Computer. 2001;34(9):120–127.

[14] Abrahamsson P, Salo O, Ronkainen J, et al. Agile Software Development Methods: Review and Analysis. VTT Technical Research Centre of Finland; 2002. Report No.: 478. .

[15] ISO/IEC/IEEE. ISO/IEC/IEEE 29148:2018 Systems and Software Engineering: Life Cycle Processes: Requirements Engineering. International Organization for Standardization; 2018.

[16] ISO/IEC. ISO/IEC 25010:2011 Systems and Software Engineering: Systems and Software Quality Requirements and Evaluation: System and Software Quality Models. International Organization for Standardization; 2011.

[17] Bass L, Clements P, Kazman R. Software Architecture in Practice. 4th ed. Addison-Wesley; 2021.

[18] Fielding RT. Architectural Styles and the Design of Network-Based Software Architectures [Doctoral dissertation]. University of California, Irvine; 2000.

[19] Fielding R, Nottingham M, Reschke J. HTTP Semantics. Internet Engineering Task Force; 2022. Report No.: RFC 9110. .

[20] Schiller J, Voisard A, editors. Location-Based Services. Morgan Kaufmann; 2004.

[21] Hardt D. The OAuth 2.0 Authorization Framework. Internet Engineering Task Force; 2012. Report No.: RFC 6749. .

[22] OWASP Foundation. Application Security Verification Standard 4.0.3. OWASP Foundation; 2021.

[23] Grassi PA, Garcia ME, Fenton JL. Digital Identity Guidelines: Authentication and Lifecycle Management. National Institute of Standards and Technology; 2017. Report No.: NIST SP 800-63B. .

[24] PCI Security Standards Council. Payment Card Industry Data Security Standard: Requirements and Testing Procedures, Version 4.0.1. PCI Security Standards Council; 2024.

[25] ISO. ISO 9241-11:2018 Ergonomics of