Agile Requirements Engineering: A systematic literature review

Nowadays, Agile Software Development (ASD) is used to cope with increasing complexity in system development. Hybrid development models, with the integration of User-Centered Design (UCD), are applied with the aim to deliver competitive products with a suitable User Experience (UX). Therefore, stakeholder and user involvement during Requirements Engineering (RE) are essential in order to establish a collaborative environment with constant feedback loops. The aim of this study is to capture the current state of the art of the literature related to Agile RE with focus on stakeholder and user involvement. In particular, we investigate what approaches exist to involve stakeholder in the process, which methodologies are commonly used to present the user perspective and how requirements management is been carried out. We conduct a Systematic Literature Review (SLR) with an extensive quality assessment of the included studies. We identified 27 relevant papers. After analyzing them in detail, we derive deep insights to the following aspects of Agile RE: stakeholder and user involvement, data gathering, user perspective, integrated methodologies, shared understanding, artifacts, documentation and Non-Functional Requirements (NFR). Agile RE is a complex research field with cross-functional influences. This study will contribute to the software development body of knowledge by assessing the involvement of stakeholder and user in Agile RE, providing methodologies that make ASD more human-centric and giving an overview of requirements management in ASD.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-RMinisterio de Economía y Competitividad TIN2015-71938-RED

Integrated knowledge acquisition from text, previously solved cases, and expert memories

Within the model-based knowledge engineering framework, an integrated knowledge acquisition method was developed for a complex real-world domain with different traces of expertise. By having an expert constructively explain the previously solved cases with more general information from other traces of expertise (text, expert memories) a model-centered knowledge base is constructed. The proposed method allows for an early knowledge verification where the relevance, sufficiency, redundancy, and consistency of knowledge are already assessed at an informal level. The early knowledge verification efficiently prepares the consecutive knowledge formalization. Through a cognitively adequate model of expertise and the explanation-oriented knowledge elicitation procedures, user friendly second generation expert systems may be developed

Scenario-based requirements elicitation for user-centric explainable AI

Explainable Artificial Intelligence (XAI) develops technical explanation methods and enable interpretability for human stakeholders on why Artificial Intelligence (AI) and machine learning (ML) models provide certain predictions. However, the trust of those stakeholders into AI models and explanations is still an issue, especially domain experts, who are knowledgeable about their domain but not AI inner workings. Social and user-centric XAI research states it is essential to understand the stakeholder’s requirements to provide explanations tailored to their needs, and enhance their trust in working with AI models. Scenario-based design and requirements elicitation can help bridge the gap between social and operational aspects of a stakeholder early before the adoption of information systems and identify its real problem and practices generating user requirements. Nevertheless, it is still rarely explored the adoption of scenarios in XAI, especially in the domain of fraud detection to supporting experts who are about to work with AI models. We demonstrate the usage of scenario-based requirements elicitation for XAI in a fraud detection context, and develop scenarios derived with experts in banking fraud. We discuss how those scenarios can be adopted to identify user or expert requirements for appropriate explanations in his daily operations and to make decisions on reviewing fraudulent cases in banking. The generalizability of the scenarios for further adoption is validated through a systematic literature review in domains of XAI and visual analytics for fraud detection

Predicting most productive requirements elicitation teams using MBTI personality traits model

The social and collaborative nature of requirements elicitation process bases its core dependency on aptitude, attitudes, and personality characteristics of its participants. The participant's personality characteristics are directly related with their personality traits, which can be categorized using different model has been used successfully for the assessments of personality of software engineers since last few decades. In this article, the personality traits for requirements elicitation teams have been predicted using MBTI personality assessments model, on the basis of their industry demands job descriptions/tasks and major soft skills. The article presents a complete personality prediction process using a systematic approach based on major soft skills mapping with job descriptions, personality attributes and personality. The obtained results show that extroversion and feelings personality traits are the most suitable assigned the task of requirements elicitation. The obtained results are very much aligned with the already published scholar's work for software engineer's personality assessments and development team composition

Observing Users - Designing clarity a case study on the user-centred design of a cross-language information retrieval system

This paper presents a case study of the development of an interface to a novel and complex form of document retrieval: searching for texts written in foreign languages based on native language queries. Although the underlying technology for achieving such a search is relatively well understood, the appropriate interface design is not. A study involving users (with such searching needs) from the start of the design process is described covering initial examination of user needs and tasks; preliminary design and testing of interface components; building, testing, and further refining an interface; before finally conducting usability tests of the system. Lessons are learned at every stage of the process leading to a much more informed view of how such an interface should be built