1. Introduction

2. Related Work

3. Methodology

Figure 1. Agile Methodolgy

Figure 1. Agile Methodolgy

4. Result and Discussion

4.3. Software Requirement

Software requirements are specifications needed from a software. on this website the following specifications are required:

Table 1. Software Requirement

Table 1. Software Requirement

Requirement	Result
DBMS	MySQL
Programming Language	PHP
Framework	Laravel
Operating System	>Andorid, Windows, Mac, ios, linux

4.5. System Design

The following is the system design that has been made

4.5.1. ERD

ERD is used to describe how the entities in the database relate to each other. ERD can help in designing databases better, and make it easier to identify and understand relationships between entities.

Figure 2. ERD

Figure 2. ERD

4.5.2. Usecase

Use case can be used to describe how users (actors) will interact with a system in different situations.

Figure 3. Usecase Admin

Figure 3. Usecase Admin

Figure 4. Usecase Officer

Figure 4. Usecase Officer

In this use case, it can be observed that the Administrator can manage officer data, handle reports, and export reports. Meanwhile, the Officer is only able to manage report data and export report data.

4.6. Product Function

This website has several main views, including:

4.6.1. Login

This view can be accessed by the admin or user to log in to the website by entering a username and password.

Figure 5. Login Interface

Figure 5. Login Interface

4.6.2. Input Report

This view can be accessed by the admin or user to input reports on waste data management by residents.

Figure 6. Input Data Warga

Figure 6. Input Data Warga

4.6.3. History Input Data

This view can be accessed by the admin or user to view the history of input data reports.

Figure 7. Tabel Input Data

Figure 7. Tabel Input Data

4.6.4. Export Data

This view can be accessed by the admin or user to export management report data.

Figure 8. Export Data

Figure 8. Export Data

4.6.5. QR Scanner

This view can be accessed by the admin or user to input data use QR Code Scanner.

Figure 9. QR Scanner

Figure 9. QR Scanner

4.8. Testing Application

In this section, we conducted application testing using black box methodology. Black box testing focuses solely on the application’s functionality, assessing whether it operates smoothly or encounters any issues.

4.8.1. Login

login page works normally

Table 2. Login Test

Table 2. Login Test

ID	T01
Test Name	Login Test
Objective	Login into Web Application
Scenario	User login using email and password on the form. if finished then click login. If true then access is accepted, if false then access is denied
Evaluation	Result accepted if Input data Form Displayed
Test Result (Data Normal)
Input	Expected	Analysis	Conclusion
Email, Password	Access Accepted, The system displays a data input interface.	Access Accepted, The system displays a data input interface.	Valid
Test Result (Data Error)
Input	Expected	Analysis	Conclusion
Email, Password	Access Denied, The system displays warning popup.	Access Denied, The system displays warning popup.	Valid

4.8.2. Input Data

Input Data Works Normally

Table 3. Input Data Test

Table 3. Input Data Test

ID	T02
Test Name	Input Data Test
Objective	Input Data Sorting
Scenario	User input data the citizen data (Name of Head of Household, House Number, RT, RW) and Select sorting
Evaluation	Result accepted if history data page Displayed
Test Result (Data Normal)
Input	Expected	Analysis	Conclusion
Name of Head of Household, House Number, RT, RW, Sorting	Data Accepted, The system displays History Input Data Page.	Data Accepted, The system displays History Input Data Page.	Valid
Test Result (Data Error)
Input	Expected	Analysis	Conclusion
Part of form is filled (ex RT is Null)	Data Rejected, The system displays Error Pop up.	Data Rejected, The system displays Error Pop up.	Valid

4.8.3. History Data

History data page work normally. In this page, data can be edited or deleted

Table 4. Edit Data History Test

Table 4. Edit Data History Test

ID	T03
Test Name	Edit Data History Test
Objective	Edit Data Sorting History
Scenario	User edit the citizen data by id
Evaluation	Result accepted if data from history data page changed
Test Result (Data Normal)
Input	Expected	Analysis	Conclusion
ID	Result Accepted, The system displays History Data Page that was changed.	Result Accepted, The system displays History Data Page that was changed.	Valid
ID	Data Accepted, The system displays Edit Data Page and then Displayed History Data Page that was changed.	Data Accepted, The system displays Edit Data Page and then Displayed History Data Page that was changed.	Valid

4.8.4. Export Report

Export data page work normally. In this page, data can be exported by date or by RT.

Table 5. Export Data Test

Table 5. Export Data Test

ID	T04
Test Name	Export Data Test
Objective	Export Data Sorting
Scenario	Users can export report data by date or RT
Evaluation	Result accepted if data report downloaded
Test Result (Data Normal)
Input	Expected	Analysis	Conclusion
Date	Result Accepted, The system displays data sorting results by date.	Result Accepted, The system displays data sorting results by date.	Valid
RT and RW	Result Accepted, The system displays data sorting results by RT.	Result Accepted, The system displays data sorting results by RT.	Valid

4.8.5. QR Scan

QR Code Scanner work normally.

Table 6. QR Code Scanner Test

Table 6. QR Code Scanner Test

ID	T03
Test Name	QR Code Scanner Test
Objective	Scan QR Code
Scenario	User scan QR Code for input data
Evaluation	Result accepted if data from QR Code inputted to Input data form
Test Result (Data Normal)
Input	Expected	Analysis	Conclusion
QR Code	Result Accepted, The system displays Inputted data from QR Code to Input Data Form.	Result Accepted, The system displays Inputted data from QR Code to Input Data Form.	Valid
Test Result (Data Error)
Input	Expected	Analysis	Conclusion
QR Code Error	Result Accepted, The system displays nothing and reloads the qr scan.	Result Accepted, The system displays nothing and reloads the qr scan.	Valid

5. Conclusion

References

1. E. Damanhuri and T. Padmi, “Pengelolaan sampah,”. Diktat kuliah TL 2010, 3104, 5–10.
2. A. S. Suryani, “Peran bank sampah dalam efektivitas pengelolaan sampah (studi kasus bank sampah malang),”. Aspirasi: Jurnal Masalah-masalah Sosial 2014, 5, 71–84.
3. B. K. P. K. PUPR, “Sampah masih menjadi kendala di perkotaan,” August 2004. [Online]. Available: https://pu.go.id/berita/sampah-masih-menjadi-kendala-di-perkotaan.
4. S. Samsoni, Y. S. Samsoni, Y. Kurniawan, and M. Ardhiansyah, “Perencanaan sistem informasi bank sampah wpl depok berbasis web,”. Jurnal VOI (Voice Of Informatics) 2021, 10, 43–54. [Google Scholar]
5. N. Purwati, F. N. Dwitama, and S. Kiswati, “Aplikasi sampling (sampah lingkungan) pengrajin sampah berbasis web menggunakan metode rad (rapid application development),”. EVOLUSI: Jurnal Sains Dan Manajemen 2021, 9.
6. W. Zarman, “Aplikasi spreadsheet untuk pengolahan data bank sampah,”. Jurnal Abdimas PHB: Jurnal Pengabdian Masyarakat Progresif Humanis Brainstorming 2023, 6, 228–234.
7. G. F. Fitriana, A. G. F. Fitriana, A. Hashina, and N. A. F. Tanjung, “Pengembangan aplikasi pengelolaan sampah berbasis android studi kasus bank sampah desa kalibagor,”. Journal of Dinda: Data Science, Information Technology, and Data Analytics 2022, 2, 97–102. [Google Scholar]
8. M. D. Marali, F. Pradana, and B. Priyambadha, “Pengembangan sistem aplikasi transaksi bank sampah online berbasis web (studi kasus: Bank sampah malang),”. Jurnal Pengembangan Teknologi Informasi dan Ilmu Komputer 2018, 2548, 964X.
9. P. Abrahamsson, O. Salo, J. Ronkainen, and J. Warsta, “Agile software development methods: Review and analysis,”. arXiv 2017, arXiv:1709.08439.
10. S. Al-Saqqa, S. Sawalha, and H. AbdelNabi, “Agile software development: Methodologies and trends.”. International Journal of Interactive Mobile Technologies 2020, 14.