An approach to estimate the saving from negotiation based on cost- benefit anaylsis model

This paper presents an approach to estimate the savings from implementing negotiation in requirements elicitation process. The aim of implementing negotiation is to minimize the possibility of introducing defects during the creation of requirements and to decrease later effort required to fix requirements defects. An empirical evaluation study is adopted through a role play experiment to evaluate the benefit of exercising negotiation. The net-gain and the return-oninvestment show positive value which suggest that negotiation activities worth an investment. Based on the return-oninvestment of 197 percent in average, this paper suggests that negotiation is a useful prevention activity to inhibit defects from occurring during the creation of requirements

Requirements Negotiation: Does Consensus Reduce Software Development Cost?

The requirements engineering activities within a software project are known to be critical to the successful production of a correctly functioning system. This is particularly so when considering the varying views of multiple stakeholders. One promising approach for improving the outcome is to introduce formal negotiation. Negotiation is beneficial to identify and to resolve conflicts between stakeholders. Consensus achieved through negotiation represents all key stakeholders’ perspectives and perceptions regarding the system to be developed. The aim of implementing negotiation is to minimize the possibility of introducing defects during the creation of requirements and to decrease later effort required to fix requirements’ defects. This paper answers the question of whether consensus gives positive significant impact to the software project as a whole or not. It presents an approach to estimate the savings from implementing negotiation in the requirements elicitation process. An empirical evaluation study is adopted through a role play experiment to evaluate the benefit of exercising negotiation. The net gain and the return on investment show positive values which suggest that negotiation activities are worth an investment. Based on a return on investment of 197 percent on average, this paper suggests that negotiation is a useful prevention activity to inhibit defects from occurring during the requirements creation process

Adding Value to Software Requirements： An Empirical Study in the Chinese Software Industry

The rapid growth of the Chinese software industry has attracted attention from all over the world. Meanwhile, software requirements selection has a crucial impact on the final value of a software product and the satisfaction of stakeholders. This paper presents an empirical study, which focuses on the decision-making criteria for requirements selection in market-driven software development projects in international companies in China. The outcome shows that some criteria, such as business strategy, customer satisfaction, and software features, are more important than others when making decisions for requirements selection

An Empirical Framework Design to Examine the Improvement in Software Requirements through Negotiation

Negotiation is one promising effort during requirements elicitation process to improve the quality of software requirements. When negotiation is claimed beneficial theoretically, it is important that the deployment of negotiation is examined and the effectiveness of negotiation is evaluated through empirical study. This paper aims at providing an empirical framework design to examine the improvement in software requirements through negotiation. Besides, it elaborates the relevance of negotiation in requirements elicitation process and its effectiveness. An empirical study method is imposed to design the framework. The design is carefully established based the selection of population and participants, the experimental protocol, threats to validity and justification of measures

A Contigency Model for Requirements Development

Drawing upon the requirements and software development literature, the present study proposes an integrative contingency model for requirements development. Based on 116 quality journal articles, we analyze requirements development risks, requirements development techniques, and heuristics for how they are effectively related. Subsequently, we synthesize the insights from the identified literature into a model for requirements development that relates patterns of risk resolution to archetypical risk profiles. The model integrates the literature on requirements and software development; sets the scene for future research; and, finally, proposes how practitioners can manage risks in requirements development projects

0028/2009 - Problemas na Elicitação de Requisitos: Uma visão de pesquisa/literatura

A primeira fase na engenharia de requisitos é a elicitação de requisitos, na qual as informações sobre as necessidades do cliente são adquiridas, sendo crucial e crítica e podendo comprometer todas as etapas subseqüentes do desenvolvimento. O presente relatório apresenta um levantamento dos problemas que ocorrem durante a elicitação de requisitos citados na literatura da área