Criteria for Accepting Software Requirements Negotiation Tools in the Software Industry

Abstract

Requirements negotiation is a centralized process of making a decision in order to resolve conflicts in the requirements of the stakeholder. The negotiation will enable the shared vision of software to be developed among the heterogeneous stakeholder in the software industry to be achieved. Many process models used for the negotiation of stakeholder’s requirements have been proposed for the software industry by the research community, yet the acceptance of these process models is discouraging. This study tends to investigate the inadequate adoption of requirements negotiation process models. Further, it finds the acceptance criteria for the software industry to adopt requirements negotiation models. Finding shows that the software industries do not adopt the process models. The perceived usefulness, perceived ease of use and many more criteria have been identified through the literature review on the general criteria of software systems acceptance.

Software Requirements Negotiation: A Review on Challenges

“…Challenges [4] Conflict resolution [12] Conflict resolution [10] Conflict resolution [42] Communication [6] Decision making [35] Decision making [9] Decision making and conflict resolution [17] Performance of RN tool [16] Performance [24] Managing requirement changes [18] Performance [43] Communication [20] Communication [22] Communication [19] Communication [44] Requirement analysis [41] Managing requirement changes [11] Conflict resolution [1] Decision making [45] Decision making and conflict resolution [36] Decision making [46] Decision making [47] Performance [33] Decision Making [15] Performance [2] Conflict resolution [38] Decision-making [48] Decision-making [49] Performance and Decision making [13] Performance [14] Performance [8] Decision-making and performance [21] Communication [50] Decision-making VI. RESEARCH FINDINGS During searching and data extraction from the selected papers, many challenges were identified in software requirements negotiation.…”