Analisa Konflik Pemangku Kepentingan Pada Rekayasa Kebutuhan Perangkat Lunak
Abstract
Abstrak. Rekayasa kebutuhan merupakan sebuah bagian terpenting dalam proses pengembangan perangkat lunak, banyak tantangan yang harus dihadapi pada bagian itu. Konflik antara pemangku kepentingan merupakan salah satu tantangan yang akan dihadapi pada fase tersebut dan merupakan tantangan yang mempunyai pengaruh besar pada fase-fase berikutnya, bahkan pada keseluruhan fase pengembangan perangkat lunak, apa bila tidak mendapat penanganan yang tepat maka konflik bisa berdampak buruk pada hasil produk sebuah perangkat lunak. Paper ini menyoroti pentingnya mengetaui penyebab dan dampak conflik yang terjadi guna menentukan formulasi penangan yang tepat terhadap konflik yang terjadi, dalam tulisan ini juga dipaparkan beberapa penelitian terkait sebelumnya dalam melakukan resolusi konflik pada rekayasa kebutuhan.
References
[1] N. Ali and R. Lai, “A method of requirements elicitation and analysis for Global Software Development,†J. Softw. Evol. Process, vol. 29, no. 4, p. e1830, 2017.
[2] I. G. A. A. D. Aristantya and I. M. A. Wibawa, “Pengaruh Konflik Interpersonal Dan Beban Kerja Terhadap Stres Kerja Pada Kantor Sekretariat Daerah Kota Denpasar,†E-Jurnal Manaj., vol. 5, no. 8, 2016.
[3] S. R. Schach, “Object-Oriented and Classical Software.†McGraw-Hill, p. 688 pp, 2011.
[4] I. S. Board, “Ieee standard glossary of software engineering terminology,†New York Inst. Electr. Electron. Ehgineers, 1990.
[5] P. Zave, “Classification of research efforts in requirements engineering,†in Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE’95), 1995, pp. 214–216.
[6] M. Rahman and J. Gao, “A reusable automated acceptance testing architecture for microservices in behavior-driven development,†in 2015 IEEE Symposium on Service-Oriented System Engineering, 2015, pp. 321–325.
[7] M. Handzic, N. Durmic, A. Kraljic, and T. Kraljic, “An empirical investigation of the relationship between intellectual capital and project success,†J. Intellect. Cap., vol. 17, no. 3, pp. 471–483, 2016.
[8] S. Asghar and M. Umar, “Requirement Engineering Challenges in Development of Software Applications and Selection of Customer-off-the-Shelf ( COTS ) Components Sohail.Asghar@jinnah.edu.pk Mahrukhumar@yahoo.com important tasks . Entire software is supported by four pillars of requ,†Int. Jounal Softw. Eng., vol. 1, no. 2, pp. 32–50, 2010.
[9] N. Kennon, P. Howden, and M. Hartley, “Who really matters?: A stakeholder analysis tool,†Ext. Farming Syst. J., vol. 5, no. 2, p. 9, 2009.
[10] K. G. Turner et al., “A review of methods, data, and models to assess changes in the value of ecosystem services from land degradation and restoration,†Ecol. Modell., vol. 319, pp. 190–207, 2016.
[11] Y. Wang, Y. Sun, and X. Liu, “Research on methodology for resolving conflicts from project stakeholders based on ANP theory,†in 2009 International Conference on Management and Service Science, 2009, pp. 1–4.
[12] T. Kim and D. Bae, “Stakeholder Conflict Resolving Model in PSS Design,†in Cumulus Helsinki Conference, 2012.
[13] R. Lai, S. Mahmood, and S. Liu, “RAAP: a requirements analysis and assessment process framework for component-based system,†JSW, vol. 6, no. 6, pp. 1050–1066, 2011.
Copyright (c) 2019 Musamus Journal Of Research Information and Communication Technology
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
