Comparison Towards Different Methods of Software Debugging

Akwan Cakra Tajimalela, Ramandha Putra Suryahadi, Rizka Alfadilla, Indira Syawanodya, Iqbal Tawakal

Abstract


To ensure that software works as expected, debugging is essential. This article discusses several types of debugging, focusing on Visual Studio Code Debugger, print statement debugging, and static code analysis. Each method is demonstrated through a simple yet comprehensive program that determines whether a selected number is a prime number. We conclude that the Visual Studio Code Debugger offers powerful features but requires prior experience with Visual Studio Code. Print statement debugging is straightforward but can become cumbersome in more complex programs. Static code analysis, particularly with ESLint, does not directly uncover "bugs" in the traditional sense but evaluates code style, security, and good programming practices. Combining these three methods can yield optimal results in the debugging and inspection process, depending on the specific needs and context of the project.

Keywords


Software; Debugging; Visual Studio Code; Programming; Coding

References


Anderson, P., & Teitelbaum, T. (2001, July). Software inspection using codesurfer. In Workshop on Inspection in Software Engineering (CAV 2001).

Azhar, N. F., & Rochimah, S. (2016). Memprediksi Waktu Memperbaiki Bug dari Laporan Bug Menggunakan Klasifikasi Random Forest. Jurnal Sistem dan Informatika (JSI), 11(1), 156-164.

Campos, J., Riboira, A., Perez, A., & Abreu, R. (2012, September). Gzoltar: an eclipse plug-in for testing and debugging. In Proceedings of the 27th IEEE/ACM international conference on automated software engineering (pp. 378-381).

Fagan, M. E. (1999). Design and code inspections to reduce errors in program development. IBM Systems Journal, 38(2.3), 258-287.

Hadiprakoso, R. B. (2020). Rekayasa Perangkat Lunak. Rbh.

Kernighan, B. W., & Pike, R. (1999). The Practice of Programming (Revised Edition). Addison-Wesley.

Laitenberger, O. (2002). A survey of software inspection technologies. In Handbook of Software Engineering and Knowledge Engineering: Volume II: Emerging Technologies (pp. 517-555).

Liang, S., & Hartanto, Y. (2022). Implementasi Bug Tracking System dengan Metodologi Scrum dan Algoritma Cosine Similarity. JURIKOM (Jurnal Riset Komputer), 9(1), 24-32.

Martin, R. C. (2008). Clean Code: A Handbook of Agile Software Craftsmanship. Prentice Hall.

McConnell, S. (2004). Code Complete (2nd Edition). Microsoft Press.

Srivastva, S., & Dhir, S. (2017, April). Debugging approaches on various software processing levels. In 2017 International conference of Electronics, Communication and Aerospace Technology (ICECA) (Vol. 2, pp. 302-306). IEEE.

Strauss, D. (2023). Debugging Your Code. In: Getting Started with Visual Studio 2022. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-8922-8_3

Wahid, N. A., Sarwo, S., & Setiawan, A. W. (2015). Implementasi Dan Analisa Jaringan Saraf Tiruan Dengan Feature Normalization Dan Principal Component Analysis Untuk Digit Classifier. Petir, 8(1), 521808.

Wahyuningsih, S. S. (2023). Identifikasi Atribut Tingkat Lebih Tinggi untuk Prediksi Umur Bug. Jurnal Kolaboratif Sains, 6(3), 164-180.

What Is Debugging? | IBM. (2023, August). Ibm.com. https://www.ibm.com/topics/debugging

Whittaker, J. (2012). How Google Tests Software. Addison-Wesley.




DOI: https://doi.org/10.17509/seict.v5i2.70590

Refbacks

  • There are currently no refbacks.


Copyright (c) 2024 Journal of Software Engineering, Information and Communication Technology (SEICT)

Creative Commons License
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

Journal of Software Engineering, Information and Communicaton Technology (SEICT), 
(e-ISSN:2774-1699 | p-ISSN:2744-1656) published by Program Studi Rekayasa Perangkat Lunak, Kampus UPI di Cibiru.


 Indexed by.