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

Abstract

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.

Green Requirement Engineering: Towards Sustainable Mobile Application Development and Internet of Things

“…Because mobile development is such a big and diverse field, the software requirements for mobile devices were not appropriately identified or omitted due to their heterogeneous nature, resulting in software failures [60,61].…”

Elevating Cultural Tourism Recommendations: Exploring the Design and Evaluation of ACUX-R’s Mobile Graphical User Interface

“…In this respect, a combination of conversation, observation, and the analytical technique as optimal for the elicitation of both functional and non-functional user requirements has been considered. More specifically, three of the most commonly used techniques in the cultural tourism domain have been combined: literature review as a conversation technique, focus groups as an observation technique, and prototyping as an analytical technique [15,16].…”

Software requirement selection using a combined multi‐objective optimisation technique

“…To do so, HGABC can be extended in many ways, such as finding a generator for the multi NRP datasets, re-advising the problem, and inventing a extra step in ABC utilising operators of GA. Further to this, we will use clustering algorithms to address the incompleteness of requirements and disagreement among stakeholders in software requirements, and the effect of such techniques for requirement prioritisation in a multi-stakeholder context [56]. The HABC-DE will also be used for e-commerce mobile applications development [57] after the model has been applied in the requirements elicitation in different scenarios, often prioritises functional requirements over quality requirements.…”