Pengujian Sistem WebGIS
- 1. 9 February 2020 Pengujian Sistem dan Optimasi Kinerja Dany Laksono Mata Pelatihan WebGIS dan Transformasi Sistem Koordinat SKKNI Teknisi Utama – Analis Sistem Informasi Geografis
- 2. Geoserver dan Layanan Berbasis OGC • Functional dan Non-Functional Testing • User Acceptance Testing • Optimasi WebGIS • Geoserver for Production
- 3. ISO/IEC 9126: Software Quality ISO Kualitas software dapat dijadikan dasar untuk menilai hasil akhir pembuatan website dan melakukan testing
- 4. Software Testing dalam Siklus SDLC Dalam siklus SDLC, software testing dilakukan setelah pembangunan aplikasi (Tahap Quality Assurance)
- 5. Requirement Analysis Desain aplikasi harus menyesuaikan kebutuhan. Bukan sebaliknya
- 6. UGM.AC.ID FR vs NFR Requirement Analysis
- 7. FT vs NFT Functional Testing Non Functional Testing It tests ‘What’ the product does. It checks the operations and actions of an Application. It checks the behaviour of an Application. Functional testing is done based on the business requirement. Non- functional testing is done based on the customer expectation and Performance requirement. It tests whether the actual result is working according to the expected result. It checks the response time, and speed of the software under specific conditions. It is carried out manually. Example: Black box testing method. It is more feasible to test using automated tools. Example: Loadrunner. It tests as per the customer requirements. It tests as per customer expectations. Customer feedback helps in reducing the risk factors of the product. Customer feedback is more valuable for non- functional testing as it helps to improve and lets the tester to know the expectation of the customer. It is testing the functionality of the software. It is testing the performance of the functionality of the software. Functional testing has the following types: •Unit testing •Integration testing •System Testing •Acceptance Testing Non-functional testing includes: •Performance testing •Load Testing •Stress testing •Volume testing •Security testing •Installation testing •Recovery testing Example: A Login page must show textboxes to Enter the username and password. Example: Test if a Login page is getting loaded in 5 seconds.
- 9. Software Testing Dalam pembangunan aplikasi, pengujian dilakukan pada tiap tahapan sampai tahap akhir aplikasi dapat diterima oleh pengguna
- 10. User Acceptance Test (UAT) Pengembang aplikasi adalah orang teknis: pembangunan perangkat lunak dilakukan berdasarkan interpretasi terhadap spesifikasi Perangkat lunak ini lengkap sesuai dengan spesifikasi fungsional tetapi ada beberapa kebutuhan bisnis dan proses yang dikenal hanya oleh end user yang mungkin belum terjawab atau salah interpretasi
- 12. Tahapan User Acceptance Test (UAT) UAT dilakukan berdasarkan atas Functional Requirement Uji diberikan kepada sample pengguna sesuai dengan business requirements dan user requirements
- 13. Contoh UAT
- 14. Contoh UAT
- 15. Contoh UAT
- 16. Contoh UAT
- 17. Web Testing Pengujian halaman web memiliki beberapa perbedaan dibandingkan dengan software desktop, khususnya pengujian Non-Functional
- 18. Frontend vs Backend Testing Frontend testing Backend testing Frontend testing is always performed on the GUI. Back End Testing involves databases and business logic testing. The tester must be knowledgeable about the business requirements as well as the usage of the automation frameworks tools. The tester to be able to perform back-end testing must have a strong background in the database and Structured Query Language (SQL) concepts. GUI is used to perform the Testing GUI may or may not be used to perform Testing It does not need any information to be stored in a database. It does need information stored in the database. It is essential to check the overall functionality of the application. Backend testing is important to check for deadlock, data corruption, data loss, etc Types of Testing done are – Unit Tests, Acceptance Testing, Accessibility Testing, Regression Testing, etc. Three widely used types of database testing are SQL Testing, API Testing, etc.
- 22. (Nishant Worah, 2009) Uji Performa
- 24. Optimasi WebGIS Untuk ukuran tile yang sangat besar, gunakan Tiling (GeoWebCache)
- 25. Perbandingan waktu-muat Gunakan WMS apabila tidak diperlukan pengolahan data layer yang memerlukan analisis spasial
- 26. Keamanan Geoserver Untuk meningkatkan keamanan Geoserver, gunakan basisdata atau tambahan keamanan dari aplikasi lain (misal LDAP)
- 28. Contoh Kasus QGIS2Web untuk membuat antarmuka WebGIS (Ramdhani, 2019)
- 29. Contoh Kasus Hasil analisis kesesuaian wilayah pemukiman (Ramdhani, 2019)
- 30. Contoh Kasus Use Case Diagram: Masyarakat dapat melihat informasi dari hasil analisis (Ramdhani, 2019)
- 31. Contoh Kasus Activity Diagram: Pengguna dapat menampilkan lokasi saat ini dengan mengklik tombol (Ramdhani, 2019)
- 32. Contoh Kasus Sequence Diagram Geolokasi (Ramdhani, 2019)
- 33. Contoh Kasus Class diagram (Ramdhani, 2019)
- 35. Contoh Kasus Hasil Akhir WebGIS (Ramdhani, 2019)
- 37. TERIMA KASIH
Editor's Notes
- #11: https://www.softwaretestinghelp.com/what-is-user-acceptance-testing-uat/
- #12: Implementasi interoperabilitas data spasial
- #13: https://cdn.softwaretestinghelp.com/wp-content/qa/uploads/2018/10/Key-Activities-of-each-UAT-Phase.jpg
- #14: Implementasi interoperabilitas data spasial
- #15: Implementasi interoperabilitas data spasial
- #16: Implementasi interoperabilitas data spasial
- #17: Implementasi interoperabilitas data spasial
- #18: Geoserver on Steroid https://www.slideshare.net/geosolutions/gs-steroids-foss4ge2014
- #19: Implementasi interoperabilitas data spasial
- #22: Google Lighthouse
- #23: Google Lighthouse
- #24: Google Lighthouse
- #25: Implementasi interoperabilitas data spasial
- #26: Implementasi interoperabilitas data spasial
- #27: Implementasi interoperabilitas data spasial
- #28: Implementasi interoperabilitas data spasial