Effort Estimation Menggunakan Metode Use Case Point untuk Pengembangan Perangkat Lunak Studi Kasus Sistem Inventory peminjaman alat Laboratorium
Main Article Content
Abstract
Estimasi proyek perangkat lunak merupakan fase krusial yang dapat menentukan keberhasilan suatu proyek, dimana di dalamnya termasuk estimasi waktu pengerjaan, biaya dan sumberdaya manusia. Salah satu estimasi yang dilakukan dalam awal sebuah proyek perangkat lunak adalah software effort estimation atau estimasi resiko dan ukuran umum dari perangkat lunak yang akan dibuat pada sebuah proyek. Metode Use Case Points (UCP) merupakan metode software effort estimation yang menunjukkan performa yang lebih baik dibandingkan dengan metode lainnya. Penggunaan metode UCP dalam proyek perangkat lunak khususnya sistem inventory di indonesia dapat menjadi salah satu contoh dan acuan bagaiamana estimasi perangkat lunak inventory. Hasil dari penelitian ini adalah resiko dari proyek sistem inventory peminjaman alat laboratorium memiliki resiko kecil, dapat dikerjakan dalam waktu yang raltif singkat dan tidak membutuhkan sumberdaya yang banyak
Article Details
Copyright Notice
Authors who publish with Journal of Informatics, Information System, Software Engineering and Applications (INISTA) agree to the following terms:
- Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution License (CC BY-SA 4.0) that allows others to share the work with an acknowledgement of the work's authorship and initial publication in this journal.
- Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgement of its initial publication in this journal.
- Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work.
References
[2] S. C.R, Software Sizing and Estimating: Mk II FPA (Function Point Analysis), New York, NY: John Wiley & Sons, Inc, 1991.
[3] A. Abran, S. Oligny, C. Symsons and J. M. Desharnais, "Functional Size Measurements Method - COSMIC - FFP; Design and Field Trials," in FESMA-AEMES Software Measurements Conference 2000, 2000.
[4] M. M. Kirmani and A. Wahid, "Use Case Point Method of Software Effort Estimation: A Review," International Journal of Computer Applications, vol. 116, no. 15, pp. 43-47, 2015.
[5] K. G, "Metrics for Objectory," University of Linkoping, Sweden, 1993.
[6] S. Kusumoto, M. Tsuda and K. Inoue, "Use Case Points Measurement Tool for Effective Project Management," in 14th Asia-Pacific Software Engineering Conference (APSEC'07), Aichi, Japan, 2007.
[7] G. Schneider and J. P. Winters, Applying Use Cases: A Practical Guide (2nd Edition), Boston, Massachusetts: Addison-Wesley Professional, 2001.
[8] B. Anda, E. Angelvik and K. Ribu, "Improving Estimation Practices by Applying Use Case Models," in International Conference on Product Focused Software Process Improvement, Rovaniemi, Finland, 2002.
[9] M. Damodaran and A. N. E. Washington, Estimation Using Use Case Points, Texas, Victoria: University of Houston, 2002.
[10] R. K. Clemmons, "Project estimation with use case points," The Journal of Defence Software Engineering, pp. 18-22, 2006.