Algorithmic Decision-Making Concerns for Software: Non-Functional Requirement Elicitation as a Solution
Keywords:
Non-functional requirement, Privacy, Software, Openness, AlgorithmAbstract
Reference [1,2] Millions of software are lunched yearly and this software depend on data to produce required output. Personal data privacy and security has been a source of public concern for some time, and is usually interpreted in terms of data obtained from interaction with software. It is difficult to know whether a software system's decisions are fair and what considerations were put in place in the system's internal decision-making process if the system's decisions are opaque. This has the potential to cause injustice and bias. In addition, a lack of openness may lead to a decrease in user acceptance and happiness. Algorithmic data-driven decision-making systems are becoming more automated, and they've had a lot of success in a lot of different applications. The General Data Protection Regulation of the European Union and other regulations limits algorithmic use of personal data and has fueled the dispute over the right to disclosure. This research adapted a crowd requirements elicitation model to develop a framework for the proper elicitation non-functional requirement. The developed model uses natural language processing integrated into a chatbot and a document extraction strategy since non-functional requirement exist also as government regulations and industrial standards. Proper and comprehensive elicitation of non-functional requirements will give accurate information on how the system performs its required task and such documents are best in terms of openness to the use of data by algorithms to avoid algorithm decision making concerns.
References
N. C. Otuneme, M. O. Eze, O. D. Adekola, A. O. Adebayo, and S. O. Ogunlere, “Railway Travel-Time Optimization System,” vol. 7, no. 11, pp. 108–116, 2018.
O. Akintunde, N. Otuneme, O. Adetunji, and A. Akinsanya, “Health Information Exchange Model for Nigerian Health Information Systems,” Article in International Journal of Computer Science and Information Security, vol. 17, no. 2, p. 181, 2019.
R. Di Cosmo, “Software Heritage: Why and How We Collect, Preserve and Share All the Software Source Code,” in 40th International Conference on Software Engineering: Software Engineering in Society (ICSE-SEIS), IEEE/ACM, 2018, pp. 2–2.
L. E. Buck and B. Bodenheimer, “Privacy and personal space: Addressing interactions and interaction data as a privacy concern,” Proceedings - 2021 IEEE Conference on Virtual Reality and 3D User Interfaces Abstracts and Workshops, VRW 2021, pp. 399–400, 2021, doi: 10.1109/VRW52623.2021.00086.
L. Chazette and K. Schneider, “Explainability as a non-functional requirement: challenges and recommendations,” Requirements Engineering, vol. 25, pp. 493–514, 2020, doi: 10.1007/s00766-020-00333-1.
IEEE Computer Society, IEEE Trial-Use Standard for Software. The Institute of Electrical and Electronics Engineers Standards Assosiation, 2019. doi: 10.1109/IEEESTD.2019.8870263.
IEEE, “IEEE 610.12 - Standard Glossary of Software Engineering Terminology | EnIEEE. 1990. IEEE 610.12 - Standard Glossary of Software Engineering Terminology | Engineering360.gineering360,” 1990. Accessed: May 27, 2021. [Online]. Available: https://standards.globalspec.com/std/398645/IEEE 610.12
S. Alzu’Bi, B. Hawashin, M. Eibes, and M. Al-Ayyoub, “A Novel Recommender System Based on Apriori Algorithm for Requirements Engineering,” 2018 5th International Conference on Social Networks Analysis, Management and Security, SNAMS 2018, pp. 323–327, 2018, doi: 10.1109/SNAMS.2018.8554909.
Regulation(eu), “EUR-Lex - 02016R0679-20160504 - EN - EUR-Lex,” EU Open Data Portal, Apr. 27, 2016. https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A02016R0679-20160504 (accessed Apr. 08, 2022).
R. Hamon, H. Junklewitz, S. Ignacio, G. Malgieri, and P. Hert De, “Bridging the Gap Between AI and Explainability in the GDPR: Towards Trustworthiness-by-Design in Automated Decision-Making,” IEEE Computational Intelligence Magazine, vol. 17, no. 1, pp. 72–85, 2022, doi: 10.1109/MCI.2021.3129960.
P. K. Srivastava and R. Sharma, “Crowdsourcing to elicit requirements for MyERP application,” in 1st International Workshop on Crowd-Based Requirements Engineering, CrowdRE 2015 - Proceedings, Institute of Electrical and Electronics Engineers Inc., Dec. 2015, pp. 31–35. doi: 10.1109/CrowdRE.2015.7367586.
O. Adetunji, E. Oyenuga, and N. Otuneme, “Crowd Requirement Rating Technique (CrowdReRaT) Model for Crowd Sourcing,” International Journal of Computer Applications, vol. 176, no. 22, pp. 9–14, 2020, doi: 10.5120/ijca2020920178.
Downloads
Published
How to Cite
Issue
Section
License
Copyright (c) 2023 Nzechukwu Otunneme, Monday Eze, Kuyoro Shade, Ayankoya Folasade
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.
Authors who submit papers with this journal agree to the following terms.
