Functional and non-functional requirements prioritization: empirical evaluation of IPA, AHP-based, and HAM-based approaches

2015 ◽  
Vol 20 (11) ◽  
pp. 4497-4520 ◽  
Author(s):  
Mohammad Dabbagh ◽  
Sai Peck Lee ◽  
Reza Meimandi Parizi
Keyword(s):  
Empirical Evaluation ◽  
Functional Requirements ◽  
Requirements Prioritization

scholarly journals On systematically building a controlled natural language for functional requirements

2021 ◽  
Vol 26 (4) ◽  
Author(s):  
Alvaro Veizaga ◽  
Mauricio Alferez ◽  
Damiano Torre ◽  
Mehrdad Sabetzadeh ◽  
Lionel Briand
Keyword(s):  
Information System ◽  
Natural Language ◽  
Qualitative Methodology ◽  
Case Study Research ◽  
Empirical Evaluation ◽  
Functional Requirements ◽  
Industrial Case Study ◽  
Requirements Specifications ◽  
Financial Domain

AbstractNatural language (NL) is pervasive in software requirements specifications (SRSs). However, despite its popularity and widespread use, NL is highly prone to quality issues such as vagueness, ambiguity, and incompleteness. Controlled natural languages (CNLs) have been proposed as a way to prevent quality problems in requirements documents, while maintaining the flexibility to write and communicate requirements in an intuitive and universally understood manner. In collaboration with an industrial partner from the financial domain, we systematically develop and evaluate a CNL, named Rimay, intended at helping analysts write functional requirements. We rely on Grounded Theory for building Rimay and follow well-known guidelines for conducting and reporting industrial case study research. Our main contributions are: (1) a qualitative methodology to systematically define a CNL for functional requirements; this methodology is intended to be general for use across information-system domains, (2) a CNL grammar to represent functional requirements; this grammar is derived from our experience in the financial domain, but should be applicable, possibly with adaptations, to other information-system domains, and (3) an empirical evaluation of our CNL (Rimay) through an industrial case study. Our contributions draw on 15 representative SRSs, collectively containing 3215 NL requirements statements from the financial domain. Our evaluation shows that Rimay is expressive enough to capture, on average, 88% (405 out of 460) of the NL requirements statements in four previously unseen SRSs from the financial domain.

scholarly journals Semantic Clustering of Functional Requirements Using Agglomerative Hierarchical Clustering

Information ◽  
2018 ◽  
Vol 9 (9) ◽  
pp. 222 ◽  
Author(s):  
Hamzeh Eyal Salman ◽  
Mustafa Hammad ◽  
Abdelhak-Djamel Seriai ◽  
Ahed Al-Sbou
Keyword(s):  
Empirical Evaluation ◽  
Modern Society ◽  
Development Project ◽  
Functional Requirements ◽  
Software Projects ◽  
Daily Work ◽  
Software Development Project ◽  
Software Applications ◽  
Functional Quality ◽  
Functional Software

Software applications have become a fundamental part in the daily work of modern society as they meet different needs of users in different domains. Such needs are known as software requirements (SRs) which are separated into functional (software services) and non-functional (quality attributes). The first step of every software development project is SR elicitation. This step is a challenge task for developers as they need to understand and analyze SRs manually. For example, the collected functional SRs need to be categorized into different clusters to break-down the project into a set of sub-projects with related SRs and devote each sub-project to a separate development team. However, functional SRs clustering has never been considered in the literature. Therefore, in this paper, we propose an approach to automatically cluster functional requirements based on semantic measure. An empirical evaluation is conducted using four open-access software projects to evaluate our proposal. The experimental results demonstrate that the proposed approach identifies semantic clusters according to well-known used measures in the subject.

scholarly journals An Approach for Integrating the Prioritization of Functional and Nonfunctional Requirements

2014 ◽  
Vol 2014 ◽  
pp. 1-13 ◽  
Author(s):  
Mohammad Dabbagh ◽  
Sai Peck Lee
Keyword(s):  
Assessment Method ◽  
Functional Requirements ◽  
Analytic Hierarchy ◽  
Requirements Prioritization ◽  
Nonfunctional Requirements ◽  
Prioritization Process ◽  
High Level ◽  
Empirical Experiment ◽  
Hierarchy Process

Due to the budgetary deadlines and time to market constraints, it is essential to prioritize software requirements. The outcome of requirements prioritization is an ordering of requirements which need to be considered first during the software development process. To achieve a high quality software system, both functional and nonfunctional requirements must be taken into consideration during the prioritization process. Although several requirements prioritization methods have been proposed so far, no particular method or approach is presented to consider both functional and nonfunctional requirements during the prioritization stage. In this paper, we propose an approach which aims to integrate the process of prioritizing functional and nonfunctional requirements. The outcome of applying the proposed approach produces two separate prioritized lists of functional and non-functional requirements. The effectiveness of the proposed approach has been evaluated through an empirical experiment aimed at comparing the approach with the two state-of-the-art-based approaches, analytic hierarchy process (AHP) and hybrid assessment method (HAM). Results show that our proposed approach outperforms AHP and HAM in terms of actual time-consumption while preserving the quality of the results obtained by our proposed approach at a high level of agreement in comparison with the results produced by the other two approaches.

IMPORTANCE OF FUNCTIONAL REQUIREMENTS PRIORITIZATION: ODOO ERP AS CASE STUDY

2020 ◽  
Vol 14 (4) ◽  
pp. 1
Author(s):  
YASEEN MUHAMMAD ◽  
MUSTAPHA AIDA ◽  
IBRAHIM NORAINI ◽  
UR RAHMAN ATTA ◽  
WAJID KAMAL SYED ◽  
...  
Keyword(s):  
Functional Requirements ◽  
Requirements Prioritization

EARLY USABILITY MEASUREMENT IN MODEL-DRIVEN DEVELOPMENT: DEFINITION AND EMPIRICAL EVALUATION

2011 ◽  
Vol 21 (03) ◽  
pp. 339-365 ◽  
Author(s):  
JOSE IGNACIO PANACH ◽  
NELLY CONDORI-FERNÁNDEZ ◽  
TANJA VOS ◽  
NATHALIE AQUINO ◽  
FRANCISCO VALVERDE
Keyword(s):  
Conceptual Models ◽  
Empirical Evaluation ◽  
End Users ◽  
Functional Requirements ◽  
Video Cameras ◽  
Model Driven ◽  
Usability Problems ◽  
Intuitive Interfaces ◽  
Analysis Design ◽  
Final System

Usability is currently a key feature for developing quality systems. A system that satisfies all the functional requirements can be strongly rejected by end-users if it presents usability problems. End-users demand intuitive interfaces and an easy interaction in order to simplify their work. The first step in developing usable systems is to determine whether a system is or is not usable. To do this, there are several proposals for measuring the system usability. Most of these proposals are focused on the final system and require a large amount of resources to perform the evaluation (end-users, video cameras, questionnaires, etc.). Usability problems that are detected once the system has been developed involve a lot of reworking by the analyst since these changes can affect the analysis, design, and implementation phases. This paper proposes a method to minimize the resources needed for the evaluation and reworking of usability problems. We propose an early usability evaluation that is based on conceptual models. The analyst can measure the usability of attributes that depend on conceptual primitives. This evaluation can be automated taking as input the conceptual models that represent the system abstractly.

scholarly journals Towards a Semi-Automated Data-Driven Requirements Prioritization Approach for Reducing Stakeholder Participation in SPL Development

2021 ◽  
Vol 7 (1) ◽  
pp. 27
Author(s):  
María Isabel Limaylla ◽  
Nelly Condori-Fernandez ◽  
Miguel R. Luaces
Keyword(s):  
Software Quality ◽  
Stakeholder Participation ◽  
Data Driven ◽  
User Needs ◽  
Functional Requirements ◽  
Software Projects ◽  
Product Lines ◽  
Requirements Prioritization ◽  
Prioritization Process ◽  
Software Product

Requirements prioritization (RP), part of Requirements engineering (RE), is an essential activity of Software Product-Lines (SPL) paradigm. Similar to standard systems, the identification and prioritization of the user needs are relevant to the software quality and challenging in SPL due to common requirements, increasing dependencies, and diversity of stakeholders involved. As prioritization process might become impractical when the number of derived products grows, recently there has been an exponential growth in the use of Artificial Intelligence (AI) techniques in different areas of RE. The present research aims to propose a semi-automatic multiple-criteria prioritization process for functional and non-functional requirements (FR/NFR) of software projects developed within the SPL paradigm for reducing stakeholder participation.

scholarly journals Requirements Prioritization Techniques Comparison

2018 ◽  
Vol 12 (2) ◽  
pp. 62 ◽  
Author(s):  
Amjad Hudaib ◽  
Raja Masadeh ◽  
Mais Haj Qasem ◽  
Abdullah Alzaqebah
Keyword(s):  
Project Success ◽  
Requirement Engineering ◽  
Decision Makers ◽  
Software Project ◽  
Functional Requirements ◽  
Engineering Process ◽  
Requirements Prioritization ◽  
Requirement Engineering Process ◽  
Single Technique ◽  
Requirement Prioritization

Requirements prioritization is considered as one of the most important approaches in the requirement engineering process. Requirements prioritization is used to define the ordering or schedule for executing requirement based on their priority or importance with respect to stakeholders’ viewpoints. Many prioritization techniques for requirement have been proposed by researchers, and there is no single technique can be used for all projects types. In this paper we give an overview of the requirement process and requirement prioritization concept. We also present the most popular techniques used to prioritize the software project requirements and a compression between these techniques. On the other hand, we spot the light on the importance of involving the non-functional requirements prioritization because of the great effects of non-functional on project success and quality; some approaches that used in prioritize non-functional requirements are discussed in this paper, in addition a general model is proposed based on reviewing the prioritization techniques in order to suggests a best suited technique for specific projects according to decision makers parameters. 

Sign in / Sign up

Export Citation Format

Share Document