A Hybrid Three-Phased Approach in Requirement Elicitation

Zakari, Abubakar; Lawan, Abdulmalik Ahmad; Bekaroo, Girish

doi:10.1007/978-3-319-52171-8_30

Cited by 6 publications

(21 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For the requirements elicitation, both functional and NFRs must be considered [3,16], since this increases the possibility of obtaining a quality product [16]. Functional requirements describe the functions that a system or software component must provide [20][21][22].…”

Section: Fundamentalsmentioning

confidence: 99%

“…One of the aspects that has a great influence on the quality and quantity of the requirements obtained during requirements elicitation stage is the selection of the requirements elicitation techniques [3,14]. These techniques can be classified as follows [24,25]:…”

Section: Requirements Elicitation Techniquesmentioning

confidence: 99%

“…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].…”

Section: Introductionmentioning

confidence: 99%

“…Requirements engineering, which is a phase of software engineering, is responsible for identifying the real functions and limitations of a software system [3]. Its purpose is to obtain quality unambiguous requirements [4, 5].…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

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

2020

View full text Add to dashboard Cite

Many of the software development projects are not successfully finished. In many cases, this is because the software requirements were not correctly identified. One of the factors that affect the elicitation of requirements is the proper selection of requirements elicitation techniques. Even when there is a lot of literature that proposes several requirements elicitation techniques, there is no reference process model that indicates the techniques that must be applied by a requirement's engineer to elicit the requirements of a mobile application for e-commerce. This gap covers both the elicitation of functional and nonfunctional requirements. Therefore, the authors propose a new model called reference process model for requirements elicitation for e-commerce mobile applications development (RPM-REFEMAD), which allows the elicitation of requirements based on the use of four elicitation techniques combined in ten steps. The proposed model was applied in the requirements elicitation of two e-commerce mobile applications in different scenarios. To visualise the results of the model, a survey was designed and applied to users/stakeholders who participated in the reference process model evaluation. The survey results indicated that RPM-REFEMAD model helps to elicit more quality and quantity functional and non-functional requirements, in comparison with the use of traditional requirements elicitation techniques.

show abstract

Section: Fundamentalsmentioning

confidence: 99%

Section: Requirements Elicitation Techniquesmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

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

2020

View full text Add to dashboard Cite

show abstract

“…n recent years, advances in software development have led to the increase in complexity of software programs, which adversely resulted in a rise in software failures [1]. The introduction of these failures in a software program due to increasing complexity has negative impacts on software quality, and this has been attributed to the lack of software conformance to it defined requirements [2]. Effective fault localization is important, as 50% to 80% of development and maintenance costs are spent in the debugging process that involves failure detection, fault localization, as well as fault repair [3,4].…”

Section: Introductionmentioning

confidence: 99%

Spectrum-based Fault Localization Techniques Application on Multiple-Fault Programs: A Review

Zakari¹,

Abdullahi²,

Shagari³

et al. 2020

GJCST

Self Cite

View full text Add to dashboard Cite

Software fault localization is one of the most tedious and costly activities in program debugging in the endeavor to identify faults locations in a software program. In this paper, the studies that used spectrum-based fault localization (SBFL) techniques that makes use of different multiple fault localization debugging methods such as one-bug-at-a-time (OBA) debugging, parallel debugging, and simultaneous debugging in localizing multiple faults are classified and critically analyzed in order to extensively discuss the current research trends, issues, and challenges in this field of study. The outcome strongly shows that there is a high utilization of OBA debugging method, poor fault isolation accuracy, and dominant use of artificial faults that limit the existing techniques applicability in the software industry.

show abstract

Hybrid Requirement Elicitation Techniques with Lean Six Sigma Methodology for an Enhanced Framework

Salleh

Nohuddin

2019

Advances in Visual Informatics

View full text Add to dashboard Cite

A Hybrid Three-Phased Approach in Requirement Elicitation

Cited by 6 publications

References 14 publications

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

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

Spectrum-based Fault Localization Techniques Application on Multiple-Fault Programs: A Review

Hybrid Requirement Elicitation Techniques with Lean Six Sigma Methodology for an Enhanced Framework

Contact Info

Product

Resources

About