Knowledge management in requirement elicitation: Situational methods view

Abstract

In small-scale software development organizations, software engineers are beginning to realize the significance of adapting software development methods according to project conditions. There is a requirement to proliferate this know-how to other developers, who may be facing the same settings/context, so that they too can benefit from others' experiences. In this paper, the application of situational method engineering in requirements elicitation phase is investigated. A novel, simple and dynamic web-based tool, Situational Requirement Method System (SRMS), is developed which can aid in conception/formulation, repository, and elicitation/derivation of methods related with this stage. The proposed approach and tool are validated by distributing a questionnaire among software professionals working in large software companies, and making SRMS accessible to them. The results indicate that a majority of the participants finds SRMS useful and provides various suggestions to improve it.

Improving the quality and quantity of functional and non‐functional requirements obtained during requirements elicitation stage for the development of e‐commerce mobile applications: an alternative reference process model

“…Each technique has advantages and disadvantages, and none of them is ideal for all circumstances [12,19].…”

“…However, these techniques can be selected and combined according to the project and may be more effective in certain circumstances than others [3,12,13,15]. When well chosen, these techniques can help to better capture high-quality requirements [12,24] and obtain a better understanding of the problem domain [12]. There are several factors that must be considered in order to select a requirements elicitation technique, such as [12]: the experience of the requirements engineer, the experience level of the requirements engineer in similar projects, the duration stage of requirements elicitation, the experience level of the customer, the possibility of holding meetings between the development team and the customer, the project budget, the level of user interaction with the system, and the project's complexity.…”

“…Although, there are several techniques available for requirements elicitation such as surveys/questionnaires, focus groups, brainstorming, ethnography, workshops, prototyping etc. [3,[9][10][11][12], software requirements are usually captured through interviews [3,13,14], mainly because the requirements engineers are usually unaware of the benefits of the application of other requirements elicitation techniques [14].…”

Knowledge Management Cycle: A Scientific Literature Review

“…Since knowledge is a significant resource for organisations, it should be managed in order to assist them to survive in various situations and maintain efficiency as well as uniqueness. Different methods are required to collect and process knowledge in order to benefit from it in the organisations (Oluikpe, 2015;Omotayo, 2015;D. Mishra, Aydin, A. Mishra, & Ostrovska, 2018).…”

An Investigation of Prototyping Technique in Pakistani Software Industry

“…R equirement engineering is a process to elicit, develop and organize the requirements in a proper way to produce a right software system [1][2][3][4][5][6]. Requirements engineering process is implemented on all stakeholders to find out their needs for system being developed [7][8][9][10]. There are mainly two types of requirements, that are user requirements and system requirements [11].…”