A Review of Fundamental Tasks in Requirements Elicitation

Sandhu, Ramandeep; Weistroffer, Heinz Roland

doi:10.1007/978-3-030-00060-8_3

Cited by 9 publications

(3 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…However, in the context of EAFP we are concerned with identification of Key Stakeholders only, which are individuals often acting as Business Relationship Managers (BRMs) or department Key Users (KUs). Similar to the definition of Primary Stakeholders from Sandhu & Weistroffer [29], KUs can be defined as individuals, which in the scope of concerned requirement, have authority & power to speak in the name of organisational unit they represent, and responsibility to clarify and interpret business vision of required solution.…”

Section: Identification Of Key Stakeholdersmentioning

confidence: 99%

Eafp

Dedić¹

2021

J. inf. organ. sci. (Online)

View full text Add to dashboard Cite

Enterprise Architecture (EA) is well researched and well-developed concept, and even a two decades ago there were a plenty of frameworks in this field. However, the functional integration of EA at operational and tactical levels in organisations is identified as one of the biggest challenges faced by many Enterprise Architects today. To overcome this challenge, a comprehensive literature review on EA is conducted, which resulted with the identification of the knowledge gap. To overcome this gap, Enterprise Architecture Fusion Process (EAFP), a novel practical approach that demonstrates the capability of integrating EA activities into operational and tactical activities in respective organisation is developed and presented in this paper.

show abstract

Section: Identification Of Key Stakeholdersmentioning

confidence: 99%

Eafp

Dedić¹

2021

J. inf. organ. sci. (Online)

View full text Add to dashboard Cite

show abstract

“…While clear requirements are a major success factor, incomplete and changing requirements are identified as a major cause of the problems leading to project failure (e.g. Alflen, Prado, & Grotta, 2020;Babar, Bunker, & Gill, 2018;Batra & Bhatnagar, 2019;Davey & Parker, 2015;Jukic & Velasco, 2010;Pacheco & Garcia, 2012a;Rosenkranz et al, 2014;Sandhu & Weistroffer, 2018;Taghavi & Woo, 2017). Despite this, little effort has been made within organizations to tackle this issue (PMI, 2014).…”

Section: Introductionmentioning

confidence: 99%

Comparing Requirements Analysis Techniques in Business Intelligence and Transactional Contexts

Guillemette

Fréchette

Moïse

2022

International Journal of Business Intelligence Research

View full text Add to dashboard Cite

Requirements elicitation is a key concern in information technology (IT) projects. Busi-ness intelligence systems (BI) have emerged and are now used widely in organizations. These systems are designed to support manager's decision-making in their business performance moni-toring activities and their requirements are very different from those of transactional systems. But past research did not consider these differences. Therefore, this paper relies on a comparative approach to assess differences in the level of use and perceived effectiveness of requirements analysis techniques in both business intelligence and transactional contexts. An exploratory quali-tative study was conducted with two phases of semi-structured interviews with experienced practitioners. Our results show that 28% of the techniques differ in their level of use or perceived effectiveness, thus demonstrating the specificity of decision makers' needs. Our results reveal the importance of using techniques appropriate to the context to adequately define requirements and improve projects’ success.

show abstract

“…Also, knowledge engineers often use requirements engineering techniques according to their knowledge, preferences and organizational guidelines, without analyze the specific requirements of knowledge management initiatives, influencing the effective selection of the set of techniques (Milton, 2007; Zheying, 2007). These aspects show the relevance of research about techniques for the identification of organizational knowledge management requirements (Sandhu and Weistroffer, 2018).…”

Section: Introductionmentioning

confidence: 99%

Techniques for the identification of organizational knowledge management requirements

Giraldo

Aguilar

Marín

et al. 2019

JKM

View full text Add to dashboard Cite

Purpose This paper aims to explore the requirements of organizational knowledge management initiatives using requirements engineering techniques, identifying the optimal techniques configuration and serving as a management tool for knowledge engineers. Design/methodology/approach The method is selection attributes. Knowledge management enablers are characterized and mapped with the coverage capabilities of requirements engineering techniques, using the attributes of the elicited object and a box-plot analysis. The information is gathered from 280 references, 32 companies and 16 experts in requirements engineering. Findings Requirements of organizational knowledge management initiatives are got optimally by combining interviews, use cases, scenarios, laddering and focus group techniques. The requirements of structure and processes are more complex to identify, while culture requirements are the best covered. Research limitations/implications Knowledge management enablers are analyzed according to the current studies and comprehension of engineering techniques. Practical implications Knowledge engineers need to consider the coverage capabilities of engineering techniques to design an optimal requirement identification and meet the objectives of organizational knowledge acquisition initiatives. Requirement engineers can improve the requirements identification by a staged selection process. Social implications The requirements of knowledge management initiatives that impact the community can be identified and traced to ensure the knowledge objectives. Requirements related to culture and people, like shared values, beliefs, and behaviors, are also considered. Originality/value To the best of the authors’ knowledge, this is the first study about formal requirement identification of knowledge management initiatives in the organizational context, providing the optimal configuration. A novel staged process is proposed for requirements engineering techniques selection, analyzing the enablers at component level and identifying the attributes associated with the elicited object.

show abstract

A Review of Fundamental Tasks in Requirements Elicitation

Cited by 9 publications

References 22 publications

Eafp

Eafp

Comparing Requirements Analysis Techniques in Business Intelligence and Transactional Contexts

Techniques for the identification of organizational knowledge management requirements

Contact Info

Product

Resources

About