An Introduction to Requirements Knowledge

Maalej, Walid; Thurimella, Anil Kumar

doi:10.1007/978-3-642-34419-0_1

Cited by 9 publications

(7 citation statements)

References 51 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…From a knowledge management perspective, a distinction is often made between two types of knowledge: implicit and explicit knowledge . Furthermore, in, requirements knowledge is defined to “consist of implicit or explicit information that is created or needed while engineering, managing implementing, or using requirements, and that is useful for answering requirements‐related questions in any phase of a software project.” Accordingly, this crowdsourced feedback can be explicit or implicit. Since literature seldom gave definitions of explicit and implicit user feedback, we draw on to define explicit and implicit crowdsourced user feedback as below:…”

Section: Our Mapping Study Processmentioning

confidence: 99%

A systematic mapping study on crowdsourced requirements engineering using user feedback

Wang

Daneva

Sinderen

et al. 2019

J Software Evolu Process

View full text Add to dashboard Cite

Crowdsourcing is an appealing concept for achieving good enough requirements and just-in-time requirements engineering (RE). A promising form of crowdsourcing in RE is the use of feedback on software systems, generated through a large network of anonymous users of these systems over a period of time. Prior research indicated implicit and explicit user feedback as key to RE-practitioners to discover new and changed requirements and decide on software features to add, enhance, or abandon.However, a structured account on the types and characteristics of user feedback useful for RE purposes is still lacking. This research fills the gap by providing a mapping study of literature on crowdsourced user feedback employed for RE purposes. On the basis of the analysis of 44 selected papers, we found nine pieces of metadata that characterized crowdsourced user feedback and that were employed in seven specific RE activities. We also found that the published research has a strong focus on crowdgenerated comments (explicit feedback) to be used for RE purposes, rather than employing application logs or usage-generated data (implicit feedback). Our findings suggest a need to broaden the scope of research effort in order to leverage the benefits of both explicit and implicit feedback in RE. KEYWORDScrowdsourced feedback, evidence-based software engineering, large-scale user involvement, requirements engineering, systematic mapping study, user feedback 1 | INTRODUCTION Crowd-based requirements engineering (RE) is the practice of large-scale user involvement in RE activities. Users are unknown volunteers and massive in number. Their involvement can take a variety of forms. For example, users generate information that becomes freely available for requirements specialists to use for requirements elicitation purposes, or participate in distributed problem-solving where they find workarounds in an application, which in turn may shape the requirements for a subsequent application release. To IT-consulting companies and software development organizations, this opportunity for large-scale user involvement means a way to get good-enough requirements and to achieve just-intime RE, which implies a significant potential to reduce the cost of RE processes. One promising form of crowdsourcing in RE-that is exploited by businesses and that attracts much research attention-is the use of feedback volunteered by large networks of anonymous users of software systems over a period of time in an RE activity, such as elicitation, validation, or prioritization.This is an open access article under the terms of the Creative Commons Attribution License, which permits use, distribution and reproduction in any medium, provided the original work is properly cited.

show abstract

Section: Our Mapping Study Processmentioning

confidence: 99%

A systematic mapping study on crowdsourced requirements engineering using user feedback

Wang

Daneva

Sinderen

et al. 2019

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…Therefore, RE is considered a complex task in which, through processes of comprehensive communication with stakeholders, the real properties and limitations of the system are concretised. This communication is developed through collaborative and problem-solving activities in which a great deal of knowledge is exchanged and analysed (Maalej and Thurimella, 2013).…”

Section: Requirements Engineeringmentioning

confidence: 99%

A framework for knowledge management in requirements engineering

Serna

Bachiller³

2018

IJKMS

View full text Add to dashboard Cite

Managing knowledge properly has become a necessity in all types of professional activities, especially in those whose products are highly utilised and disseminated, such as software engineering. Because we live in a softwaredependent society, this technological development requires improving the processes of understanding and manufacturing; thus, it is recommended to use knowledge as a basis to achieve such improvements. This paper presents the results of an analysis of the proposals to manage knowledge in requirements engineering, in which it is evident that the proposals fail to meet the needs of work teams. The practices evaluated in this study propose an integrated framework for the management of knowledge in RE comprised by the conjunction between the phases of knowledge and the stages of RE and characterised by including two principles of complex thought: transdisciplinarity and multidimensionality.

show abstract

“…Following the work of [24], the strategy consists of three phases: domain modelling (DM), system modelling (SM) and specification developing (SD) and structures its flow of activities according the KEM-RE. Furthermore, it includes transversal activities to identify and make explicit the most possible quantity of tacit knowledge.…”

confidence: 99%

Knowledge Management for Informally Structured Domains: Challenges and Proposals

Olmos-Sánchez¹,

Rodas-Osollo²

2017

Knowledge Management Strategies and Applications

View full text Add to dashboard Cite

Eliciting requirements of products or solutions in informally structured domains is a highly creative and complex activity due to the inherent characteristics of these domains, such as the great quantities of tacit knowledge used by domain specialists, the dynamic interaction between domain specialists and their environment in order to solve problems, the necessity of these solutions of products to be developed by teams of specialists and the asymmetry of knowledge between domain specialists and requirements engineers. The knowledge management discipline promotes an integrated approach in order to face these challenges; therefore, a strategy for addressing requirements elicitation that incorporates techniques and methods of this discipline has been proposed as a serious approach to deal with those challenges. The valuable results of the application of the strategy in real cases prove empirical insights about its utility.

show abstract

An Introduction to Requirements Knowledge

Cited by 9 publications

References 51 publications

A systematic mapping study on crowdsourced requirements engineering using user feedback

A systematic mapping study on crowdsourced requirements engineering using user feedback

A framework for knowledge management in requirements engineering

Knowledge Management for Informally Structured Domains: Challenges and Proposals

Contact Info

Product

Resources

About