Identification of Software Requirements using a Qualitative Study of the Persona User approach (Case Study: The Process of Making a Practicum Module with the Ability of Students to Reduce the Case of Source Code Plagiarism)
DOI:
https://doi.org/10.21111/fij.v5i2.4385Keywords:
Persona, Metode, User Persona, HCIAbstract
AbstrakIdentifikasi kebutuhan dalam pengembangan perangkat lunak merupakan langkah awal yang dilakukan dan mempengaruhi terhadap tahapan-tahapan pengembangan selanjutnya. Dalam tahap ini terdapat proses penentuan kebutuhan mengenai apa yang akan dibuat. Dalam tahap ini terdapat salah satu metode yang digunakan, yaitu User Persona. Teknik Personas yang dikembangkan oleh human-computer interaction (HCI) mengumpulkan data-data tentang pengguna, memperoleh pemahaman tentang kriteria mereka serta dapat mengetahui apa yang dibutuhkan oleh user pada system. Penelitian ini bertujuan menggunakan pendekatan pesona untuk mengetahui kebutuhan dan menganalisa keberagaman user yang memiliki perbedaan dari segi umur, jenis kelamin dan pengetahuan sehingga dapat dijadikan acuan dalam pengembangan sistem. Penggunaan pendekatan persona untuk menyelesaikan permasalahan dalam penyusunan materi modul praktikum dengan kemampuan mahasiswa agar dapat mengurangi kasus plagiasi source code pada waktu praktikum. Dari penelitian ini bahwa pengambilan data menggunakan pendekatan persona selanjutnya di analisis sesuai kebutuhan user, dan menghasilkan perangkat lunak yang dapat mengelola modul praktikum. Perangkat lunak ini memberikan akses bagi dosen, asisten laboratorium dan mahasiswa untuk dapat membagikan modul praktikum, mengerjakan soal latihan yang disesuaikan dengan Rencana Pelaksanaan Pembelajaran sebelum mengerjakan soal-soal praktikum dan menerima hasil praktikum lebih efektif dan mengurangi plagiarisme diantara mahasiswa.Kata Kunci – Persona, Metode, User Persona, HCI Abstract[Identification of Software Requirements using a Qualitative Study of the Persona User approach (Case Study: The Process of Making a Practicum Module with the Ability of Students to Reduce the Case of Source Code Plagiarism)] - Identification of requirements in software development is a very important initial stage and influences the subsequent stages of development. In this stage there is a process of determining the needs of what will be made. The method that will be used in this stage is User Persona. The Personas technique developed by human-computer interaction (HCI) collects data about users, obtains an understanding of their criteria and can find out what is needed by the user on the system. This study aims to use the charm approach to determine the needs and analyze the diversity of users who have differences in terms of age, gender and knowledge so that it can be used as a reference in system development. The use of a persona approach to solving problems in the preparation of practical module materials with the ability of students to reduce the case of source code plagiarism at the time of practicum. From this study the data collection by using the persona approach will be analyzed according to user needs, and produces software that could manage practice module. The purpose of this software is to provide access for lecturers, laboratory assistants, and students to be able to distribute practicum modules, do the excercises that are adjusted to the Learning Implemantation Plan before working on practicum questions and receive practical results more efectively, and reduce plagiarism among students.Keywords: Persona, Metode, User Persona, HCIReferences
[1] S. T. Acuña, J. W. Castro, and N. Juristo, “A HCI technique for improving requirements elicitation,” Inf. Softw. Technol., vol. 54, no. 12, pp. 1357–1375, 2012, doi: 10.1016/j.infsof.2012.07.011.[2] J. W. Castro, S. T. Acuña, and N. Juristo, “Enriching requirements analysis with the personas technique,” in CEUR Workshop Proceedings, 2008.[3] T. Miaskiewicz, T. Sumner, and K. A. Kozar, “A Latent Semantic Analysis methodology for the identification and creation of personas,” in Conference on Human Factors in Computing Systems - Proceedings, 2008, doi: 10.1145/1357054.1357290.[4] A. Jansen, M. Van Mechelen, and K. Slegers, “Personas and behavioral theories: A case study using self-determination theory to construct overweight personas,” in Conference on Human Factors in Computing Systems - Proceedings, 2017, doi: 10.1145/3025453.3026003.[5] S. T. Acuña, J. W. Castro, and N. Juristo, “A HCI technique for improving requirements elicitation,” in Information and Software Technology, 2012, doi: 10.1016/j.infsof.2012.07.011.[6] J. Grudin and J. Pruitt, “Personas, Participatory Design and Product Development: An Infrastructure for Engagement,” PDC, 2002.[7] B. Ferreira, G. Santos, and T. Conte, “Identifying possible requirements using personas: A qualitative study,” ICEIS 2017 - Proc. 19th Int. Conf. Enterp. Inf. Syst., vol. 2, no. Iceis, pp. 64–75, 2017, doi: 10.5220/0006311600640075.[8] K. Väänänen-Vainio-Mattila, V. Roto, and M. Hassenzahl, “Towards Practical User Experience Evaluation Methods,” in Proceedings of the International Workshop on Meaningful Measure: Valid Useful User Experience Measurement (VUUM 2008), 2008, doi: citeulike-article-id:8362765.[9] F. Guo, S. Shamdasani, B. Randall, and P. Rau, “Creating Effective Personas for Product Design: Insights from a Case Study Internationalization, Design and Global Development,” Lect. Notes Comput. Sci. Incl. Subser. Lect. Notes Artif. Intell. Lect. Notes Bioinforma., 2011, doi: 10.1007/978-3-642-21660-2_5.[10] N. A. M. Maiden and G. Rugg, “ACRE: Selecting methods for requirements acquisition,” Softw. Eng. J., 1996, doi: 10.1049/sej.1996.0024.[11] J. Pruitt and T. Adlin, The Persona Lifecycle: Keeping People in Mind Throughout Product Design. 2006.[12] L. Nielsen and K. S. Hansen, “Personas is applicable- A study on the use of personas in Denmark,” in Conference on Human Factors in Computing Systems - Proceedings, 2014, doi: 10.1145/2556288.2557080.[13] M. Aoyama, “Persona-and-scenario based requirements engineering for software embedded in digital consumer products,” in Proceedings of the IEEE International Conference on Requirements Engineering, 2005, doi: 10.1109/re.2005.50.[14] K. Goodwin, “Getting from research to personas: harnessing the power of data,” Cooper, 2008. .
Downloads
Submitted
Accepted
Published
Issue
Section
License
Please find the rights and licenses in the Fountain of Informatics Journal (FIJ). By submitting the article/manuscript of the article, the author(s) agree with this policy. No specific document sign-off is required.
1. License
The non-commercial use of the article will be governed by the Creative Commons Attribution license as currently displayed on Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
2. Author(s)' Warranties
The author warrants that the article is original, written by the stated author(s), has not been published before, contains no unlawful statements, does not infringe the rights of others, is subject to copyright that is vested exclusively in the author, and free of any third party rights, and that any necessary written permissions to quote from other sources have been obtained by the author(s).
3. User/Public Rights
FIJ's spirit is to disseminate articles published are as free as possible. Under the Creative Commons license, FIJ permits users to copy, distribute, display, and perform the work for non-commercial purposes only. Users will also need to attribute authors and FIJ on distributing works in the journal and other media of publications. Unless otherwise stated, the authors are public entities as soon as their articles got published.
4. Rights of Authors
Authors retain all their rights to the published works, such as (but not limited to) the following rights;
- Copyright and other proprietary rights relating to the article, such as patent rights,
- The right to use the substance of the article in own future works, including lectures and books,
- The right to reproduce the article for own purposes,
- The right to self-archive the article (please read out deposit policy),
- The right to enter into separate, additional contractual arrangements for the non-exclusive distribution of the article's published version (e.g., post it to an institutional repository or publish it in a book), with an acknowledgment of its initial publication in this journal (Jurnal Optimasi Sistem Industri).
5. Co-Authorship
If the article was jointly prepared by more than one author, any authors submitting the manuscript warrants that he/she has been authorized by all co-authors to be agreed on this copyright and license notice (agreement) on their behalf, and agrees to inform his/her co-authors of the terms of this policy. FIJ will not be held liable for anything that may arise due to the author(s) internal dispute. FIJ will only communicate with the corresponding author.
6. Royalties
Being an open accessed journal and disseminating articles for free under the Creative Commons license term mentioned, author(s) aware that FIJ entitles the author(s) to no royalties or other fees.
7. Miscellaneous
FIJ will publish the article (or have it published) in the journal if the article’s editorial process is successfully completed. FIJ's editors may modify the article to a style of punctuation, spelling, capitalization, referencing, and usage that deems appropriate. The author acknowledges that the article may be published so that it will be publicly accessible and such access will be free of charge for the readers as mentioned in point 3.
