Framework for matching requirements elicitation techniques to project characteristics

Abstract

One of the most difficult jobs for requirements engineers is to select an appropriate RE method for the project at hand. Good engineers make good choices and have skills in applying selected techniques appropriately. Poor engineers usually have a narrow choice range limited by their training and biased by their experience. Once a RE technique that does not fit the current project is selected, the project is doomed to fail. In this article, we propose a framework to characterize typical RE techniques and use it as a base for selecting appropriate techniques at the time a project is started, as well as at the time a change in the nature of the project is recognized, or an obstacle is encountered in defining a suitable set of requirements.

Requirements gathering: the journey

“…Another RG technique selection method is the utilisation of frameworks developed in past research such as Carrizo, Dieste, & Juristo (2008) and Tsumaki & Tamai (2006). General project characteristics have been identified that point to the effectiveness or otherwise of particular techniques to elicit the most amount of requirements.…”

“…General project characteristics have been identified that point to the effectiveness or otherwise of particular techniques to elicit the most amount of requirements. Similarly in Tsumaki & Tamai (2006), their framework has focused on establishing which technique is most effective for a particular set of project characteristics.…”

“…Hickey & Davis (2003, p. 168) state that the success or failure of a system development effort depends heavily on the quality of the requirements. We can also see that problems with the elicited requirements can often be traced back to the technique used to gather these requirements (Tsumaki &Tamai, 2006, Davey andCope 2008).…”

Towards a new software quality model for evaluation the quality of gamified systems

“…[5] On the other hand, many software projects still fail today to deliver on time, with the expected costs and scope. One of the main reasons behind the failure of these projects is that they do not meet requirements, often caused by insufficient stakeholder collaboration, incomplete understanding of needs, insufficient knowledge and other [6].…”

A Systematic Investigation into the Use of Game Elements in the Context of Software Business Landscapes: A Systematic Literature Review

“…This can be clarified by the effects of human role in the development process by being a stakeholder (influencing the process by being a customer, developer and manager separately) related to the software product. Reasons for why these problems occurred while producing complex software products are: lack of communication among team members that causes collaboration problems, misunderstood of business requirements and objectives from customer, late performance evaluation and lack of reward systems by the management and also insufficient technical experiences [20].…”