A Survey About the Impact of Requirements Engineering Practice in Small-Sized Software Factories in Sinaloa, Mexico

Aguilar, José Alfonso; Zaldívar-Colado, Aníbal; Tripp-Barba, Carolina; Espinosa, Roberto; Misra, Sanjay; Zurita, Carlos Eduardo

doi:10.1007/978-3-319-95171-3_26

Cited by 7 publications

(6 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Furthermore, we were able to identify the consequences of incorrect stakeholder identification through the proposed SLR study. We debated in our proposed approach if requirements are gathered from wrong or irrelevant stakeholders that might lead to incorrect, ambiguous, and incomplete stakeholder requirements, thus affecting the software requirements specification document, which results in the project failure [146,147]. For this purpose, we identify two main categories from the literature studies that gathering or eliciting requirements from incorrect or wrong stakeholders can lead to system failure and exceed the development project's cost and time.…”

Section: Discussionmentioning

confidence: 99%

A Comparative Systematic Analysis of Stakeholder’s Identification Methods in Requirements Elicitation

Khan

Assam

et al. 2022

IEEE Access

View full text Add to dashboard Cite

Context and Motivation]Before eliciting and gathering requirements for a software project, it is considered pivotal to know about concerned stakeholders. It becomes hard to elicit the actual system requirements without identifying relevant stakeholders, leading the software project to failure. Despite the paramount importance of stakeholder identification in requirement elicitation, it has been given less attention in the software engineering literature.[Method] For this purpose, we conducted a thorough Systematic Literature Review (SLR) on stakeholder identification (SI) and its methods in requirement elicitation. However, previously, a literature study on SI in the requirement elicitation was conducted. We found that no one has proposed any standard or baseline research method for stakeholder identification, stakeholder assessment, and stakeholder interaction up to date according to our knowledge. It provides an opportunity to update the current SLR on SI in requirements elicitation from 2011 till 2021 to search for a baseline methodology for the SI. For this purpose, we explored the existing literature research that involves the SI methods in requirements elicitation. [Principle Ideas/Results] Furthermore, we identify and capture seventeen research methodologies for SI, eight key stakeholders interaction methods, and ten stakeholders assessment methods in requirement elicitation. To further enhance the stakeholder identification process, we additionally identify pivotal information such as different potential stakeholder categories, stakeholder assessments methods, and stakeholder interaction methods. Also, based on the proposed SLR, we find out the existing gaps and new opportunities for SI methods in the requirement elicitation. [Contribution] These SI methodologies help requirements engineers and practitioners identify key stakeholders and efficiently improve the requirements quality. Moreover, this research study helps identify the effective practices used for the traditional and CrowdRE SI, recover consequences that can affect the effectiveness of SI, and recommend advisable SI practices to be employed in the future. This research study would help the software researchers and developers efficiently and accurately identify correct and concerned stakeholders to improve end-user satisfaction instead of considering it a self-evident task. INDEX TERMS Stakeholder Identification, stakeholder methods, Requirement Elicitation, SLR.

show abstract

Section: Discussionmentioning

confidence: 99%

A Comparative Systematic Analysis of Stakeholder’s Identification Methods in Requirements Elicitation

Khan

Assam

et al. 2022

IEEE Access

View full text Add to dashboard Cite

show abstract

“…Aguilar et al [19] investigated the impact of RE practice in 16 small-sized software firms through a survey in Sinaloa, Mexico. The degree of relationship between each variable was determined using Pearson correlation analysis.…”

Section: E Survey On Re In Practicementioning

confidence: 99%

Issues in Requirements Specification in Malaysia’s Public Sector: An Evidence from a Semi-Structured Survey and a Static Analysis

Zahrin¹,

Osman²,

Halin³

et al. 2022

IJACSA

View full text Add to dashboard Cite

Requirement specifications (RS) are essential and fundamental artefacts in system development. RS is the primary reference in software development and is commonly written in natural language. Bad requirement quality, such as requirement smells, may lead to project delay, cost overrun, and failure. Focusing on requirement quality in the Malaysian government, this paper investigates the methods for preparing Malay RS and personnel competencies to identify the root cause of this issue. We conducted semi-structured interviews that involved 17 respondents from eight critical Malaysian public sector agencies. This study found that ambiguity, incompleteness, and inconsistency are the top three requirement smells that cause project delays and failures. Furthermore, based on our static analysis, we collected the initial Malay RS documents from various Malaysian public sector agencies; we found that 30% of the RS were ambiguous. Our analysis also found that respondents with more than 10 years of experience could manually identify the smells in RS. Most respondents chose the Public Sector Application Systems Engineering (KRISA) handbook as a guideline for preparing Malay RS documents. Respondents acknowledged a correlation between the quality of RS and project delays and failures.

show abstract

“…Unfortunately, this relationship seems to be underestimated: during the software engineering process, the requirements are not necessarily identified, qualified, or prioritized, which constitute weaknesses associated with the requirements management [ 15 , 16 , 37 ].…”

Section: Theoretical Frameworkmentioning

confidence: 99%

“…Because most researchers and the software industry define requirements management as a key process, and it is recognized as a key phase for successful project management [ 15 , 16 ]. The goal of this paper is to provide a path to follow to facilitate the implementation of best practices in the requirements management process.…”

Section: Introductionmentioning

confidence: 99%

A Path for the Implementation of Best Practices for Software Requirements Management Process Using a Multimodel Environment

Gasca‐Hurtado

Muñoz²

2020

Computational Science and Its Applications – ICCSA 2020

View full text Add to dashboard Cite

Continuous improvement is one of the topics of interest for organizations seeking positioning opportunities in the world market. However, software development organizations have high levels of difficulty to implement best practices that address continuous improvement. This paper presents a path to follow to facilitate the work of continuous improvement in a software development organization and that seeks to implement best practices in the software requirements management process. The path is drawn from an analysis of software process improvement models and standards related to software development best practices, under a multimodel environment. The path is structured with a set of techniques, tools, activities, and outputs associated with identified best practices, to facilitate the implementation of improvements in the software requirements management process. Besides, the established path is proposed as an alternative to facilitate the process improvement using a multimodel environment, this way allows establishing balance and instances of collaboration among best practices independent of the model or standard to be implemented.

show abstract

A Survey About the Impact of Requirements Engineering Practice in Small-Sized Software Factories in Sinaloa, Mexico

Cited by 7 publications

References 8 publications

A Comparative Systematic Analysis of Stakeholder’s Identification Methods in Requirements Elicitation

A Comparative Systematic Analysis of Stakeholder’s Identification Methods in Requirements Elicitation

Issues in Requirements Specification in Malaysia’s Public Sector: An Evidence from a Semi-Structured Survey and a Static Analysis

A Path for the Implementation of Best Practices for Software Requirements Management Process Using a Multimodel Environment

Contact Info

Product

Resources

About