ABSTRACT
21 Laundry Padang is an bussiness that engaged in laundry services which is provide various services such as a complete laundry (dry cleaning and ironing), wash and dry, and the ironing only. Based on the analysis conducted, it was found that the transaction system running at 21 Laundry Padang was not optimal and found problems such as accumulation of archives and reports, slow information flow, slow process of collecting data, and difficulty in reporting. The solution for these problems is implementaion of a web-based information system that is equipped with a mobile application that can be accessed by the costumer anytime and anywhere. The systems was built by using waterfall method which is consist of analysis, design, implementation, and testing phase. In the analysis phase, the tools used for modeling is BPMN (Business Process Model Notation), Use Case Diagram and Use Case Scenarios. The design phase was done by making the architectural design of application, DFD (Data Flow Diagram), ERD (Entity Relationship Diagram), and User Interface. The implementation process was done by using MySQL database and PHP and javascript programming language. Programming was done by using procedural method. Basic4Android was used to build mobile application. Then the system that had been built was tested by using black-box testing. The test results show that the system has been built in accordance with the specified functional requirements. This research has deliver a laundry information system services that can be used for managing laundry service at 21 Laundy Padang.
Untuk setiap use case yang berhasil diidentifikasi, perlu dilakukan analisa tingkah laku sistem. Tingkah laku sistem memperlihatkan respon yang akan diberikan oleh sistem saat menerima input dari pengguna sistem. Tingkah laku sistem dimodelkan dengan menggunakan skenario use case. Skenario use case merupakan urutan jalannya proses pada setiap use case yang terdapat di dalam sistem. Skenario use case ini menjelaskan apa yang dilakukan oleh pengguna dan apa reaksi yang diberikan oleh sistem terhadap suatu proses tertentu.
Tabel 1. Skenario use case menambah data transaksi
| Use Case Name | Menambah Data Transaksi |
| Participating Actors | Pemilik dan Karyawan |
| Flow of Events | 1. Pemilik/karyawan mengklik sub menu tambah transaksi pada menu transaksi
2. Sistem menampilkan form tambah data transaksi 3. Pemilik/karyawan memilih pelanggan yang akan melakukan transaksi 4. Pemilik/karyawan menambahkan data cucian pelanggan 5. Pemilik/karyawan menambahkan data pembayaran awal pelanggan. 6. Pemilik/karyawan mengklik tombol “simpan” 7. Sistem menyimpan dan menampilkan pesan data sukses disimpan Entry Condition
|
| Entry Condition | Pemilik/karyawan telat login ke system |
| Exit Condition | Sistem menyimpan data transaksi |
| Alternative Scenario |
1. Sistem memeriksa status login 2. Pemilik/karyawan mengisi form tambah data transaksi 3. Sistem memeriksa valid atau tidaknya data yang diisi 4. Sistem menampilkan pemberitahuan data harus diisi 5. Pemilik/karyawan mengisi form tambah data yang belum terisi dan mengklik tombol “simpan” 6. Sistem menyimpan data dan menampilkan pesan data sukses disimpan
|
Referensi :
file:///D:/Materi%20bu%20herla%20sem4/jurnal/jurnal%20pembangunan-sistem-informasi-pelayanan-j.pdf
Husnil Kamil1*, Audiah Duhani2
Website : jurnal.umj.ac.id/index.php/semnastek
RenaaWeb 